You're staring at a black screen with STATUS_FAIL_CHECK (0XC0000229) and the words "A consistency check failed." I know that sinking feeling — your PC won't boot, and you're probably mid-work or mid-game. Let's get you back in. The fix is almost always a corrupted Boot Configuration Data (BCD) file, and we can rebuild it in about ten minutes.
The Fix: Rebuild the BCD with Bootrec
You'll need a Windows installation USB or DVD. If you don't have one, you can create it on another working PC using Microsoft's Media Creation Tool (search "Windows 10 download" or "Windows 11 download"). Grab a USB stick with at least 8 GB — everything on it will be erased, so use a spare.
- Plug the installation drive into your broken PC. Turn it on and press the key to open the boot menu. That's usually F12, Esc, or F9, but your motherboard may differ. You should see a list of devices — select your USB drive.
- If you don't see a boot menu, enter the BIOS/UEFI setup (often Del or F2) and change the boot order to put the USB first. Save and exit. The PC will restart and boot from the USB.
- You'll see the Windows Setup screen with language options. Click Next, then click Repair your computer in the bottom-left corner.
- On the next screen, choose Troubleshoot → Advanced options → Command Prompt. A black command window will open.
Now type these commands one at a time, pressing Enter after each. Watch the output — you want to see "The operation completed successfully" after each one.
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
After the last command, if it finds a Windows installation, it'll ask "Add installation to boot list?" Type Y and press Enter.
Close the Command Prompt and click Restart. Remove the USB drive when the PC starts to restart. You should see the Windows logo and boot normally.
If you get an error on bootrec /fixboot saying "Access is denied," that's uncommon on UEFI systems but happens. Run this instead: bootrec /fixboot won't work, so skip it and go straight to bootrec /scanos then bootrec /rebuildbcd. That's often enough.
Why This Works
Windows stores boot information in a small database called the BCD. It contains entries for each operating system, pointing to where the OS files live. If that database gets corrupted — a sudden power loss during an update, a disk error, or a bad sector — Windows can't find itself and throws the consistency check error. The bootrec commands rewrite the master boot record and rebuild that BCD from scratch. It's like clearing a corrupted spreadsheet and re-entering the one row that matters.
Less Common Fixes for the Same Error
If the BCD Rebuild Doesn't Help
Sometimes the error isn't the BCD itself, but a driver or system file that fails a consistency check. Try these in order:
- Run Startup Repair — From the same Advanced options screen (before Command Prompt), pick Startup Repair. Let it run. It may take 10–20 minutes. It will attempt to fix issues like missing system files.
- Check your disk for errors — Back in the Command Prompt, run
chkdsk /f /r C:(replace C: with your Windows drive letter — it might be D: in the recovery environment). This scans for bad sectors and file system errors. It'll take a while, so be patient. - Remove recently installed hardware — If you just added an NVMe SSD or a new RAM stick before this error, power off and remove it. I've seen a flaky drive cause exactly this blue screen.
If You Have a BitLocker-Encrypted Drive
BitLocker complicates things. The consistency check might be failing because it can't read the encrypted boot files. You'll need your recovery key (usually saved to your Microsoft account or a USB drive). When you boot from the installation media, it may ask for the key. If you don't have it, you're stuck — sorry.
Corrupted System Files
If none of the above works, the system files themselves might be damaged. From the Command Prompt, run:
sfc /scannow
dism /online /cleanup-image /restorehealth
The first checks integrity of protected system files. The second uses Windows Update to fix any corrupted components. Both take time — run them, then restart and see if the error is gone.
Prevention — Keep It From Happening Again
The most common trigger I see is a forced shutdown during a Windows update. Your PC is mid-install, power blips, and the BCD never gets written properly. So:
- Connect your desktop to a UPS if you're in an area with power flickers. A $50 uninterruptible power supply is cheap insurance.
- On a laptop, keep it plugged in during updates — don't let the battery die while Windows is installing.
- Update your BIOS/firmware occasionally. Motherboard manufacturers often fix bugs that affect boot behavior.
- If you use third-party antivirus, make sure it's compatible with your Windows version. Some boot-level protections have been known to corrupt BCD entries.
And always keep a Windows installation USB handy. Create one now, even if your PC is working fine. When this error hits again — and it might — you'll be ready.