Windows INACCESSIBLE_BOOT_DEVICE (0x0000007B) — Boot Drive Not Found
Criticalbsod
Overview
INACCESSIBLE_BOOT_DEVICE BSOD occurs during startup when Windows cannot access the boot partition, often after BIOS changes, driver updates, or disk errors.
Key Details
- Stop code 0x0000007B — Windows cannot access the system partition during boot
- Very common after changing SATA mode in BIOS (IDE to AHCI or vice versa)
- Can occur after Windows Update installs a new storage controller driver
- Also triggered when moving a Windows drive to a different computer
- The BCD (Boot Configuration Data) may be pointing to the wrong partition
Common Causes
- SATA mode changed in BIOS from AHCI to IDE or RAID
- Storage controller driver missing or incompatible after update
- Boot configuration data (BCD) corrupted or pointing to wrong partition
- Windows drive moved to a new computer with different storage controller
- Corrupted or missing storage driver files on the boot partition
Steps
- 1Enter BIOS and verify SATA mode matches what Windows was installed with (usually AHCI)
- 2Boot into Windows Recovery: Troubleshoot > Advanced > Command Prompt
- 3Rebuild BCD: bootrec /rebuildbcd and bootrec /fixmbr and bootrec /fixboot
- 4Enable Safe Mode from recovery: bcdedit /set {default} safeboot minimal — then remove problematic driver in Safe Mode
- 5If SATA mode was changed, revert it in BIOS or enable AHCI driver in registry before changing
Tags
windowsbsodinaccessible-boot-devicebootsata
More in Bsod
windows-0000000A-irql-not-less-or-equalWindows Error 0x0000000A — IRQL NOT LESS OR EQUAL
Criticalwindows-00000050-page-fault-in-nonpaged-areaWindows Error 0x00000050 — PAGE FAULT IN NONPAGED AREA
Criticalwindows-0000007E-system-thread-exception-not-handledWindows Error 0x0000007E — SYSTEM THREAD EXCEPTION NOT HANDLED
Criticalwindows-0000007A-kernel-data-inpage-errorWindows Error 0x0000007A — KERNEL DATA INPAGE ERROR
Criticalwindows-000000EF-critical-process-diedWindows Error 0x000000EF — CRITICAL PROCESS DIED
Criticalwindows-00000133-dpc-watchdog-violationWindows Error 0x00000133 — DPC WATCHDOG VIOLATION
CriticalFrequently Asked Questions
Yes, but you must enable the AHCI driver in registry first: set HKLM\SYSTEM\CurrentControlSet\Services\storahci\Start to 0, then change BIOS.