CMOS Checksum error (Biostar motherboard)

[billmurray22]

Hi all,

Building a computer and using a new Biostar M7SUA (M7VKQ Pro)
motherboard. I get the following error on every bootup (right out of
the box):

"CMOS Checksum error - Defaults loaded. Warning, your CPU has been
changed. Please setup CPU HOST clock in Chipset features setup."

10 seconds after entering CMOS setup, all the words and numbers on the
screen become jumbled and my system locks up. What's more, if I
reboot I get the same error message above and I can't get back into
the CMOS without cracking the case and clearing the CMOS using the
jumper.

Award (BIOS manufacturer) says the above error could be due to a
faulty battery or corrupt CMOS chip--I'm thinking the latter. I'm
waiting to hear back from Biostar, but in the meantime, has anyone
else seen this issue? Or does anyone have any ideas?

TIA,

~Bill

 

[JAD]

pull the battery pull the plug short the cmos jumper....2minutes return battery plug in boot...cross fingers

hth

 

[LeeB18509]

Hi all,

Building a computer and using a new Biostar M7SUA (M7VKQ Pro)
motherboard. I get the following error on every bootup (right out of
the box):

"CMOS Checksum error - Defaults loaded. Warning, your CPU has been
changed. Please setup CPU HOST clock in Chipset features setup."

10 seconds after entering CMOS setup, all the words and numbers on the
screen become jumbled and my system locks up. What's more, if I
reboot I get the same error message above and I can't get back into
the CMOS without cracking the case and clearing the CMOS using the
jumper.

Award (BIOS manufacturer) says the above error could be due to a
faulty battery or corrupt CMOS chip--I'm thinking the latter. I'm
waiting to hear back from Biostar, but in the meantime, has anyone
else seen this issue? Or does anyone have any ideas?

TIA,

~Bill

I had the same thing happen to me. All I was doing was replacing a cpu with
the original that ran in the mobo for a year. Tried a new battery, didn't
help. I think the error can occur when there's something hosed between the
cpu and ram. Anyway, I would get all kinds of different boots, different
cpu speed shown, sometimes I could get in the BIOS, other times not.

All I did was remove the heatsink, recheck everything and reinstall the CPU
and it all went away and ran fine after that. I guess it just didn't like
the way it was sitting in the socket. Weird...HTH.

 

[billmurray22]

I had the same thing happen to me. All I was doing was replacing a cpu with
the original that ran in the mobo for a year. Tried a new battery, didn't
help. I think the error can occur when there's something hosed between the
cpu and ram. Anyway, I would get all kinds of different boots, different
cpu speed shown, sometimes I could get in the BIOS, other times not.

All I did was remove the heatsink, recheck everything and reinstall the CPU
and it all went away and ran fine after that. I guess it just didn't like
the way it was sitting in the socket. Weird...HTH.

Thanks for the replies, I will try those suggestions--for some reason
removing the heatsink and reseating the CPU sounds very promising.
Any other ideas from anyone else?

 

[Andrew]

CHECK the CMOS settings for your MEMORY's speed! I have a M7VIZ and an
running the 1800+ (a 266 CPU) with DDR333 memory. The "optimal" CMOS
setting sets up 333 but the CMOS gets funky and booting is unreliable. Once
I set the DRAM to 133 it's running STABLE!!!

Andrew