BIOS Checksum Error

Lantoka

Weaksauce
Joined
Jun 13, 2004
Messages
71
Hey guys,

I just finished building my new computer, and booted it up for the first time. It's running on an Abit IC7-G mother board that I bought newly purchased from NewEgg. Unfortunately, when booting up, it's dispaying the following.

Award BootBlock BIOS v1.0
Copyright (c) 2000, Award Software, Inc.

BIOS ROM checksum error

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

I see that and go... where the heck is my BIOS? A friend recommends putting the XP CD in, and I try that. No go. So I try the floppy that came with the mobo, which has the SATA drivers on it. No go.

So then I go to the Abit website and download the BIOS onto a floppy.
http://www.abit-usa.com/downloads/bioshelp.php
http://www.abit-usa.com/downloads/bios/bios_revision.php?categories=1&model=4

I insert that disk, and I find that it runs AWDFLASH.EXE automatically. (When trying with that other disk, it asked for a disk with that file. I assumed it was the BIOS update file, which appears to be correct. It won't let me run any other file or use any other optical drive at this point.)

This takes me to a screen that looks like this.

AwardBIOS Flash Utility V8.32
(C)Phoenix Technologies Ltd. All Rights Reserved

Flash Type -

File Name to Program : ______________________






Check to see if FDD & HDD error occured


Message:

Several problems here. 1) My keyboard has mysteriously stopped working at this point. 2) I have no idea what the "flash type" is, nor what file name I should program. 3) It just sits here and does nothing.

After this, I figured that maybe it installed on its own or something and just locked up there at the end, so I reset my CMOS using the jumper cables on the board. A minute and a boot up later, the same thing.

So... no BIOS, no way to install Windows, no way to run anything! What do I do? :(
 
Ignore the bios flashing for now.

If you can get into the bios, load the setup defaults, and or optimized defaults (depends on board what its called) save and exit bios, jump right back into the bios on next post and go into the advanced bios features, if you havent installed XP yet, set first boot devices as CD Rom, second boot device as HDD 0.

One thing of note on that, if you have onboard SATA and your using that for your boot drive, set the second boot device to SCSI, and there should be another section for enabling or disabling the onboard SATA.

If you can't get into the bios, shut it off, unplug it, use the CMOS reset jumper and then proceed as above.

Note that depending on your CPU you may need to manually setup the FSB and Memory timings.
 
What I posted above is exactly what I see. As far as I can tell, there's no way for me to either continue the boot sequence or get to the BIOS.
 
Lantoka said:
What I posted above is exactly what I see. As far as I can tell, there's no way for me to either continue the boot sequence or get to the BIOS.

Ok do a CMOS reset with the jumper. If you happen to be using a wireless or usb keyboard, plug in an old style keyboard into the mouse PS2 port, that will sometimes help.
 
I'm using a standard PS/2 keyboard, and I already reset the CMOS with the jumpers.

I'll try again, however.

edit: Same as above after reset.
 
Be sure when you do it, that you unplug the power, and move the jumper over for at least 30 seconds, move it back and then repower it.
 
Oh... didn't unplug the power. Trying again.

edit: Didn't work. Same as above.
 
One trick that you can use to make sure that there is no residual power in the system is after you unplug it hit the power button, it will discharge any residual power held in the system, then proceed with the cmos jumper.
 
Try a different keyboard if you got one floating around, allways the posibility that that one toasted.

Other than that I don't have much more to try.
 
This keyboard works with the other comp from which I grabbed it just fine.

I tried powering down and doing the reset again, making sure to hit the button first. No go.

*sigh*

All that work to build my first computer and a software problem brings me down. :(

Any other ideas, guys?
 
short beep and long beep could indicate a ram problem try swappin sticks

if you can't get at least the keyboard workin it looks like its near time to either RMA the board or at the very least find somebody to flash the chip locally or online for you
 
your probably not passing the POST (Power On Self Test)
so look up that beep code and try to resolve that first
a checksum error simply means it lost whatever settings there where
and its back to an original state, happens when you remove the battery,
clear the CMOS or after a flash
and when your battery is toast as well, or loose in the socket

I have a keyboard stashed away for AT, PS2 and even a serial mouse, just incase
like Sniper_Merc pointed out its likely RAM or the Video

however
Unfortunately there are many versions of the Award BIOS, and they are supported not by one company, but by the motherboard maker. Award's website states "Award Software software products are sold to a board or system manufacturer ("hardware vendor"), who customizes them further before selling the system. Award Software cannot supply upgrades for a BIOS that has been subsequently modified by hardware vendors."
so check the manual for the beep code of that board
 
I'm currently getting some limited help on the ABIT forum. That at least has identified the problem, which is simply a bad BIOS. The RAM and video card seem to be working fine.

http://pages.sbcglobal.net/jefn/bootblock.html

BootBlock appears to be the program that comes up on newer ABIT motherboards when the BIOS is corrupted. Not much more to it.

Now, the procedure outlined above is for trying to flash the BIOS in order to update the corrupted version with a newer one. My problem is that it hangs up once AWDFLASH.EXE is run. I lose my keyboard at that point, and it just sits there.

I downloaded the mobo manual from online. It does not contain the beep codes.

I'm running out of options, and I think this flash is the key to the whole thing. How do I get the stupid thing to work? :(
 
damn that sux

try to cross verify your RAM in another machine

try rebuilding the floppy with DrDOS
it lacks the memory managers like himem
and is specifically built with BIOS flashing in mind
get a new floppy, and redownload all the utilities and BIOS
and make sure it the right BIOS for the board
it sounds like the wrong BIOS may have been flashed the first time round

and try again

past that, there are 3 options
get a new EPPROM from a 3rd party or the mobo manufacturer
(sub option buy a dual EEPROM like the BIOS Savior preprogrammed)
send your EEPROM out to have it reflashed
hot flash the EEPROM from an identical mobo (risky to both )

you say the RAM and Video are OK
are you stll getting beeps?
 
I get beeps only when I don't have the diskette with the flash in the drive, or if I insert the wrong diskette. If I have the diskette in from when I turn on the computer, I get no beeps and it goes right to the program. For that reason, I don't think other hardware is to fualt.

My dad just pointed out that the "Check to see if FDD & HDD error occured" message above may not be an option as I originally thought, but a message signifying an error. With that information in mind, any other ideas?
 
got to fly got 6 border collies mugging me for a walk
but check your jumpers and cbales, specifically that the masters are at the end, and that there is no master with slave present when there isnt and vice versa


also verify the FDD cable is correctly attached
does it light? when the floppy is in?

will be back this afternoon
 
My floppy seems to work fine. The little LED on the floppy lights up when it reads the disk.

My HDD is a newly purchased Western Digital 250GB 7200RPM SATA, hooked up to SATA1 on the mobo. I don't think that this little emergency program could access it because of that configuration, although it's displaying the error for it anyway. The HDD is blank and considering that this comp has never successfully booted up, shouldn't have any info on it.

So... why would it be displaying an error for it? =/

edit: I just felt my HDD after leaving my comp on for several minutes. It's not warm at all. That HDD error is because the HDD isn't functioning. I don't see why it'd need to, but it's generating an error nonetheless. Should I try to correct that before reflashing with a new disk and all of that?
 
Okay, I used DrDOS to format another floppy. The file system changed from FAT32 to FAT. I then put the necessary files on the floppy and ran it on my computer. It is now getting stuck in the same place, except the HDD / Floppy error is gone. I'm going to wait and see if it does something or not, but once again, it appears to be stuck. It's not currently reading from the floppy or anything. ^_^
 
Somebody recommended that I swap AWDFLASH.EXE with AWDFLASH.EXE version 8.22a.

I got that to run... w00t!

Then it restarted itself, and stopped itself at "Detecting floppy drive A media..."

So I proceeded to clear the CMOS again.

I reboot, and it's still giving me BootBlock, with one exception. It's no longer trying to read a disk. It gets stuck at "Detecting floppy drive A media..." and does nothing.

What do I do at this point? It looks like the BIOS didn't install correctly and that I can't try again because BootBlock won't accept the disk... uuugh! ^_^
 
looks to me like you either misinserted the floppy cable, or the keyboard controller on mobo is dead or.....many output shields in the back dont line up with mobo i/o ports like mouse and keyboard so they dont go all the way in when you push them, so make sure they are not partially inserted.
 
I'm sending the mobo back to NewEgg for a replacement. I received assistance on the ABIT forum and they've confirmed that there's nothing I can do at this point. ;(

Thank you for all of your help, you guys! :)
 
If someone else has problems with a bad flash in an older motherboard out of guarantee, he / she can purchase the RD1 BIOS Savior which can save you from a lot of trouble :)

Oh and here's the link
http://www.ioss.com.tw/eg/
 
most of the time

I have one in my KR7A
but there are alot of EEPROMs out there
and some mobos arent covered, like my workstation
 
Back
Top