Anybody know what causes this? I've been having some random crashes. When i can finally get the post again it will say CMOS Checksum error in the post screen. I'm putting this in the CPU forum instead of the mobo forum because it only happens with my 3.2E. I have a 3.2C it doesn't happen with. ANy ideas?
![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
-
A Great friend to the HardForum with a great kid that he is trying to get a scholorship to continue his schooling. Please give hime a vote! Only 24 hours left! Thanks.
If you have an VOTE FOR KEENAN!
CMOS Checksum Error
- Thread starter pigpen
- Start date
S
SirKenin
Guest
I would flash the BIOS myself.
It's the latest BIOS. I was using the 3.2E on this mobo (same BIOS) only a few months ago with no problems. Switched it back in and all of a sudden had this strange crash and error. THe point of the thead was more to see if anybody actually knows what CMOS checksum error means. I'm thinking it has something to do with an inability to access something CPU related, but i'm not sure.
The_Mage18
[H]ard|Gawd
- Joined
- Jul 31, 2004
- Messages
- 1,712
Loose definition: A CMOS checksum error occures when there is faulty circuitry in the motherboard between the Northbridge and the CPU or a faulty/unsupported CPU. What happens is when the system is powered up, the BIOS micro-code is read, decompressed and executed. A checksum error occures when the decompression fails the check (binary math here. 0+0=0, 1+0=0, 1+1=1).
Lamen's terms the POST more or less completed successfully but when the BIOS was decompressed and attempted to be run, it failed the check (ie the double check ended with something like 1+1=0 which is wrong) so an error is displayed on the screen and the system halts since it can't execute the instructions in the BIOS to continue.
You already proved it's not the motherboard since it works fine with your 3.2C chip and if it has the latest bios already and does support the 3.2E, then the 3.2E is defective.
Lamen's terms the POST more or less completed successfully but when the BIOS was decompressed and attempted to be run, it failed the check (ie the double check ended with something like 1+1=0 which is wrong) so an error is displayed on the screen and the system halts since it can't execute the instructions in the BIOS to continue.
You already proved it's not the motherboard since it works fine with your 3.2C chip and if it has the latest bios already and does support the 3.2E, then the 3.2E is defective.
