INACCESSIBLE_BOOT_DEVICE Blue Screen 0x7B: Fixes in Microsoft Order

Published October 24, 2026 · SJ AI Studio

INACCESSIBLE_BOOT_DEVICE is Windows stop code 0x0000007B (0x7B). Microsoft defines it as Windows having "lost access to the system partition during startup": the drive Windows lives on could not be reached or read while the PC was booting. Microsoft's page is unusually practical for this code. It splits the fixes into two lists, one for when Windows will not boot at all and one for when Windows still boots, and it warns that error logs may be empty because the crash happens before Windows gets far enough to write them.

This page follows the Microsoft Learn article "Bug check 0x7B: INACCESSIBLE_BOOT_DEVICE," read on 12 October 2026 and checked against the Microsoft Docs source file. Microsoft labels it as written for programmers and points customers to https://www.windows.com/stopcode. We reproduce the two lists in Microsoft's order and add nothing to them.

Why can't Windows reach its own drive?

Causes of Stop Code 0x7B

Microsoft's "Cause" section gives several routes to the same stop code:

Cause named by MicrosoftWhat it means in practice
Boot device failureThe boot device driver failed to initialise the boot device, typically a hard disk
Unrecognised file systemFile system start-up failed because it did not recognise the data on the boot device
A recent changeRepartitioning the system partition, changing the BIOS configuration, or installing a disk controller
Incompatible disk hardwareAt first setup, Windows may have been installed on an unsupported disk controller; some controllers need extra drivers at start-up
Failed storage hardwareThe storage hardware has failed and cannot respond to Windows

Microsoft also notes that this error "always occurs while the system is starting," often before a debugger connection exists, so the usual logs may have nothing in them.

Which list applies to you?

Microsoft's split is simple. If you get the stop code and Windows never reaches the desktop, use the first list. If you get it but Windows does start, sometimes or after retries, use the second.

If Windows will not boot: Microsoft's 4 steps

If Windows Will Not Boot

Microsoft's page does not explain what a clean install keeps or removes, and it is the last item on the list. If files on the drive matter to you, think about how you would recover them before you get to this step.

Boot and setup keys Microsoft lists

Microsoft says these vary by maker and to check your PC's documentation, but gives the keys commonly used:

If Windows does boot: Microsoft's 11 steps

Quick Checks

These are in the page's order.

What should you write down first?

Microsoft's "Remarks" section suggests learning as much as possible about the boot drive:

Checklist

Error Details

For developers

Microsoft's debugger notes: run lm to confirm the storage drivers loaded, checking disk, partmgr, NTFS, classpnp and pci, plus the controller's own driver (examples on the page include iaStorA.sys, EhStorClass and storahci). If you can boot with a debugger attached, run !devnode 0 1 when the stop occurs, or !devnode 0 1 storahci to save time, to see which device lacks a driver or did not start. Status flags that include DNF_INSUFFICIENT_RESOURCES, or that lack DNF_STARTED or DNF_ENUMERATED, may point to the problem. Parameter 1 is either the address of a UNICODE_STRING holding the ARC name of the boot device, or the address of the device object that could not be mounted; parameters 2 to 4 are 0.

Data recovery. If the drive has failed, recovering files is outside Microsoft's page and outside this one.

Sources and how to check

Questions readers ask about INACCESSIBLE_BOOT_DEVICE Blue Screen 0x7B

What is stop code 0x7B?

It is INACCESSIBLE_BOOT_DEVICE (0x0000007B). Microsoft says Windows lost access to the system partition during startup.

What causes INACCESSIBLE_BOOT_DEVICE?

Microsoft names boot device failure, an unrecognised file system, repartitioning, BIOS configuration changes, a new disk controller, incompatible disk hardware and failed storage.

I changed the controller mode to AHCI. What now?

Microsoft says to revert recent UEFI (BIOS) changes such as switching the controller mode from legacy to AHCI.

Why are my logs empty?

Microsoft says the error always occurs during startup, often before Windows has booted far enough to start its logging, so logs might be empty.

How much free disk space does Microsoft suggest?

It says the exact need varies but it is a good idea to have 10% to 15% free.

Related articles