Skip to content
PCTestHub

INACCESSIBLE_BOOT_DEVICE (0x7B) blue screen: what it means and how to fix it

Windows cannot access the drive it is installed on. Below you will find the most common causes and the steps to fix it, in order. To look up another code, use the search box.

Blue screenINACCESSIBLE_BOOT_DEVICE · 0x0000007B

Windows cannot access the drive it is installed on

During startup, Windows lost access to the system drive. According to Microsoft, it is usually a drive failure, a change in BIOS settings (such as SATA or RAID mode), a change in partitions or storage controller, or incompatible hardware.

Why it happens

  • The drive mode was changed in the BIOS (AHCI, RAID, Intel RST or VMD).
  • The system drive was replaced, cloned or repartitioned.
  • A failing drive or cable.
  • An update that broke the storage driver.

How to fix it

  1. If you changed something in the BIOS (SATA mode between AHCI and RAID, or the Intel RST/VMD option), set it back to its previous value.
  2. If you replaced or cloned the drive, check that it is properly connected and first in the BIOS boot order.
  3. If Windows does not start, open the Recovery Environment (it appears on its own after two or three failed starts, or from a Windows installation USB › Repair your computer). Under Troubleshoot › Advanced options you have Startup Repair, System Restore, Uninstall Updates and Startup Settings (to enter Safe Mode).
  4. From the Recovery Environment › Command Prompt, check the drive with chkdsk C: /f (if Windows shows up under another letter, find it with dir D:, dir E:, etc.).
  5. Check the health of the hard drive or SSD (SMART status) with its maker's free tool and, if it is an SSD, update its firmware from there.

Still happening? If the BIOS does not see the drive or it makes noises, the problem is the drive, the cable or the connector.

Meaning based on Microsoft's official documentation. The steps are general guidance: if you are not sure, ask a technician for help.

How to find the code of a blue screen

The error screen shows the code on the «Stop code» line (for example CRITICAL_PROCESS_DIED) and sometimes «What failed» with the file that caused it (for example nvlddmkm.sys). In recent Windows 11 versions that screen is black instead of blue, but the codes are the same.

If the computer restarts before you can read it, the code is saved: press Windows + R, type eventvwr and go to Windows Logs › System. Look for an event with source BugCheck: it shows the code in hexadecimal (for example 0x0000007e), which you can also type in the search box. To stop Windows from restarting by itself so you can read the screen, go to Advanced system settings › Startup and Recovery › Settings and uncheck «Automatically restart».

What to do with any blue screen

This works for any code, including the ones without their own explanation. These are Microsoft's general steps, in the order worth trying them:

  1. Write down the code and the file shown in «What failed», if any: they tell you what failed.
  2. Think about what changed before it started (a program, a driver, an update or a part) and undo it. System Restore (rstrui) goes back to an earlier point without touching your documents.
  3. Install Windows updates and the drivers from your PC maker's website; if the problem started with a new driver, roll back to the previous one.
  4. Update the BIOS from the maker's website, with the charger connected.
  5. Test the hardware: memory with mdsched and the drive with chkdsk C: /f. If you raised speeds (overclock or XMP), go back to default values.
  6. Scan for malware with Windows Security (Microsoft Defender Offline scan).
  7. Free up space: Microsoft recommends 10% to 15% of the drive.
  8. Repair Windows with DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow in Command Prompt as administrator.

If Windows does not start, the Recovery Environment appears after two or three failed starts: from Troubleshoot › Advanced options you can use Startup Repair, System Restore, Uninstall Updates or enter Safe Mode.

Most common blue screens

Windows Update errors

Activation errors

Windows startup errors

Errors when opening programs

Meanings come from Microsoft's official documentation (bug check code reference and the page of each error), checked on November 17, 2026. The texts and steps are our own. See all codes → En español