S
S.Boardman
Hello. As found in many posts below, I recently upgraded an Athlon XP2000+
on a MSI KT3 Ultra VIA KT333 chipset to the same board with a XP2500+, 512Mb
Corsair PC3200 RAM, plus new heatsink. I have Win 98SE.
I'd changed the FSB to 166, and RAM settings sorted, CAS 2.5, I thought it
was all stable and OK. Memtest was fine, Windows processor load was 100%
(using SETI) for three or four days running 24/7. The BIOS reported temp has
never been above 39 degrees, with system temp about 33 degrees (side off
case).
Last night, playing a 2D game (Northland demo), with SETI running in the
background as low priority, Windows rebooted with no errors or anything. (I
have played the game like this before with no probs.) Then it did it again
during Scandisk on the reboot. I had just got into the BIOS to check things
and it did it again. I have dropped back down to FSB133, and changed the
memory, too. I don't know if this will cure the problem.
Why should it do this after four days of running fine? The m/b, CPU and
memory should have no problems at this speed (FSB166). The PSU is 300W, it
has a two disk RAID to supply plus a DVD-ROM drive. The graphics card is a
nVidia GeForce 4 MX440.
Please help.
on a MSI KT3 Ultra VIA KT333 chipset to the same board with a XP2500+, 512Mb
Corsair PC3200 RAM, plus new heatsink. I have Win 98SE.
I'd changed the FSB to 166, and RAM settings sorted, CAS 2.5, I thought it
was all stable and OK. Memtest was fine, Windows processor load was 100%
(using SETI) for three or four days running 24/7. The BIOS reported temp has
never been above 39 degrees, with system temp about 33 degrees (side off
case).
Last night, playing a 2D game (Northland demo), with SETI running in the
background as low priority, Windows rebooted with no errors or anything. (I
have played the game like this before with no probs.) Then it did it again
during Scandisk on the reboot. I had just got into the BIOS to check things
and it did it again. I have dropped back down to FSB133, and changed the
memory, too. I don't know if this will cure the problem.
Why should it do this after four days of running fine? The m/b, CPU and
memory should have no problems at this speed (FSB166). The PSU is 300W, it
has a two disk RAID to supply plus a DVD-ROM drive. The graphics card is a
nVidia GeForce 4 MX440.
Please help.