ErrorFix
Windows PC Errors

How to Fix BSOD INACCESSIBLE_BOOT_DEVICE (0x0000007B)

By ErrorFix · Updated October 13, 2026 · 8 min read

Error 0x0000007BPlain English: Windows lost access to the drive it boots from — usually a storage driver or BIOS setting problem after an update or hardware change.
Quick answer: This usually strikes right after a Windows update, BIOS change, or drive swap. Check that the BIOS SATA mode (AHCI vs IDE) matches what Windows was installed with, then boot into recovery and run bootrec /fixmbr, /fixboot, and /rebuildbcd, followed by chkdsk. Details below.

What error 0x0000007B means

INACCESSIBLE_BOOT_DEVICE is a blue-screen stop code that appears during startup. Here's what happens: the boot loader finds your Windows installation and hands control to the kernel, but the kernel then fails to communicate with the storage controller that owns the boot drive. Windows can't load anything further without its system drive, so it stops with this error rather than limping along in a broken state.

The classic triggers are a SATA mode flipped in the BIOS (AHCI changed to IDE or RAID, or vice versa), a Windows update that replaced the storage driver with an incompatible one, a corrupted Boot Configuration Data (BCD) store, or a drive that's physically failing. Cloned or migrated drives also hit this when the new system's storage controller needs a different driver. Because the cause is usually configuration or driver-level, your files are almost always intact — the fix is about restoring access, not recovering data.

Common causes

How to fix error 0x0000007B — step by step

Work through these fixes in order. You will need a Windows installation USB for steps 2 through 5 if Windows can't boot at all.

  1. Check the SATA mode in BIOS or UEFI. Restart the PC and press the BIOS key (usually Del, F2, or F12) during startup. Find the storage or SATA configuration section — look for "SATA Mode," "SATA Configuration," or "Storage Controller." Make sure it's set to the mode Windows was installed with, which is AHCI on the vast majority of modern PCs. If it's already AHCI, try IDE/Compatibility mode once as a test. Save with F10, exit, and try booting.
  2. Boot into the Windows recovery environment. Insert your Windows installation USB and boot from it. Choose your language, click "Repair your computer" (not Install), then go to Troubleshoot and open Command Prompt. This gives you a terminal that can repair your offline Windows installation.
  3. Rebuild the boot records with bootrec. In the recovery Command Prompt, run these commands one at a time: bootrec /fixmbr, then bootrec /fixboot, then bootrec /scanos, then bootrec /rebuildbcd. The last command scans for Windows installations and rebuilds the Boot Configuration Data. If /fixboot reports "Access is denied," run diskpart, then list vol, assign a letter to the EFI partition, and retry.
  4. Run chkdsk on the system drive. Still in the recovery Command Prompt, run chkdsk C: /f /r. Note that drive letters shift in the recovery environment — your Windows drive might be D: or E: here. Use diskpart then list vol to confirm which letter holds Windows before running the check.
  5. Run an offline SFC scan. Run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows, adjusting the drive letter to match your Windows drive in the recovery environment. This repairs corrupted system files in the offline installation, including storage driver files.
  6. Check cables, reseat the drive, and test its health. Power off completely and unplug the PC. Open the case (or the drive bay on a laptop, if accessible), check that both the data and power cables are firmly seated, and reseat the drive. If the drive isn't detected in BIOS at all, it's likely a hardware failure — test it in another PC or check its SMART health data.

Did this fix it? Quick checklist

If Windows boots but the error returns after the next update, the update is reinstalling a bad storage driver. In that case, download the correct storage/chipset driver from your motherboard or laptop manufacturer's site, install it manually, and use the "Show or hide updates" troubleshooter to block the problematic driver update.

Frequently asked questions

What does INACCESSIBLE_BOOT_DEVICE mean?

It means Windows started booting but then lost access to the drive containing the operating system. The boot loader found Windows, but the Windows kernel could not communicate with the storage controller — usually because of a wrong SATA mode, a corrupt boot configuration, or a failing drive.

Why did 0x0000007B appear after a Windows update?

Some updates replace storage controller drivers or change how they initialize. If the new driver does not match your controller or the BIOS SATA mode, Windows can no longer talk to the boot drive after the restart and throws this exact stop code.

Will I lose my files fixing 0x0000007B?

The repair steps in this guide — checking BIOS settings, rebuilding boot records, and running chkdsk — do not touch your personal files. Your data stays on the drive throughout. Only a clean reinstall would erase files, and that is the last resort.

What is AHCI mode and why does it matter?

AHCI is the modern communication mode between Windows and SATA drives, enabling features like native command queuing. Windows installs the storage driver for whichever mode was active during setup, so flipping the BIOS setting to IDE or RAID afterward breaks the driver match and causes this blue screen.

Related fixes