STOP 0x0000007B: Inaccessible Boot Device Fix

The machine was starting up, and just after the Windows logo appeared, the screen went blue with STOP: 0x0000007B and the text INACCESSIBLE_BOOT_DEVICE. Windows has already loaded enough of itself to start the kernel, but it cannot read the disk that holds the rest of the operating system. The error is not a hard drive failure report. It is Windows saying that the driver it needs to talk to the storage controller is not present or not working.

The most common trigger is a hardware change: moving the hard drive to a different computer, changing the SATA mode in the BIOS, or attaching the drive to a different controller. The drive itself may be perfectly healthy. The problem is that Windows has loaded a driver for the old controller, and that driver cannot handle the new one.

What Causes 0x0000007B

Three things can produce this stop code, and they need different fixes. Diagnose before changing anything.

1. SATA Mode Mismatch (AHCI vs. IDE vs. RAID)

Modern BIOS/UEFI firmware offers several modes for the SATA controller: IDE (or Legacy), AHCI, and RAID. Windows loads a different driver for each mode. If the drive was installed with the controller in AHCI mode and the mode is switched to IDE, Windows will try to load the IDE driver, which does not exist for that controller, and you get 0x0000007B.

This is the most common cause because changing the SATA mode is a single BIOS setting, and it is easy to flip it while troubleshooting other problems.

How to check: Enter the BIOS/UEFI setup (usually by pressing Del, F2, or F10 during startup) and look for a SATA or Storage Configuration section. Note the current mode. If you know the original mode, set it back. If you do not, try each mode in turn, booting after each change. One of them will work if the drive and controller are functional.

2. Missing or Incompatible Storage Controller Driver

When Windows is installed, it loads the driver for the controller that was present at that time. If the drive is moved to a computer with a different controller chipset (for example, from an Intel to an AMD system), the driver for the new controller is not in the driver store, and Windows cannot load it at boot.

This is also common when cloning a system to different hardware without preparing it first.

How to check: If changing SATA modes does not help, the controller driver is likely missing. The registry key that controls which driver loads is HKLM\SYSTEM\CurrentControlSet\Services\msahci (for AHCI) or HKLM\SYSTEM\CurrentControlSet\Services\pciide (for IDE). If the Start value is not set to 0 (meaning “load at boot”), Windows will not load the driver.

3. Corrupted Boot Configuration or Master Boot Record

The boot configuration data (BCD) or the master boot record (MBR) can be damaged, causing Windows to attempt to load from the wrong location or with the wrong parameters. This is less common than the driver issues but still possible, especially after a failed update or a power loss during boot.

How to check: If the drive is known to be good and the SATA mode is correct, run a boot repair. This will not fix a driver problem, but it will fix a corrupted boot configuration.

Repairs in Order of Least-Destructive First

Step 1: Change the SATA Mode in BIOS/UEFI

This is the fastest test and the most common fix. It does not touch any data.

1. Restart the computer and enter the BIOS/UEFI setup.
2. Find the SATA mode setting. It is usually under Advanced > SATA Configuration or Storage.
3. Change the mode to the opposite of what it is now (IDE to AHCI, or AHCI to IDE). If you do not know the original, try each one.
4. Save and exit. Windows will start if the driver for that mode is present.

If the system boots, the problem is solved. If it does not, revert to the original mode and continue.

Step 2: Use Windows Recovery Environment to Repair Boot

If changing SATA mode did not help, the boot configuration may be corrupted. This does not affect personal files.

1. Boot from the Windows installation media (USB or DVD).
2. Select your language, then click Repair your computer.
3. Choose Troubleshoot > Advanced options > Command Prompt.
4. Run the following commands, one at a time:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

• bootrec /fixmbr rewrites the master boot record without touching the partition table.
• bootrec /fixboot rewrites the boot sector.
• bootrec /rebuildbcd scans for Windows installations and rebuilds the boot configuration database.

If the commands report success, restart the computer. If they fail with “The system cannot find the path specified” or similar, the boot configuration is not the issue.

Step 3: Enable the Correct Storage Driver in the Registry

If the boot repair did not help, the driver is missing or disabled. This step requires editing the registry, which can make the system unbootable if done incorrectly. The changes are limited to two values, and the procedure is reversible.

This step is for the case where the SATA mode is correct but the driver is not loading. Confirm that by checking the BIOS mode and knowing the original mode.

1. Boot from the Windows installation media and open the Command Prompt as in Step 2.
2. Identify the Windows drive letter. It is often not C:. Run:

diskpart
list volume

Note the volume letter that corresponds to your Windows installation (look for the volume with the Windows folder). Exit diskpart with exit.

3. Load the registry hive from the offline system:

reg load HKLM\OFFLINE\SYSTEM <drive>:\Windows\System32\config\SYSTEM

Replace <drive> with the actual letter, e.g., D:.

4. Check the current value of the Start parameter for the AHCI driver:

reg query HKLM\OFFLINE\SYSTEM\ControlSet001\services\msahci /v Start

If the value is not 0x0, change it:

reg add HKLM\OFFLINE\SYSTEM\ControlSet001\services\msahci /v Start /t REG_DWORD /d 0 /f

5. Do the same for the IDE driver (pciide):

reg query HKLM\OFFLINE\SYSTEM\ControlSet001\services\pciide /v Start
reg add HKLM\OFFLINE\SYSTEM\ControlSet001\services\pciide /v Start /t REG_DWORD /d 0 /f

6. Unload the hive:

reg unload HKLM\OFFLINE\SYSTEM

7. Restart the computer.

If the system boots, the driver is now enabled. If it still fails, the driver for the new controller is not present in the driver store, and you will need to inject it (see Step 5) or reinstall Windows.

Step 4: Check the Disk for Errors

A failing disk can also produce 0x0000007B, but this is less common than the driver issues. If the disk is physically failing, no driver change will help. Run a disk check from the recovery command prompt:

chkdsk <drive>: /r

Replace <drive> with the Windows volume letter. This scans for bad sectors and attempts recovery. It can take hours on a large disk. If chkdsk reports extensive damage, the disk is likely failing, and data should be backed up immediately.

Step 5: Inject the Missing Storage Driver (Advanced)

If the controller is different from the one the system was installed with, the driver for the new controller must be added to the driver store. This is done with the dism tool from the recovery environment.

This step requires a copy of the driver for the new controller, usually downloaded from the manufacturer’s website and placed on a USB drive.

1. Boot from the Windows installation media and open the Command Prompt.
2. Mount the Windows image (offline servicing):

dism /image:<drive>: /add-driver /driver:<path-to-driver> /recurse

Replace <drive> with the Windows volume letter and <path-to-driver> with the location of the driver on the USB drive, e.g., E:\drivers.

3. The command adds the driver to the offline image. After it completes, restart.

If the driver is correct, Windows will boot. If not, the system will still fail, and a reinstall may be the only option.

What People Get Wrong About 0x0000007B

The most common misdiagnosis is assuming the hard drive is dead. The error text says “inaccessible boot device,” which sounds like the disk is gone, but in the majority of cases the disk is fine. The natural mistake is to replace the drive or reinstall Windows immediately, which destroys the existing installation and data. The actual cause is almost always a driver mismatch, which is fixable without losing anything.

Another error is changing the SATA mode randomly and then giving up when the first attempt fails. The mode must match the driver that Windows has loaded. If you do not know the original mode, you have to try each one, but you must also consider that the driver may be missing entirely, which no BIOS setting will fix.

A third mistake is running a boot repair when the problem is a missing driver. bootrec only fixes boot configuration, not driver issues. It will report success but the blue screen will return. The registry and driver steps are the ones that address the actual cause.

Comparison of Causes and Fixes

Preparing Before Moving a Drive

If you plan to move a Windows installation to different hardware, prepare it in advance to avoid 0x0000007B. Before shutting down the original system, run the following in an elevated Command Prompt to set the storage drivers to load at boot:

reg add HKLM\SYSTEM\CurrentControlSet\Services\msahci /v Start /t REG_DWORD /d 0 /f
reg add HKLM\SYSTEM\CurrentControlSet\Services\pciide /v Start /t REG_DWORD /d 0 /f

This ensures that both AHCI and IDE drivers are enabled, so the system can boot on either type of controller. After moving the drive, if the new system uses a different controller, you may still need to inject the driver, but this step covers the common cases.

When to Reinstall

If all the above steps fail, and the disk is confirmed healthy, the driver for the new controller is not available or cannot be injected. In that case, a clean installation of Windows is the reliable solution. This will erase all data on the system drive, so back up files first. Reinstalling is the last resort, not the first response.