//flex table opened by JP

Click to See Complete Forum and Search --> : System lockups (1.2Tbird)


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)

Sterling_Aug
04-03-2002, 04:43 PM
The 1.34 MHz error you are reporting is not enough to worry about.

What confuses me is you say it is a 1200 MHz processor and then you say the BIOS sees it as 1333 MHz.

It sounds to me like your jumper/BIOS settings are not set correctly and you may be overclocking the processor without knowing it.

richard_cocks
04-03-2002, 05:24 PM
Mistake, I'll edit now, that was just me being dumb, it is a 1333Mhz Tbrid, I just had 1.2 on the brain from a dif post.

And it wasn't the OC that worried me, more it was happening in a strange amount and unreported anywhere in the BIOS and on jumpers etc.

Actually I didn't check the jumpers. Since he wouldn't really let me poke around his nice baby I didn't want to push it, moving the ram was such a struggle (somehow I think the mobo may have slightly been curved since installing that was a bugger, I've never known such force be needed). I didn't want to ask about mobo jumpers etc.

However at worst it would be only a 1MHz increment to the FSB that way, and that would still be reported in the BIOS.

I would have tried under clocking it to see whether this stopped the freezing, but in the bios the option under 133/33 was 132/44

Bios mistake or what is this, I have never heard of 44!