MSI KT3 ultra2 reboots frequently

kais

Junior Member
Oct 6, 2002
21
0
0
Hi, I set up the ultra2 mb with AMD 1800+ over the weekend. NO overclocking at all. I installed windows 2000. It has 256mb pc2100 kingston rams and a 30gb maxtor 7200rpm HD. THe video card is a 3dfx vodoo. I did some stress tests Prime95 and SiSoftware Sandra Standard). It didn't crash. The temperature was around 45-49c under full load. I use coolermaster hsc-v62 which is a auto speed cpu cooler. All looked great. No rebbot. looked very stable. But I always got some beeping and a green screen when I power up the computer before the video card info. is displayed. Fast boot is disable. The MSI logo is disable.

Then last night, I set up the modem. Then I flashed the bios with the lastest 5.6 bios. The machine rebooted frequently. I launched PC alert 4. The cpu temperature was around 40c. That looked ok. Sometimes the machine boots into windows, and after I do some non-cpu-intense work, like going online, or launching some applications, it reboots. Then during the reboot, sometimes it reboots again when the bios info is being displayed( not even get to boot the device). Sometimes it reboots when the windows 2000 startup staus bar is advancing. Sometimes nothing is displayed during the bootup. Checking the LEDs on the D-Bracket, it indicates that it's trying to initializing hard drive controller. It even reboots when I just look at the bios menu(eg. checking PC health status). I lower the cpu FSB clock from 133mhz to 100mhz. It still have the same problem.

I think it's the bios problem. Then i downloaded ami 5.5 bios and flashed it. It seemed to work. but after I ran Prime95 to do the stress test for a few mins, it rebooted again. And the same weired rebooting problems happened.

The screen before video card detection sometimes is red, sometimes is green. It alwasy beeps when the screen is displaying.


Because it reboots before it looks for the boot device, I think this is really a bios problem.
I don't remember the version of the original bios. There are only 2 versions of bios on the msi support site: 5.5 and 5.6.

Lesson learned: never go for the latest version if the current one is working fine. Being a programmer, I should have known that...................................

Please help.
Thanks a lot.
 

kais

Junior Member
Oct 6, 2002
21
0
0
I forgot to mention the PS info.
It's a duro 400w PS. It comes with this case

It has 28A on the 3.3v rail and 30A on the 5v.
 

jatwell

Golden Member
Oct 9, 1999
1,730
0
76
Do you happen to have another power supply just to test with? Even if it's only an old 250W ATX power supply, that would most likely rule it out as a cause. It really does sound like a bad power supply, and if not that, a bad motherboard...
 

kais

Junior Member
Oct 6, 2002
21
0
0
It's not stable at all with the safe setting. Now it doesn't even get into the windows. Whenever the default user is logged into the system, it just reboots.

The system beeps 4 times. according to th AMI bios doc, it means 'Motherboard Timer Not Operational'. what's that? Does it mean I got a bad board?

I don't have any other psu to test.
 

kais

Junior Member
Oct 6, 2002
21
0
0
Now it's dead...... Man... the power supply's fan doesn't even spin.......
must be the board.... I hope it didn't damage the CPU.....
I shorted the green and black pins on the power supply connector. The fan of the ps spins....
I need to exchange the board.
 

AMCRambler

Diamond Member
Jan 23, 2001
7,714
31
91
I would take everything out of the board and reseat everything good. I had mine working fine and then took the chip out to test my friend's in my board, and then put everything back in and when I booted up I started having reboots too. We had also reset the cmos. I took the chip out and reseated it snugly in the socket and made sure the heatsink was clamped firmly over the chip. Another thing we found out with the MSI boards is that if the heatsink isn't pushing the chip down into the socket, they won't boot. We were messing around for a couple hours trying to get the dumb thing to just post so we didn't have the heatsink on the chip or anything. Then we popped his chip into my board without the heatsink on it, so we thought it was the chip when it did the same thing in my pc. We put my chip back in my pc minus the heatsink and tried booting it and it did the same thing his was doing. as soon as we clamped the heatsink back on, it booted up no prob. We felt really stupid afterward, but I don't remember ever seeing anything about this prob anywhere. If that doesn't do it, plug your Dr. LED thing in and see what error code it's giving you.