Windows Boot Error Codes: Causes and Fixes (Index)

Stuck at a blue screen or a black screen with a hex code? Find your stop code below for the one-line cause and the exact fix. Most boot errors are repaired from Windows Recovery (WinRE) — reach it by forcing three failed boots, or by booting from a Windows install USB and choosing Repair your computer.

Before you repair: if the machine holds the only copy of data you can't lose, image the drive to a known-good external disk first. Boot repairs are normally safe, but never run format, clean, or a reinstall to "get past" an error — that destroys data, especially on BitLocker-encrypted drives.
Stop code Likely cause Fix
INACCESSIBLE_BOOT_DEVICE
0x0000007B
Wrong SATA mode (AHCI/RAID), missing storage driver, or bad update broke the boot path. Exact fix →
0xc000000e BCD points to a boot volume Windows can't reach. On UEFI, bootrec /fixboot says "Access denied". Exact fix →
0xc0000225 winload.efi missing/corrupt — EFI boot files damaged, often after a clone or partition change. Exact fix →
BitLocker recovery loop An update changed TPM/Secure Boot measurements; BitLocker keeps prompting for the recovery key. Exact fix →
0xc0000001 Corrupt registry or unreadable BCD/SAM; Windows can't read boot data. In WinRE Command Prompt: run bootrec /scanos, bootrec /rebuildbcd, then chkdsk C: /f /r and sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows. If it persists, run Startup Repair.
0xc000014c BCD store is missing, corrupt, or unreadable — often after power loss during a write. Rebuild the BCD in WinRE: bootrec /scanos then bootrec /rebuildbcd (type Y to add the install). On UEFI, rebuild with bcdboot instead. Then chkdsk C: /f /r.
0xc0000034 BCD missing required boot entry — common after a failed/interrupted Windows update. Run Startup Repair from WinRE first. If that fails, rebuild the BCD: bootrec /rebuildbcd (legacy) or bcdboot C:\Windows /s S: /f UEFI (UEFI). Consider uninstalling the last update from Advanced options → Uninstall Updates.
CRITICAL_PROCESS_DIED
0x000000EF
A critical Windows process crashed — corrupted system files, a bad driver, or disk errors. Exact fix →
UNMOUNTABLE_BOOT_VOLUME
0x000000ED
Windows can't mount the boot volume — file-system corruption, a failing drive or cable, or a bad update (confirmed with the January 2026 KB5074109 update). Exact fix →
GRAM tip: Every fix above runs in Windows Recovery, which is already on the broken PC — no second computer needed. Once the machine boots again, plug in GRAM — a free portable repair toolkit that runs from a USB inside Windows — to check disk health, read the crash history, and let its AI agent confirm the root cause so the stop code doesn't come back. (New to rescue USBs? See the difference between portable and bootable repair toolkits.)
Download GRAM free See AI pricing →