CMOS Checksum Error – Defaults Loaded

Fix BIOS CMOS Checksum Error on Boot – Step by Step

Hardware – RAM & MB Beginner 👁 9 views 📅 Jun 17, 2026

This error means your CMOS battery is dying or your BIOS settings got corrupted. Here's how to reset it and get your PC booting again.

Quick Answer

Replace the CR2032 battery on your motherboard, then load BIOS defaults. That fixes 90% of these errors instantly.

What’s Actually Happening?

You see that dreaded message — CMOS Checksum Error – Defaults Loaded — and your PC won't boot properly. I’ve seen this a thousand times. It’s your motherboard telling you the settings it saved in the CMOS memory don't match what it's reading now. Usually, it's a dead CR2032 coin cell battery. That little battery keeps your BIOS settings alive when the PC is off. When it dies, the checksum — a simple mathematical check — fails, and the BIOS falls back to factory defaults. But here's the thing: sometimes it's not the battery. A power surge, a bad overclock, or even a static shock can corrupt the stored settings. I've also seen this happen after a BIOS update that got interrupted. So before you panic, know this: it's almost always fixable in under 10 minutes.

Fix Steps – The Main Fix

  1. Power down and unplug everything — including the power cord from the wall. Pull the battery out of the motherboard (it's the silver coin cell, usually CR2032). Wait 30 seconds. This fully drains any residual charge. Put the battery back in.
  2. Boot the PC and immediately press Del or F2 (depending on your motherboard — check the splash screen). You'll land in the BIOS.
  3. Load Optimized Defaults — it's usually an option like Load Optimized Defaults or Load Setup Defaults. Hit Enter, then F10 to save and exit. If the PC boots to your OS, you're done. The error won't come back if the battery is good.

Alternative Fixes (If the Main Fix Fails)

Try a Different Battery

If the error returns after a few days, the battery is dying. Replace it with a fresh CR2032 from a drugstore or electronics shop. I keep a pack of Energizer CR2032s in my toolkit — they last 3-5 years in a motherboard. Don't use cheap no-name batteries; they leak voltage faster.

Clear CMOS with a Jumper

Some boards need a jumper to fully clear the CMOS. Check your motherboard manual for a 2-pin header labeled CLR_CMOS or JBAT. With the PC off and unplugged, short those two pins with a screwdriver for 10 seconds. Put the jumper back to the normal position (usually pins 1-2). This forces a deeper reset than just removing the battery.

Check for Physical Damage

I've seen swollen capacitors or bent pins on the battery holder cause this. Inspect the CR2032 holder — if the metal contacts are bent or corroded, carefully bend them back with a plastic spudger. A little isopropyl alcohol on a cotton swab can clean off corrosion. If the holder is cracked, you'll need to solder a new one or replace the motherboard.

BIOS Update Gone Wrong

If this happened right after a BIOS update, reflash the BIOS. Download the latest stable version from the motherboard vendor using another computer, put it on a FAT32 formatted USB drive, and boot into the BIOS flash tool. If your board has a dual BIOS feature (like some Gigabyte boards), try the backup BIOS — there's usually a switch on the board to toggle between them.

Prevention Tips

  • Replace your CMOS battery every 3-4 years as routine maintenance. I mark the date on the battery itself with a Sharpie.
  • Always shut down your PC properly — don't yank the power cord. Sudden power loss can corrupt BIOS settings.
  • If you overclock, save your profile in BIOS after stability testing. Then if you get a checksum error, you can reload it fast.
  • Use a good surge protector or UPS. Power spikes can zap the CMOS memory instantly.
  • When updating BIOS, never turn off the PC. Wait until it finishes and reboots naturally. A failed update is a nightmare to recover from.

In my years running a help desk, I'd say 8 out of 10 CMOS checksum errors are just a dead battery. The other 2 are corrupted settings from a crash or bad update. Either way, this fix works every time.

Was this solution helpful?