Help! ... bios checksum error

[slpavman]

When my son turned his comp on this morning it wouldn't boot. All it does is go to a screen that says:

Award Bootblock bios V1.0

Bios checksum error

Detecting floppy drive A media...
INSERT SYSTEM DISK AND PRESS ENTER

I inserted a Win98 boot disk and pressed enter, unplugged all drives, cleared the CMOS with the jumper, removed the CMOS battery for 30 seconds, removed the 2 SDRAM blocks (it then beeped several slow beeps), tried all combinations of SDRAM, pulled the CPU and HSF and reseated them ...

I tried to reboot after every change, the error message never changed....
I've used up all my "tricks" ! Anyone else have an idea?

My system specs:
AMD T-bird 1.0ghz with a SuperOrb HSF
Epox 8KTA3 (new bios about a month ago)
(2) 128mb sticks of Mushkin Rev3
Geforce MX400 (about 2 month old drivers)

Any suggestions will be appreciated!

 

[sohcrates]

try removing the battery for at least 1/2 an hour, and make sure computer is unplugged from wall

checksum errors are almost always fixed by clearing the bios one way or the other

let me know if that doesn't work

 

[morkinva]

Methinks you have a trashed bios, either by a bad flash or virus. It's booting to the floppy to find the files to flash the bios.

If sohcrates suggestion doesn't work, I think you'll have to try to reflash

Good luck

 

[bozo1]

Have you actually gone into the BIOS setup? Checksum error means that the saved data was wiped/trashed for whatever reason. You will continue getting that message until you actually go into the setup, set your options properly, let it detect your drives, etc., SAVE the settings and exit. On many board, clearing the CMOS will prompt the checksum error as their way of forcing you in there to reset the options you just cleared.

 

[slpavman]

I can't get into the bios set-up. I hit delete (repeatedly) as soon as I turn it on, but it still goes to the screen I copied. I tried to reflash anyway, by making a new flash-disk (with latest bios), but I don't think it's even really reading the A: drive (even though the drive DOES make sounds like it is....)
I'll try leaving the battery out for at least 30 mins (I thought 30 seconds would be sufficient).

PS I didn't know that a virus could mess up the bios! As a matter of fact after doing a little more investigation ... I found out that my son's friend (...hmmmm?) was on Kazaa (actually not d/l just importing files from the HDD to "My Kazaa" ) last night when they started to get a bunch of strange screenies ... and it said it was copying like 7000 files or something ... so they tries to escape and then rebooted and when it came back it had the error message I posted and wouldn't go any further ...

 

[slpavman]

Any other ideas?

 

[tbalon]

Almost sounds like a virus may have tried to reflash your BIOS for you.... Have you tried the following?

(copied from EPOX website)

BIOS Update Instructions

There are two ways in which we recommend to flash the BIOS. They will be termed as follows:

. The ALT+F2 Method
. The Boot Disk Method

The ALT+F2 method may not be available on older mainboards with older BIOS, in such cases it is necessary to carry out the Boot Disk Method.

----------------------------------------------------------------------

The ALT+F2 Method

1. Download the required BIOS image file from the EPoX website.

2. Copy or extract the BIOS image file (named xxxxxxxx.bin) to a blank floppy disk with no bad sectors on it.

3. Restart the machine with the floppy disk in the floppy drive. When prompted at machine initialization, press ALT+F2 to begin performing the flashing of the BIOS.

4. The BIOS will automatically flash and reboot the machine.

5. After this, press DEL to enter the BIOS setup and select to "LOAD OPTIMIZED DEFAULTS". After doing this select to "SAVE & EXIT."

6. Please note that this does not create a backup of the BIOS binary file.

7. This does not require you to have a bootable floppy disk.

----------------------------------------------------------------------

The Boot Disk Method

1. Create a bootable floppy disk in accordance with the instructions laid out in the manual of your particular operating system. This bootable floppy needs to be able to boot to a DOS console capable of executing normal MS-DOS batch and executable files.

2. Download and extract the xxxxxxxx.EXE file corresponding to your model from the EPoX website to the floppy. It will self extract into the above listed files.

3. Boot using your DOS floppy disk to the ?A:\>? command prompt. At the DOS command prompt type: UPDATE

4. The BIOS will automatically flash.

5. Reboot the machine.

6. After this, press DEL to enter the BIOS setup and select to "LOAD OPTIMIZED DEFAULTS". After doing this select to "SAVE & EXIT."

Note: During the use of UPDATE a backup of your original BIOS date/code will be saved in the same directory as the UPDATE file. It will be called ?OLD.BIN? and can be used with the restore instructions below in case you need to revert back to the original BIOS date/code.

----------------------------------------------------------------------

BIOS Restore Instructions

Use of the restore procedure requires the OLD.BIN file created in the Boot Disk method procedure above!

1. Boot using your DOS floppy disk to the ?A:\>? command prompt. At the DOS command prompt type: RESTORE

2. The BIOS will automatically flash.

3. Reboot the machine.

4. After this, press DEL to enter the BIOS setup and select to "LOAD OPTIMIZED DEFAULTS". After doing this select to "SAVE & EXIT."

5. The system flash is now completed and should now be reverted back to the original BIOS date/code.

----------------------------------------------------------------------

BIOS flash failed

If you have access to an old un-accelerated ISA video card, you might be able to recover your BIOS. Remove all cards and drives from your system, except for the ISA video card and the floppy drive. Then try to boot from a system disk (a bootable floppy with only the flash programs and corresponding BIOS binary). If you are able to boot to the floppy, flash your BIOS according to the directions above.

 

[tbalon]

If the above doesn't work for you, I would have to suggest that you try a "hot flash" of the BIOS chip in another machine.

 

[tbalon]

Also came across this on EPOX website:

''Everytime I boot the system I get a checksum error and I have to reset the BIOS ''
Location: Knowledge Base
Article #: 1149
Product: EP-MVP3G-M (1Mb)
Processor: AMD K6-2/450
Memory: 64MB
Hard drive: Western digital Hard drives
Operating System: Windows 98 4.10.1998

ISSUE REPORTED BY CLIENT

Almost everytime I boot the system I get a checksum error and I have to reset the BIOS.

POSSIBLE SOLUTION

Try entering the CMOS, load the defaults, then Save and Exit. Also try remounting the motherboard in your case and also remove all cards except for the video and retest. This can help narrow down what is causing the issue.

-Customer response-
Found the problem, the clip that holds the battery is loose. I was able to fix the clip.

 

[NewSilkTurtle]

Interesting problem. I also had serious problems after trying to use Kazaa. The checksum error could be as simple as a low/dead battery in the mobo, too.

 

[slpavman]

Okay ... any ideas that have "when you get to the A: prompt" are out ... I never get that far. I can't hot boot since I don't know anybody around here with that bios chip. If anyone knows anything about Epox mobos... I get hung at code 41 on the mobo LED which is " If auto-configuration is enabled, program chip-set with pre-defined values". I'm pretty sure ACPI is enabled, but I have no idea how to program chipset with pre-defined values ...
I will try and find a PCI vid card, I probably have one laying around somewhere. I will also change the battery for the CMOS (but the old one reads 3.1vdc and it's a 3vdc battery).
I saw that alt F2 procedure at Epox, but I didn't think it would work since I can't seem to get it reading from the A: drive, but what the heck - what do I have to lose by trying it at this point? Thx!

 

[slpavman]

Nope! None of that stuff worked. I did get in touch with Epox tech support this morning and by afternoon I had an e-mail saying they had mailed me a new BIOS chip They asked me to send back the old one upon receipt, I figure it's the least I could do! Not bad! One day response and a free BIOS chip for a mobo that's 6 months past warranty. I'll have to put them on my "good guys" list, no doubt!

 

[tbalon]

Please let us know if this solves your problem. It is nice when companies appreciate their customers.....

 

[shathal]

Tech support folks generally try to bend the rules a little. It's not as if we're out there to ruin everybody's live's. It's just nice to be appreciated in return every now and then. That certainly happens rarely enough ...

 

[slpavman]

I have written commendatory letters about what I considered outstanding customeer support on several occasions. I have also sent very scathing letters of reprimand for support that I thought deseved it! That's why I always get the techs name when I get through to support. I want to be able to give credit or condemnation where deserved!

I will certainly post back the results (either way) after I replace the chip. Thx for all the ideas (at least it kept me busy and kept my mind off it ... and you never know - SOMETHING might have worked!)

 

[slpavman]

You have got to be kidding me !!!!!!!!!!! I got the new BIOS chip from Epox today, cleared the CMOS, pulled the old BIOS chip, pulled the battery, put the new BIOS chip in, put the battery back in, un-jumped the CMOS, put a boot disk in, powered up and SAME FREAKIN ERROR MESSAGE !!! Now I'm really lost! What the HE!! else can cause a BIOS Checksum Error! The only thing possibly left (as far as I can tell) is replacing the whole damn mobo! If anyone has any other ideas .... PLEASE help!

 

[DaiShan]

Try the memory, I have heard that checksum errors are the result of bad memory, you should try swapping out with some known working memory.

 

[Golio]

Did u look the POST code on the motherboard? What it could say?

If not done, try unplug everything not vital on the machine.
Try to change your bios battery, even if i dont think its the pb cause u have
changed your bios chip yet.

For information, one virus attack the BIOS. Its name is CIH, or Hiroshima.
It can destroy BIOS by flashing it with other datas than the BIOS program.

Nico

 

[Golio]

Sorry, didnt see one of your post...
You tryed everythings i would tryed... It could be interesting
to have the Epox test result. Maybe its one of your motherboard chips.

Nico

 

[slpavman]

... Epox tech support says I need to take my board back to where I purchased it ... Nope, it's past warranty and would almost certainly cost more to fix than to buy new one! Oh well ... I can't see how it could possibly be fixed by anything less than a mobo replacement at this point :-(
Thx to everyone for trying to help ...

 

[DaiShan]

Where did you buy it? Can you try to RMA it to them?

 

[slpavman]

I bought it 18 months ago and it's a 1 year warranty ...

 

[slpavman]

One of my old geek friends just happened to get in touch with me and I told him what was going on. He said checksum errors are caused by memory probs, when I tried to explain that I already tried all the memory stuff he said "NO, the CPU onboard memory - I think it's the L2 cache". Oops!
The new mobo came today, before I installed it I figured I'd swap the old CPU out - just in case he was right .., sure as crap! As soon as I installed it and booted up "Bingo", I'm in Windows! Now I'm freaked! I just bought a new mobo and the CPU was bad! I cleaned up the old CPU, and just for S and G's I decided to try the old CPU again and "Wallah"! IT freakin works too!
So now what do I do? (between the 2 comps) I have a brand new mobo (and 2 good ones), 2 good CPUs and a questionable spare ... crap! I decided to hold on to the new mobo for a while, just in case ...
I hate PFM (pure freaking magic) repairs! I have no clue what the original problem was! (and oh, btw I figured out that the floppy drive HAD gone south on me sometime during all this crap!) Maybe why I couldn't reflash the BIOS or boot-up?......Maybe the Arctic Silver thermal compound I used shorted out something on the orig CPU, causing the orig prob!? WhoKnows!?

Anyway, I apologize to anyone who suggested it might be a CPU problem (and I kind of blew them off because I THOUGHT I knew better) :-( I would have bet anything that the dang BIOS chip was bad! The floppy drive failing in the midst of this really caused me some hardship too!

Well THX AGAIN! To everyone who helped me with this.

 

[slpavman]

A follow on note... I thought that the floppy drive had gone bad, but when I swapped in a known good one, the problem still existed! So, it turns out that the Floppy controller on the mobo was bad! I swapped out the mobo a couple of days ago and so far everything is working perfect. Hopefully EVERYTHING is fixed now, otherwise the next step is start from scratch on a new computer!

Thx again to everyone for their help!