richard_cocks
04-03-2002, 03:59 PM
My friend has a 1.33GHz athlon and for about a year, after a while in intensive programs (3d games ) and occasionally in windows, the computer just completely locks up.
I was trying to help today, I know it isn't the vid card as he has tried various devices. I figured it could be the ram of CPU overheating, so I DLed MBM5 and WCPUID.
The mbm5 was a little high (CPU about 60C, sys temp about 30-40) in windows, but didn't get much more under load. That temp isn't too high for the specifications, but that was with the side case off and a case fan running.
What did concern me (and what I really want to get from this thread) is why WCUPID showed the system bus as 134.32MHz, and the DDR double that accordingly.
The bios determined the CPU as 1333 in the post screen, and in the bios setup the FSB settings were 133/33.
However in WCPUID there was this discrepency.
Does anyone know if this is a simple reporting error or could this very small uncontroled OC be a source of the error.
Had he been more happy about transfering things, I would have helped lend him some SDR, but we tried swapping the DDR's slot over, but that ram took ages and LOTS of force to get it back in the slot, and it also soundec like someone treading on gravel as we did.
I wanna help my friend out, but short of stripping it down and testing various bios settings trying to underclock it I didn't think there was much I could do.
Also it isn't software, this was happening after a fresh format.
It is an ALi chipset, could flashing the BIOS help cure this error?
I just though the post screen was what the CPU was running at whatever, but I trust WCPUID a lot, especially since it woudl explain why it freezes (well almost, a 1MHz fsb Oc shouldn't really cause a lockup, but would be nice to eliminate)
I was trying to help today, I know it isn't the vid card as he has tried various devices. I figured it could be the ram of CPU overheating, so I DLed MBM5 and WCPUID.
The mbm5 was a little high (CPU about 60C, sys temp about 30-40) in windows, but didn't get much more under load. That temp isn't too high for the specifications, but that was with the side case off and a case fan running.
What did concern me (and what I really want to get from this thread) is why WCUPID showed the system bus as 134.32MHz, and the DDR double that accordingly.
The bios determined the CPU as 1333 in the post screen, and in the bios setup the FSB settings were 133/33.
However in WCPUID there was this discrepency.
Does anyone know if this is a simple reporting error or could this very small uncontroled OC be a source of the error.
Had he been more happy about transfering things, I would have helped lend him some SDR, but we tried swapping the DDR's slot over, but that ram took ages and LOTS of force to get it back in the slot, and it also soundec like someone treading on gravel as we did.
I wanna help my friend out, but short of stripping it down and testing various bios settings trying to underclock it I didn't think there was much I could do.
Also it isn't software, this was happening after a fresh format.
It is an ALi chipset, could flashing the BIOS help cure this error?
I just though the post screen was what the CPU was running at whatever, but I trust WCPUID a lot, especially since it woudl explain why it freezes (well almost, a 1MHz fsb Oc shouldn't really cause a lockup, but would be nice to eliminate)