bad motherboard?

ccho

Junior Member
Sep 20, 2006
12
0
0
I recently put together a system and encountered a problem that neither me nor my friends have seen before and am afraid it might be a bad motherboard since I have ruled out almost every other factor.

The system is an ABIT Fatal1ty F-I90HD with e6600 C2D and 2GB Crucial Ballistix DDR2-800. The rest of the components have been tested and interchanged with another set of components in my main PC.

I initially setup Windows XP and Ubuntu Linux Server on this machine and it seemed to be working fine until I decided to flash the bios to smooth out the bugs with S3 suspend mode. After flashing the bios with version 12 using a DOS boot cd, I got the "CMOS Checksum Error - Defaults Loaded" text. I decided to go into setup to fix all the BIOS settings to what they were before. The PC rebooted and immediately shutoff before it POST-ed.

I cleared the CMOS using the jumper and decided to press resume rather than setup after I got the CMOS Checksum Error again. It almost completed booting XP and then shut down. It would then shut down before POST-ing on subsequent boot attempts until I reset the CMOS again with the jumpers. I tried booting Ubuntu through GRUB using the Resume option to get through and that also shut down before it displayed the login after the Ubuntu splash screen.

I have tried using a new CMOS battery, ran memtest, reseated all components, changed the PSU, disconnected the HDs, checked system temps, etc. I can't think of anything else to try... anyone have any ideas? Should I RMA the motherboard?
 

ccho

Junior Member
Sep 20, 2006
12
0
0
Solved my own problem... the motherboard was reporting the wrong CPU temp and auto shutdown was enabled. Not sure why both versions of the BIOS do not report the correct temperature however.
 

Puffnstuff

Lifer
Mar 9, 2005
16,187
4,871
136
Abit has had long standing issues with reported temps with their bios. When I first got my fatal1ty an8 the bios reported really high temps and it took several months before abit corrected the problem. I would tell you to head over to the abit forum however their site is down.