STOP Code Inaccessible Boot Device Fix

The INACCESSIBLE_BOOT_DEVICE stop code (0x0000007B) means Windows can’t read the drive that holds your system files during startup. The fix usually involves checking the boot order, running Startup Repair, or rolling back a recently installed driver. Below are the causes and step-by-step solutions that work for most people.

What Causes INACCESSIBLE_BOOT_DEVICE?

This error appears when the Windows kernel can’t access the volume that contains the system files. The most common triggers are:

• A recent driver update (especially storage controllers like AHCI, RAID, or NVMe).
• Incorrect BIOS/UEFI settings, such as SATA mode switched between IDE and AHCI.
• Corrupted system files or a damaged boot sector.
• A failing hard drive or SSD.
• Loose cables or a drive not detected by the system.
• After a Windows update, particularly a feature update that changes storage drivers.

How Windows Boot Works (Why This Error Happens)

When you power on your PC, the BIOS/UEFI initializes hardware and then loads the boot manager. The boot manager loads the Windows kernel, which then needs to access the system drive to read drivers and continue booting. If the kernel can’t find or read the boot device, it throws the INACCESSIBLE_BOOT_DEVICE stop code. This is different from a “bootmgr missing” error, which means the boot manager itself is missing. Here, the boot manager is present but the kernel can’t talk to the storage.

Before You Start: Check Physical Connections

For desktop PCs, power off, unplug, and reseat the SATA or NVMe cable. Also try a different SATA port. For laptops, this is less common, but if you recently opened the case, check the drive. After reseating, boot again. This is a quick fix that works more often than you’d think.

Method 1: Run Startup Repair

If the error appears after a recent change, Startup Repair can often fix it. You’ll need to access the Windows Recovery Environment (WinRE). If you can’t boot normally, you can force WinRE by interrupting the boot process three times: turn the PC on, wait until Windows starts loading, then press and hold the power button to force off. Do this three times; on the fourth boot, Windows should enter Automatic Repair.

1. On the recovery screen, click Troubleshoot.
2. Click Advanced options.
3. Click Startup Repair.
4. Select your operating system and wait for the process to complete.

If Startup Repair says it couldn’t fix the problem, try the next method.

Method 2: Check BIOS/UEFI SATA Mode

A very common cause is a mismatch between the SATA controller mode in BIOS and the driver Windows expects. For example, if Windows was installed with AHCI enabled and you later switch to IDE (or vice versa), the system can’t load the correct driver and throws this error.

1. Restart your PC and press the key to enter BIOS/UEFI (often Del, F2, F10, or Esc).
2. Look for a setting called SATA Mode, Storage Configuration, or Controller Mode.
3. If it’s set to IDE, change it to AHCI. If it’s already AHCI, try IDE (though AHCI is recommended for SSDs).
4. Save and exit. If Windows boots, you’re done. If not, revert to the original setting.

Some newer systems use NVMe drives; ensure the NVMe controller is enabled in BIOS.

Method 3: Roll Back or Disable Recent Drivers

If the error started after a driver update, you can roll back the driver from the recovery environment.

1. Boot to WinRE (as described in Method 1).
2. Go to Troubleshoot > Advanced options > Startup Settings.
3. Click Restart. After restart, you’ll see a list of options.
4. Press 4 or F4 to enable Safe Mode.

In Safe Mode, Windows loads with minimal drivers. If it boots, you can open Device Manager and roll back the storage controller driver:

1. Right-click the Start button and select Device Manager.
2. Expand Storage controllers.
3. Right-click the controller (e.g., Intel AHCI Controller) and select Properties.
4. Go to the Driver tab and click Roll Back Driver if available.

If rollback isn’t available, you can uninstall the driver and restart. Windows will reinstall the default driver.

Method 4: Use Command Prompt to Run CHKDSK and SFC

If the drive is corrupted, you can run disk checks from the recovery environment.

1. Boot to WinRE, go to Troubleshoot > Advanced options > Command Prompt.
2. Type chkdsk /f /r C: and press Enter. (Replace C: with your system drive letter if different.)
3. If it asks to dismount the volume, type Y and press Enter.
4. After CHKDSK completes, run sfc /scannow to check system file integrity.
5. Exit and restart.

Note: CHKDSK can take a long time on large drives. If it finds bad sectors, the drive may be failing.

When to Consider Reinstalling Windows

If none of the above works, the system files may be too corrupted to repair. You can try a repair install (which keeps your files) using Windows installation media. If that fails, a clean install is the final option. Back up your data if possible, though if the drive isn’t accessible, you may need to use a bootable Linux USB to copy files.

Frequently Asked Questions

Can this error be caused by a failing SSD?

Yes. SSDs can fail, and the controller may become unresponsive. If you’ve tried all software fixes and the drive still isn’t recognized, test the drive on another computer or use manufacturer diagnostics. If the drive is under warranty, consider replacing it.

How do I know if my SATA mode is AHCI or IDE?

You can check in BIOS/UEFI. The setting is usually under Storage or Advanced. If you’re not sure, look up your motherboard manual. Changing this setting after Windows is installed can cause this exact error, so only change it if you know the correct mode.

Will this error damage my files?

Usually no, the error itself doesn’t damage files. However, if the cause is a failing drive, you may lose data. It’s always wise to back up important files regularly.

Can I fix this without a Windows installation disc?

Yes, you can use the built-in recovery environment by forcing Windows to enter Automatic Repair (as in Method 1). If that doesn’t work, you can create a Windows installation USB on another computer using Microsoft’s Media Creation Tool.

What does “INACCESSIBLE_BOOT_DEVICE” mean exactly?

It means Windows loaded the boot manager but then couldn’t read the system drive to continue loading the OS. The kernel is telling you it can’t access the boot volume. It’s a storage access issue, not a display or memory problem.

Related

• Recover Deleted TIFF Files: Full Guide
• Enterprise AI Security: Full Lifecycle Guide
• Cobblemon Path of Adventure Server Fabric Setup Guide