Page 1 of 1

BIOS Checksum Error

Posted: Sun Feb 10, 2002 9:05 am
by Busby
Ok my server started acting weird the other day. I would boot it up and Award BootBlock would show up and say BIOS Checksum Error. I pressed the reset button on the computer and it did the same thing. Pressed reset again and it booted up jst fine, no errors. Been runnin for awhile and then this morning my internet wasn't working. So I goto the server and it is just frozen, mouse, keyboard, anything won't work. So I press the reset button. BootBlock shows up again. After 5 minutes with combinations of pressing Reset and turning power off and then on, it finally booted up fine.

What would cause this weird error when there actually isn't an error? Also why would it just freeze like that (2nd time it's happened)? This machine has run a week straight before.

Specs:
Abit BE6 mobo
Celeron 366@550
128MB RAM (it's ECC (somehow) and currently I think BIOS has Non-ECC setting)
10GB Harddrive on Highpoint HPT366 controller
SiS 900 NIC
Realtek NIC
Voodoo 3 2000 PCI
300W Enlight PSU
Win2k Adv. Server OS (Runs DHCP, Routing, Print Serving, and ZA Pro)

LMK if more info is needed.

Posted: Sun Feb 10, 2002 12:18 pm
by PreDatoR
Only time i've seen something like that was on my Iwill KK266 when i was overclocking an had a failed attempt... To get rid of it i had to clear cmos... To me it sound like A. you bios is going. B. A setting the bios isn't agreeing with something else on bootup.. You might try clearing CMOS and setting the bios up again and see if that helps... Or try flashing the bios again. Hope this helps.

Posted: Sun Feb 10, 2002 12:43 pm
by chottoED
I got that message when my BH6's BIOS went south.

Posted: Sun Feb 10, 2002 2:18 pm
by Busby
The thing is it works perfectly fine 8 or 9 times out of ten. I had to change cases so I reseated all the different stuff (CPU, Mem, etc.) and so far (about 3 or 4 reboots) haven't gotten the error. I am overclocking but that Celeron has been going strong for a little over 2 years at that speed. I did lower the VCORE to 2.05 instead of 2.1 but I changed that back today (forgot I changed it).

Posted: Sun Feb 10, 2002 2:22 pm
by DocSilly
Maybe a dying CMOS battery? They only last 2 or 3 years ...

Posted: Sun Feb 10, 2002 2:40 pm
by TruckStuff
As much as I hate to say it, the overclocking may be part of the problem. I have a 700E that was chugging along just fine at 933 for months. Then one morning it just decided that it didn't want run at 933 anymore. Half of the time it would work fine, the other half it wouldn't work at all. I backed it down to stock (painful, I know), but its worked fine ever since.

Posted: Sun Feb 10, 2002 3:06 pm
by Busby
The CMOS settings keep in tact through all of this. Wouldn't a dying battery cause a loss of settings?

On the overclocking issue: I doubt seriously that is the problem but if it happens again I might try it out.

I think that could have just been a loose contact between the mobo and the CPU or mem and since everything was reseated I'm hoping it'll be solved (cause it did start happening after I had taken it w/ me to a friend's house.

Posted: Sun Feb 10, 2002 5:35 pm
by FlyingPenguin
Basically something is corrupting the CMOS settings.

Overclocking or it's overheating probably.

Posted: Tue Feb 12, 2002 10:40 pm
by TruckStuff
Originally posted by Busby
On the overclocking issue: I doubt seriously that is the problem but if it happens again I might try it out.
That's what I said when my system started wigging out on me. ;)

Posted: Wed Feb 13, 2002 10:56 am
by Kakarot
He's in denial. :P

Posted: Wed Feb 13, 2002 1:06 pm
by Busby
Well after moving parts around and reseating while moving, so far no lockups or errors so again I doubt it's the overclocking.