Windows Stop Error 0x0000007B / INACCESSIBLE_BOOT_DEVICE – System Fails to Boot
Stop error 0x0000007B (INACCESSIBLE_BOOT_DEVICE) prevents Windows from starting when the OS cannot access the system partition, most commonly caused by a missing or incompatible storage controller driver, corrupted Boot Configuration Data (BCD), or a BIOS/UEFI SATA mode change. Recovery requires booting into the Windows Recovery Environment (WinRE) to repair boot records, validate BCD entries, restore critical storage drivers to boot-start, and repair corrupted system files using SFC and DISM. Reverting BIOS settings or injecting appropriate drivers resolves the majority of cases without a full OS reinstall.
Indicators
- Blue screen displaying Stop error code 0x0000007B
- Blue screen displaying INACCESSIBLE_BOOT_DEVICE error message
- System fails to boot into Windows and loops back to the error screen
- System enters automatic repair loop without successfully completing startup
- Error occurs immediately after a hardware change such as replacing or adding a storage controller
- Error occurs after a Windows update or storage driver update
- Error appears after migrating a physical machine to a virtual environment (P2V)
Likely causes
- Storage controller driver not loaded or incompatible (e.g., switching from IDE to AHCI or NVMe without pre-enabling the driver)
- BIOS/UEFI firmware SATA mode changed (e.g., AHCI to IDE or vice versa) without corresponding driver preparation
- Missing or corrupt boot-critical storage driver (storahci.sys, stornvme.sys, iaStorV.sys, etc.) with Start value not set to 0
- Corrupted or misconfigured Boot Configuration Data (BCD) store
- Corrupted system files or registry hive preventing storage stack initialisation
- Physical-to-virtual (P2V) migration performed without injecting the appropriate virtual storage controller drivers
- Windows update that modified or removed a critical storage driver
- Incorrect or missing driver for a newly installed storage controller card
Diagnostic steps
-
Boot from Windows installation media and open a Command Prompt via 'Repair your computer' > 'Troubleshoot' > 'Advanced options' > 'Command Prompt' to enter the Windows Recovery Environment (WinRE).
-
Run 'bcdedit /enum all' to review the Boot Configuration Data store and verify that the boot device identifier, partition, and Windows directory path are correct and consistent.
-
Run 'diskpart', then execute 'list disk', 'list volume', and 'list partition' to confirm the system and boot partitions are visible and correctly assigned drive letters. Reassign letters with 'assign letter=X' if missing.
-
Run 'bootrec /fixmbr', 'bootrec /fixboot', and 'bootrec /rebuildbcd' to repair the Master Boot Record and rebuild the BCD store if boot files are found to be corrupted or absent.
-
Run 'sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows' (substituting the correct drive letter identified via diskpart) to check and repair corrupted system files in the offline Windows image.
-
If SFC reports unrepairable files, run 'DISM /Image:C:\ /Cleanup-Image /RestoreHealth' to repair the offline Windows image using Windows Update or installation media as the source.
-
Mount the offline SYSTEM registry hive: 'reg load HKLM\TempSys C:\Windows\System32\config\SYSTEM'. Navigate to HKLM\TempSys\ControlSet001\Services and verify that the appropriate storage driver key (storahci, stornvme, or iaStorV) has its 'Start' DWORD value set to 0 (boot start). Correct it with 'reg add' if it is set to 3 (demand start) or 4 (disabled). Unload the hive with 'reg unload HKLM\TempSys'.
-
If the BIOS/UEFI SATA controller mode was recently changed (e.g., IDE to AHCI), revert the setting in BIOS/UEFI firmware to the original mode and attempt to boot. Alternatively, pre-enable the correct driver (Step 7) before changing the BIOS mode.
-
If the error follows a P2V migration, use DISM or the VM vendor's driver injection tool to inject the appropriate virtual storage controller drivers (e.g., VMware PVSCSI or Hyper-V storvsc) into the offline Windows image before attempting to boot in the virtual environment.
-
Restart the system, remove the installation media, and verify successful boot into Windows. If the issue persists, review the System event log for additional storage or disk errors and confirm hardware integrity.
Resolution path
- Boot into WinRE using Windows installation media via 'Repair your computer' > 'Advanced options' > 'Command Prompt'
- Use diskpart to verify disk and partition visibility and confirm or reassign boot/system partition drive letters
- Run bcdedit /enum all to validate Boot Configuration Data entries match the visible partitions and correct any discrepancies
- Run bootrec /fixmbr, /fixboot, and /rebuildbcd to repair corrupted MBR and BCD store
- Run offline SFC (sfc /scannow /offbootdir /offwindir) to detect and repair corrupted system files
- Run offline DISM /Cleanup-Image /RestoreHealth if SFC cannot repair all files
- Load the offline SYSTEM registry hive and set the Start value to 0 (boot start) for the relevant storage driver (storahci, stornvme, or iaStorV)
- Revert BIOS/UEFI SATA mode settings to the configuration present when Windows was originally installed if the mode was recently changed
- For P2V migration scenarios, inject the appropriate virtual storage controller drivers into the offline Windows image before booting
- Remove installation media, restart the system, and confirm successful boot into Windows
Prevention
- Create a full system backup or VM snapshot before changing BIOS/UEFI storage controller mode settings
- Pre-configure the target storage driver to boot-start (Start=0) in the registry before making BIOS storage mode changes or migrating to a new platform
- Prepare and test storage driver injection procedures before undertaking P2V or P2P migrations
- Test Windows cumulative updates and driver updates in a non-production environment before deploying to critical servers or workstations
- Maintain up-to-date storage controller drivers sourced from the hardware or hypervisor vendor
- Use Windows built-in backup (wbadmin), Veeam, or an equivalent solution to maintain a recent bootable recovery point for every production system
- Document all BIOS/UEFI settings before making hardware or firmware changes to enable rapid and accurate reversion
- Schedule regular offline SFC and DISM health checks to detect system file corruption before it causes a boot failure
Tools
- bcdedit.exe (Boot Configuration Data editor)
- diskpart.exe (Disk partition and volume management)
- bootrec.exe (MBR, boot sector, and BCD repair tool)
- sfc.exe (System File Checker – offline mode)
- DISM.exe (Deployment Image Servicing and Management – offline image repair)
- reg.exe (Command-line registry editor for offline hive loading and editing)
- regedit.exe (GUI registry editor for offline hive inspection)
- Windows PE / Windows Recovery Environment (WinRE)
- Windows Memory Diagnostic (memtest86 / mdsched.exe)