IS7 cmos checksum error

Status
Not open for further replies.
Joined
Jul 10, 2003
Messages
2
Reaction score
0
Hi,

This is going to be a long question. Sorry about it, but I hope someone can help me.

I just assembled my computer (the typical P4 machine that everyone is getting now : P4 2.4Ghz with HT and 800fsb, Abit IS7, dual channel 256MBX2, and other accessories).

I first booted the comp and it seemed normal. I went into setup and did a few configurations which includes setting drive a: to None because I didn't have one. I saved the changes and computer re-booted. Then suddenly, I got these really disturbing beeping noises and a screen that says cmos checksum error and also something like Drive A:
Not Found error. I had to cut the power to shut it off. I cleared cmos and rebooted, but same thing happened.

After a few tries, I actually did get it to load a system disk (Windows 2000) but it says it cannot find some .exe file. Restarted and it couldn't find the .exe file again. So I shut down (cut power), but then remembered I left the cd in the cdrom. So I turned it on again to get the cd and cut power again. That's when everything fell apart. Is it possible that by doing this, I screwed up the cmos??

This is what happens after : Clear cmos. Boot machine. Went to setup. Changed drive a floppy to None. Saved and reboot. Then "BeepBeepBeepBeepBeepBeepBeepBeepBeep..."(with cmos checksum error and drive a not found error). [Repeat from clear cmos]. ..

So I got fed up and plugged in a floppy, the Drive A: error was gone, but the cmos checksum error was still there. I flashed the bios to version 13 but nothing changed.

A friend says it's not possible to screw up cmos with what I did. He says it's probably already screwed up. But why was I able to load the system disk that time (it was actually a few times that I was able to load system disk) ? I have no idea what's going on. If anyone has any suggestion(s) as to what I can do, it would be really appreciated. Thanks!
 
"red_riding_hood" wrote:

Hi,

This is going to be a long question. Sorry about it, but I hope someone can help me.

I just assembled my computer (the typical P4 machine that everyone is getting now : P4 2.4Ghz with HT and 800fsb, Abit IS7, dual channel 256MBX2, and other accessories).

I first booted the comp and it seemed normal. I went into setup and did a few configurations which includes setting drive a: to None because I didn't have one. I saved the changes and computer re-booted. ...

Sounds like its already screwed up to me, check your vbat voltage, and if thats normal (+- 0.3v from 3V) then u probably should return the board
 
just to be safe, try the board out of the case on a safe, non-conductive work surface. even if you set newspaper on top of your case and hook up the PC connectors (yes, remember BOTH connectors). you don't need anything else but CPU, RAM and video card and a KB if you want to be able to get into the bios setup. see if it acts the same way as it was when it was mounted up and if so, something is definitely screwy with that board...
 
Did you do a fresh Windows install, or are you trying to use a hard drive with an OS already installed from another system?
 
help me here... how is an attempt at reusing a previous OS going to have any impact on getting a checksum error from the bios? the checksum error is declared before the system even completes a POST process and starts the boot, right?
 
Thanks everybody for the response.
Someone suggested that I replace the mobo battery with a "known" working one, so I think I'm going to take it back to the store to have them test if it's the battery that's causing the problem.

And about the hard drive, it's a brand new one...but as TomG said, it's not related to the checksum error...

"TomG" wrote:
help me here... how is an attempt at reusing a previous OS going to have any impact on getting a checksum error from the bios? the checksum error is declared before the system even completes a POST process and starts the boot, right?

--

Thomas Geery
Network+ certified

ftp://geerynet.d2g.com
ftp://68.98.180.8 Abit Mirror <----- Cable modem IP
...
 
Hi
I had some problems getting my IS7E kicked off and finally I did a Clear CMOS, using the jumper on the main board, just change the jumper for a few seconds, put it back and do a reboot, you lose all your setting, but It really doesn't take long to put them back.

I had the same problem when I moved from a parallel IDE to two SATA drives, nothing I did would enable the new SATA config, I did a CCMOS and it all powered up a treat.

It only takes a minute or two and cant hurt to try.

Good Luck
Jerry

"red_riding_hood" wrote:

Hi,

This is going to be a long question. Sorry about it, but I hope someone can help me.

I just assembled my computer (the typical P4 machine that everyone is getting now : P4 2.4Ghz with HT and 800fsb, Abit IS7, dual channel 256MBX2, and other accessories).

I first booted the comp and it seemed normal. I went into setup and did a few configurations which includes setting drive a: to None because I didn't have one. I saved the changes and computer re-booted. ...
 
help me here... how is an attempt at reusing a previous OS going to have any impact on getting a checksum error from the bios? the checksum error is declared before the system even completes a POST process and starts the boot, right?

To be perfectly honest with you, Tom, I'm not exactly sure. Thinking it through further, I have to concede that it doesn't really make sense.

One thing I do know for sure is that the only time (in over 25 builds) that I have ever seen a "checksum error" before a complete POST was about 3-4 years ago when I moved a hard drive from an Intel chipset based system to a VIA chipset based system without reinstalling the operating system. Reformatting the drive and a fresh Windows install seemed (at the time) to get rid of the problem. However, maybe the BIOS didn't detect the HD properly, or maybe I swapped RAM somewhere in the process. Who knows? The motherboard was one of those cheap PC Chips brand that most people wouldn't take for free, so I guess anything goes with that crap.

Looks like my attempt at a diagnosis was off track with this one, so thanks for straightening me out. :)
 
If it turns out to be the battery or the motherboard - be sure your not accidently shorting out the battery during installation into the case. The terminals to the battery are often exposed on the back side of the board.

Forrest

Motherboard Help By HAL web site:
http://home.attbi.com/~hal-9000/

On 11 Jul 2003 07:00:03 -0700,
(red_riding_hood) wrote:

Thanks everybody for the response.
Someone suggested that I replace the mobo battery with a "known" working one, so I think I'm going to take it back to the store to have them test if it's the battery that's causing the problem.

And about the hard drive, it's a brand new one...but as TomG said, it's not related to the checksum error...

"TomG" wrote:
help me here... how is an attempt at reusing a previous OS going to have
any impact on getting a checksum error from the bios? the checksum error is ...
 
agreed. that is why I made the recommendation to try the system out of the case...
 
Right-ee-oh Tom. Just explaining so that it might not happen a second time...

Forrest

On Sat, 12 Jul 2003 08:08:31 -0400, "TomG"
wrote:

agreed. that is why I made the recommendation to try the system out of the case...
 
right! I wasn't trying to say anything other than I agree with you completely.
 
Status
Not open for further replies.
Back
Top