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?
Microsoft's "Cause" section gives several routes to the same stop code:
| Cause named by Microsoft | What it means in practice |
|---|---|
| Boot device failure | The boot device driver failed to initialise the boot device, typically a hard disk |
| Unrecognised file system | File system start-up failed because it did not recognise the data on the boot device |
| A recent change | Repartitioning the system partition, changing the BIOS configuration, or installing a disk controller |
| Incompatible disk hardware | At first setup, Windows may have been installed on an unsupported disk controller; some controllers need extra drivers at start-up |
| Failed storage hardware | The 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
- Revert recent hardware changes. Remove recently added hardware, especially hard disk drives or controllers, and see whether the error goes away. If the problem hardware is a hard disk, its firmware might be incompatible with your version of Windows; contact the maker for updates. If removing some other device fixes it, Microsoft says IRQ or I/O port conflicts might exist; reconfigure the new device per its maker's instructions. If you recently changed UEFI (BIOS) settings, such as switching the controller mode from legacy to AHCI, revert those changes.
- Check storage compatibility. Confirm that all hard disk drivers, disk controllers and other storage adapters are compatible with your installed version of Windows.
- Update UEFI (BIOS) and firmware. Check for updates to the system UEFI (BIOS) and the storage controller firmware.
- Use the Media Creation Tool. On another computer, use Microsoft's Media Creation Tool to create a bootable USB drive or DVD, then use it to perform a clean install, either by running the setup file or by booting from the USB drive. You may need to change the boot order in UEFI (BIOS) to boot from USB or DVD instead of the hard disk.
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:
- Boot menu: F12, ESC, F9, F10, F8
- UEFI (BIOS) setup: ESC, DEL, F2
If Windows does boot: Microsoft's 11 steps
These are in the page's order.
- Boot to Safe Mode, then boot normally. Safe Mode loads a core set of storage drivers that may let Windows reach the storage system again. Microsoft's path: Settings, Update and Security, Recovery, Advanced startup; then Troubleshoot, Advanced Options, Startup Settings, Restart; then choose option 4, 5 or 6. After Safe Mode loads, restart to see whether the proper storage drivers load and the drive is recognised. Safe Mode may also be reachable with a function key at boot such as F8, depending on the PC maker.
- Scan the disk. Right-click (or press and hold) the drive, then select Properties, Tools, Check now.
- Run a virus scan that checks the Master Boot Record. Microsoft notes that disk corruption caused by viruses can generate bug check codes.
- IDE devices. Set the onboard IDE port as Primary only, check each IDE device's master, subordinate or stand-alone setting, and try removing all IDE devices except hard disks. Then check the System Log.
- Free space. Make sure the drive has enough free space. Microsoft says the exact need varies but "it's a good idea to have 10% to 15% of free space available."
- Device Manager. Look for devices marked with an exclamation point, review the driver's event log and try updating the related driver.
- Event Viewer. Check the System Log for critical errors in the same time frame as the blue screen.
- Manufacturer diagnostics. Run the hardware diagnostics supplied by the system maker.
- System File Checker. Run
SFC /scannowto scan for and restore corrupted Windows system files. - System Restore. After automatic repair, on the Choose an option screen, select Troubleshoot, Advanced options, System Restore, and pick a restore point from before the error started. Microsoft says restore points are created when you install a new app, driver or update, or when you make one manually.
- Kernel debugger. Attach one and analyse the failure, as the page's remarks describe.
What should you write down first?
Microsoft's "Remarks" section suggests learning as much as possible about the boot drive:
- What type of controller it is connected to, such as SATA or IDE (Device Manager shows the controller and disk driver properties if Windows boots)
- Whether other devices, such as an SSD or DVD drive, share the same controller
- The file system on the drive, typically NTFS
Checklist
- Did you change anything in UEFI (BIOS) recently, especially the storage controller mode?
- Did you add, remove or move a drive or disk controller?
- Did you repartition the system disk or install a disk controller?
- Does Windows reach the desktop at all? That decides which of Microsoft's lists you use
- Important files backed up, or a plan to recover them, before any clean install
- Controller type and file system noted
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
- Bug check 0x7B: INACCESSIBLE_BOOT_DEVICE, Microsoft Learn: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7b--inaccessible-boot-device
- Use the System File Checker tool, Microsoft Support: https://support.microsoft.com/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system
- Bug check code reference, Microsoft Learn: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- Troubleshoot blue screen errors (for regular users): https://www.windows.com/stopcode
- Source: Microsoft Learn, as of 12 October 2026. Checked against the Microsoft Docs source files (MicrosoftDocs/windows-driver-docs). Microsoft documentation is licensed under Creative Commons Attribution 4.0 (CC BY 4.0); this article adapts and summarises it with credit to Microsoft and links to the originals. Microsoft does not endorse this site.
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.