Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
system always makes errors
- Thread starter jaslatrix
- Start date
If you are using a PCCHIPS / SIS motherboard there are known problems - the north / south chipset is rated at a maximun speed lower than the board can run. For instance, the M598LMR has a maximun bus speed of 100mHz, but the chipset is rated 82mHz. Setting the bus speed to what a higher-speed CPU needs is actually overclocking the main chipset. Slowing the board down and using a higher multiplier makes it more stable.
If not you have either (1) a processor problem (heat caused or other CPU fault), (2) RAM problem, (3) power problem (running at higher speeds causes components to draw more power, and thereby disipate more energy as heat). Bring in RAM to, say. a computer show / swap meet and usually a dealer has a hardware-based RAM tester. Have them check the RAM up to your set speed. It's not too unusual for 1 chip on a SIMM or DIMM to be slightly off-tolerance. Otherwise suspect heat - those are the 1 & 2 primary causes.
If not CPU & MB may need to be changed. If CPU gets damaged it is somewhat common for the MB to be damaged also. If you can swap CPU to check - but if MB is damaged new CPU gets damaged, as well. A hit-or-miss proposition. Your mileage may vary...
If not you have either (1) a processor problem (heat caused or other CPU fault), (2) RAM problem, (3) power problem (running at higher speeds causes components to draw more power, and thereby disipate more energy as heat). Bring in RAM to, say. a computer show / swap meet and usually a dealer has a hardware-based RAM tester. Have them check the RAM up to your set speed. It's not too unusual for 1 chip on a SIMM or DIMM to be slightly off-tolerance. Otherwise suspect heat - those are the 1 & 2 primary causes.
If not CPU & MB may need to be changed. If CPU gets damaged it is somewhat common for the MB to be damaged also. If you can swap CPU to check - but if MB is damaged new CPU gets damaged, as well. A hit-or-miss proposition. Your mileage may vary...
Sorry, but you weren't listening - slowing the processor and FSB will reduce bit errors caused by timing faults when accessing the memory and peripherals.
If a component of the system is off spec of the running FSB / CPU frequency it can drop bits due to its lack of being able to respond in time to the clock pulse. Your mileage may vary...
If a component of the system is off spec of the running FSB / CPU frequency it can drop bits due to its lack of being able to respond in time to the clock pulse. Your mileage may vary...
I was trying to understand how you got all of that from his post. I guess I'm not that good at reading between the lines. He never said what kind of errors he was getting.(BSOD, page faults, freezes.....)????? It could be anything (including CPU speed). "A little knowledge is a dangerous thing....." ![[morning]](/data/assets/smilies/morning.gif "[morning] [morning]")
Apologies. My fault entirely. With my current physical condition (I broke my right wrist Monday) writing these tech tips takes forever one-handed and is physically challenging. My post about system resources (in different posting) took over 30 minutes to type.
In order for a system to run at a certain speed all components must be capable of that speed. To simplify - slowing down the processor allows all components time to react in the proper manner. RAM, for instance. Let's go with the classic design, not taking into account current clock double and quadruple-pumping designs.
The RAM can only accept data in an exactly timed window between the down side of the clock pulse and any other timings, like the refresh and the address strobe. Reaction and storage (or retrieval) must occur in this window. If the RAM is off-timing it will not catch the full rise, or fall, of the data square waves. So, for instance, instead of seeing the pulse from the beginning - rising from 0 to say 4.7V which would read as '1' - by being late on sync it would see the pulse falling from 1.8V to 0 and read it as a '0'. Instant bit error.
Sorry for the technical, but the only way to properly explain. Previous based on 5V dynamic RAM, single clock read.
So slowing the system down allows all components to see and react properly to all events. Since he stated in the opening remarks that slowing the system down makes it work the direct correlation is that some component can't handle the speed - it either wasn't designed for it, was designed but out of spec (from factory or aging), or suffered damage and is no longer capable of the speed. Your mileage may vary...
In order for a system to run at a certain speed all components must be capable of that speed. To simplify - slowing down the processor allows all components time to react in the proper manner. RAM, for instance. Let's go with the classic design, not taking into account current clock double and quadruple-pumping designs.
The RAM can only accept data in an exactly timed window between the down side of the clock pulse and any other timings, like the refresh and the address strobe. Reaction and storage (or retrieval) must occur in this window. If the RAM is off-timing it will not catch the full rise, or fall, of the data square waves. So, for instance, instead of seeing the pulse from the beginning - rising from 0 to say 4.7V which would read as '1' - by being late on sync it would see the pulse falling from 1.8V to 0 and read it as a '0'. Instant bit error.
Sorry for the technical, but the only way to properly explain. Previous based on 5V dynamic RAM, single clock read.
So slowing the system down allows all components to see and react properly to all events. Since he stated in the opening remarks that slowing the system down makes it work the direct correlation is that some component can't handle the speed - it either wasn't designed for it, was designed but out of spec (from factory or aging), or suffered damage and is no longer capable of the speed. Your mileage may vary...
I misunderstood his post entirely, so it's my fault. I thought he meant his PC stopped after slowing it down. If he meant the errors stopped tnen I see your point. My apologies to you. "A little knowledge is a dangerous thing....."
Your mileage may vary...- Status
Similar threads
- Locked
- Question
- Locked
- Question