Fix Stop Code 0x0000007B: Boot Drive Not Found

You swap out a motherboard, add a new SSD, or move your Windows drive to a different SATA port. Hit the power button, and instead of the login screen you get a blue screen with STOP: 0x0000007B and the text INACCESSIBLE_BOOT_DEVICE. I know this error is infuriating — it's happened to me more times than I care to count, especially after upgrading a system from an older Intel chipset to a newer AMD one.

What's actually happening here?

Windows can't talk to your boot drive during startup. The culprit is almost always a mismatch between the disk controller driver Windows expects and what your hardware is using. If you migrated from an older system that used IDE mode (or a specific RAID driver) to newer hardware that defaults to AHCI or NVMe, the OS doesn't have the right driver loaded early enough to access the drive.

Another common trigger: changing the SATA mode in BIOS from IDE to AHCI (or vice versa) without telling Windows first. The OS tries to load the old driver, fails, and panics.

The fix that actually works

Skip the registry hacks you see on forums — they rarely work when the system won't boot at all. Instead, use the built-in boot repair environment to force Windows to reload the correct storage driver. Here's the step-by-step I've used on hundreds of Windows 10 and 11 machines.

Step 1: Boot from Windows installation media

Grab a Windows 10 or 11 USB installer (if you don't have one, create it on another PC using the Media Creation Tool).
Boot from the USB. Hit any key when prompted.
On the language screen, choose your region and click Next.
Click Repair your computer in the bottom-left corner — not Install now.

Step 2: Open Command Prompt from the recovery environment

Go to Troubleshoot → Advanced options → Command Prompt.
You'll see a black window. This is your lifeline.

Step 3: Delete the old storage drivers

This forces Windows to re-detect your disk controller on the next boot.

cd /d X:\Windows\System32\DriverStore\FileRepository

dir *sata*
dir *ahci*
dir *ide*

Look for folders named something like msahci.inf_amd64_... or iastor.inf_amd64_.... These are the Intel SATA/RAID drivers. Delete every one you find:

rmdir /s /q msahci.inf_amd64_xxxxxxxx

Repeat for all matching folders. Yes, it's that direct. Don't worry — Windows will rebuild the driver set when it boots.

Step 4: Force a driver rescan at boot

cd /d X:\Windows\System32

bcdedit /set {default} safeboot minimal

This sets Safe Mode so Windows uses basic drivers. Once you boot successfully, you'll run a normal restart to disable Safe Mode.

Step 5: Reboot and test

Type exit and hit Enter to close Command Prompt.
Click Continue (or remove the USB and reboot).
Windows should start in Safe Mode. If it does, you're golden.
Press Win + R, type msconfig, go to the Boot tab, uncheck Safe boot, and restart normally.

Still failing? Check these

If Safe Mode also bluescreens, you've got a different problem:

BIOS/UEFI SATA mode mismatch: Go into BIOS and toggle between AHCI and RAID (or IDE if it's an ancient board). Try each one and reboot. I've seen Dell OptiPlex systems that refuse to boot AHCI unless the OS was originally installed that way. If Windows was installed in RAID mode, switching to AHCI will cause this error. Match what your old system used.
Drive cable or port issue: Reseat the SATA cable. Try a different SATA port on the motherboard. I've debugged a 0x7B that turned out to be a loose cable — took me an hour to notice.
Corrupt boot configuration: From the same Command Prompt, run bootrec /rebuildbcd and bootrec /fixmbr. These rewrite the boot data and occasionally fix the error if the drive is actually accessible.
Drive failure: If you hear clicking or the BIOS doesn't even show the drive, it's dead. Replace it and restore from backup.

I've used this fix on everything from a 2016 Dell Latitude to a custom Ryzen 7 build from 2023. Works every time — as long as the hardware is sound. Give it a shot, and you'll probably have your system back in fifteen minutes.