sodcalculator

10 Tech How-To

Fix INACCESSIBLE_BOOT_DEVICE BSOD in Windows 10

Guide 10-52671 · Updated · Step by step

If you see the INACCESSIBLE_BOOT_DEVICE blue screen error in Windows 10, it means the operating system cannot read the drive that holds your system files during startup. The fix usually involves checking drive connections, disabling incompatible storage drivers, or running Startup Repair, and most users can resolve it without reinstalling Windows.

What Causes INACCESSIBLE_BOOT_DEVICE

This stop code (0x0000007B) appears when the Windows boot loader loads but the kernel cannot access the boot volume. The error is not about a missing file—it means the storage controller driver is missing, incompatible, or the physical drive is not responding. Common triggers include:

  • A recent Windows update that replaced a storage driver with one your hardware doesn’t support
  • Changing the SATA mode in BIOS from IDE to AHCI (or vice versa) after installation
  • A loose SATA cable, power cable, or a failing hard drive/SSD
  • Third-party disk encryption or partitioning software that modified boot files
  • Overclocking or unstable firmware settings that cause the drive to drop offline

Unlike other BSODs that happen after login, this one occurs very early in the boot process, so you usually cannot reach the desktop.

First Steps: Check Physical Connections and BIOS

Before touching software, confirm the drive is actually present and recognizable. Shut down the PC, unplug it, and reseat the SATA data cable and power connector on both the drive and the motherboard. For NVMe SSDs, remove and reinsert the card in its M.2 slot. Then enter BIOS/UEFI (usually by pressing Del, F2, or F12 during startup) and check:

  • Is the drive listed under Storage or SATA configuration?
  • Does the boot order include the correct Windows Boot Manager entry?
  • Is the SATA mode set to AHCI (the normal modern setting)?

If the drive does not appear at all, try a different port or cable. If it appears but the error persists, the problem is likely a driver mismatch rather than a dead disk.

Run Startup Repair from Recovery Environment

Windows 10 includes a built-in repair tool that can fix boot files and registry issues. To access it, you need a Windows 10 installation USB or recovery drive:

  1. Boot from the installation media and select your language.
  2. Click “Repair your computer” at the bottom-left instead of “Install now”.
  3. Choose Troubleshoot → Advanced options → Startup Repair.
  4. Select your operating system and wait for the diagnostic to finish.

Startup Repair will scan for problems like missing boot configuration data or corrupt system files. If it finds an issue, it will attempt to fix it automatically. If it reports that it couldn’t repair your PC, proceed to the next steps.

Disable or Re-enable the Storage Controller Driver

When the error appears right after a Windows update or a BIOS change, the most effective fix is to disable the problematic driver via the Command Prompt from the recovery environment. This forces Windows to use the generic Microsoft storage driver on the next boot.

  1. Boot from the installation media and go to Troubleshoot → Advanced options → Command Prompt.
  2. Type regedit and press Enter to open the Registry Editor.
  3. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci and ...\Services\stornvme (for NVMe drives).
  4. Double-click Start in the right pane and change its value to 0 (enabled) or 4 (disabled) depending on what you suspect. Setting it to 0 forces the driver to load; setting it to 4 prevents it from loading.
  5. Close the Registry Editor and restart the PC normally.

If you recently switched from IDE to AHCI in BIOS, set the storahci Start value to 0 before changing the BIOS setting. If you switched from AHCI to IDE, set it to 4. This tells Windows which driver to expect.

Use Command Prompt to Check Disk and Boot Files

If the registry tweak doesn’t help, run disk and boot integrity checks from the same Command Prompt window:

  • bootrec /fixmbr – rewrites the master boot record
  • bootrec /fixboot – repairs the boot sector
  • bootrec /rebuildbcd – scans for Windows installations and rebuilds the Boot Configuration Data
  • chkdsk C: /f /r – checks the system drive for file system errors and bad sectors (replace C: with your actual system drive letter)

Run these in order. After each, restart the PC to see if the error clears. If chkdsk finds many bad sectors, the drive may be failing and you should back up important data immediately.

When to Consider System Restore or Reset

If the above steps fail, you can try System Restore to roll back recent driver or update changes. From the recovery menu, select Troubleshoot → Advanced options → System Restore, and choose a restore point from before the error started. If no restore points exist, your last option is to reset Windows 10, which reinstalls the OS while keeping your personal files (if you choose “Keep my files”). This requires a working installation media and will remove installed applications.

Resetting is a last resort because it takes time and you will need to reinstall software. However, it is less destructive than a full clean install and often resolves driver corruption that other methods miss.

Frequently Asked Questions

Can I fix INACCESSIBLE_BOOT_DEVICE without losing data?

Yes, in most cases. Startup Repair, driver disabling, and bootrec commands do not delete personal files. Only the “Reset” option with “Remove everything” would erase data, so always choose “Keep my files” if you attempt a reset.

Why did this happen after a Windows update?

Windows updates sometimes replace storage drivers with generic versions that do not match your motherboard’s chipset. This mismatch causes the boot loader to fail when trying to access the drive. Disabling the new driver and letting Windows fall back to the inbox driver usually resolves it.

Is this error a sign that my hard drive is dead?

Not necessarily. A failing drive can cause it, but so can a loose cable or a driver issue. Run chkdsk to check the disk health. If chkdsk reports many bad sectors or the drive makes clicking noises, replace the drive.

How do I know which drive letter to use in chkdsk?

In the recovery Command Prompt, type diskpart, then list volume. The volume with the label “System” or the one that is about 100-500 MB is the EFI partition; the large NTFS volume is usually C:. Type exit to leave diskpart before running chkdsk.

Will changing SATA mode from IDE to AHCI fix this error?

Only if the error started after you changed the mode. If you never changed it, leave the BIOS setting alone. If you did change it, set it back to the original mode first, then follow the registry steps to enable the correct driver before switching again.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →