Windows Stop Code on Windows 11: Complete Troubleshooting Guide (Including INACCESSIBLE_BOOT_DEVICE)
Fix Windows 11 stop code BSODs fast. Step-by-step fixes for INACCESSIBLE_BOOT_DEVICE, CRITICAL_PROCESS_DIED, and more. Restore your PC in minutes.
- Windows 11 stop codes (BSODs) are caused by driver corruption, failing hardware (RAM/SSD/HDD), incompatible software, or corrupted system files — the specific stop code text tells you exactly where to look first.
- INACCESSIBLE_BOOT_DEVICE is the most common stop code on Windows 11 and usually points to a missing or corrupted storage driver, a failed Windows Update, or a misconfigured boot partition.
- Quick fix summary: boot into Safe Mode or the Windows Recovery Environment (WinRE), run SFC /scannow and DISM, roll back recent drivers or updates, and use the built-in Memory Diagnostic tool to rule out RAM failure — most BSODs resolve within these four steps.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Startup Repair (WinRE) | PC won't boot at all; repeated BSOD loop | 5-15 min | Low |
| SFC /scannow + DISM | Occasional BSOD; Windows boots but crashes | 15-30 min | Low |
| Driver Rollback / Uninstall | BSOD started after a driver or Windows Update | 5-10 min | Low |
| System Restore | BSOD appeared after a software or settings change | 15-30 min | Medium — reverts recent changes |
| Windows Memory Diagnostic | Random BSODs with no clear pattern; suspect RAM | 30-60 min | None — read-only test |
| Rebuild BCD / Fix MBR | INACCESSIBLE_BOOT_DEVICE; bootloader errors | 10-20 min | Medium — modifies boot data |
| Reset / Clean Install Windows 11 | All other steps failed; hardware confirmed healthy | 60-120 min | High — data loss possible |
Understanding Windows 11 Stop Codes
A Windows Stop Code — colloquially known as the Blue Screen of Death (BSOD) — is Windows 11's last-resort safety mechanism. When the kernel detects a condition from which it cannot safely recover (memory corruption, an unresponsive critical driver, a missing boot device), it halts all processes, displays a QR code and a plain-English stop code name, and writes a minidump file to C:\Windows\Minidump\.
Common Windows 11 stop codes include:
INACCESSIBLE_BOOT_DEVICE(0x0000007B)CRITICAL_PROCESS_DIED(0x000000EF)SYSTEM_SERVICE_EXCEPTION(0x0000003B)KERNEL_SECURITY_CHECK_FAILURE(0x00000139)PAGE_FAULT_IN_NONPAGED_AREA(0x00000050)MEMORY_MANAGEMENT(0x0000001A)DRIVER_IRQL_NOT_LESS_OR_EQUAL(0x000000D1)WHEA_UNCORRECTABLE_ERROR(0x00000124)
Each name is a direct pointer to the subsystem that failed. The number in parentheses is the bug check code recorded in the minidump and the Windows Event Log under Event ID 1001.
Step 1: Identify the Exact Stop Code and Read the Minidump
Before attempting any fix, you need to know exactly which stop code you're dealing with and what triggered it.
If Windows 11 boots:
- Press
Win + R, typeeventvwr.msc, press Enter. - Navigate to Windows Logs → System.
- Filter by Event ID 1001 (BugCheck). The description contains the stop code and the faulting module.
- Open WinDbg (available via the Microsoft Store as "Windows Debugger") and load the latest minidump from
C:\Windows\Minidump\to read the faulting driver.
If Windows 11 will not boot (BSOD loop):
- Boot from a Windows 11 USB installer or allow Windows to enter the Recovery Environment automatically after three failed boots.
- Select Troubleshoot → Advanced Options → Startup Settings → Restart.
- Choose option 4 (Safe Mode) or 5 (Safe Mode with Networking).
- Once in Safe Mode, follow the steps above.
Step 2: Fix INACCESSIBLE_BOOT_DEVICE on Windows 11
This is the most searched Windows 11 stop code. It means Windows cannot find the partition it was installed on during startup. Common causes:
- A Windows Update changed storage controller drivers (especially switching SATA modes in BIOS from AHCI to IDE, or vice versa).
- The
iaStorAV.sysorstorahci.sysdriver is corrupted. - The Boot Configuration Data (BCD) is damaged.
- An NVMe SSD firmware issue.
Fix A — Run Startup Repair from WinRE:
- Boot from Windows 11 USB media.
- Click Repair your computer → Troubleshoot → Advanced Options → Startup Repair.
- Let the tool run and restart.
Fix B — Rebuild the BCD manually (see code block below).
Fix C — Check BIOS SATA Mode:
- Reboot and enter BIOS/UEFI (usually
Del,F2, orF10). - Locate Storage Configuration or SATA Mode.
- If it reads IDE, change to AHCI. If it was recently changed to AHCI, change back to IDE and test.
- Save and reboot.
Step 3: Repair System Files with SFC and DISM
Corrupted Windows system files cause the majority of stop codes not related to hardware. Run these tools in order:
- Open an elevated Command Prompt (right-click Start → Terminal (Admin)).
- Run DISM first to repair the component store:
DISM /Online /Cleanup-Image /RestoreHealth - After DISM completes successfully, run SFC:
sfc /scannow - Restart the PC. If SFC reports it found and repaired files, the BSOD should be resolved.
Step 4: Roll Back Problematic Drivers
If the BSOD started after installing new hardware or a Windows Update:
- Boot into Safe Mode.
- Press
Win + X → Device Manager. - Expand the relevant category (Display Adapters, Network Adapters, Storage Controllers).
- Right-click the device → Properties → Driver tab → Roll Back Driver.
- If Roll Back is greyed out, right-click → Uninstall Device, then restart so Windows reinstalls a stable version.
For display driver issues (NVIDIA/AMD), use Display Driver Uninstaller (DDU) in Safe Mode for a completely clean removal before reinstalling the latest WHQL-certified driver.
Step 5: Test RAM with Windows Memory Diagnostic
Random BSODs with codes like MEMORY_MANAGEMENT or PAGE_FAULT_IN_NONPAGED_AREA often indicate failing RAM.
- Press
Win + R, typemdsched.exe, press Enter. - Choose Restart now and check for problems.
- The tool runs in a pre-boot environment for 1-2 passes. Results appear in Event Viewer under Windows Logs → System, Event source MemoryDiagnostics-Results after reboot.
- If errors are found, reseat RAM sticks, test each stick individually, and replace faulty modules.
Step 6: Check Storage Health
A failing SSD or HDD causes INACCESSIBLE_BOOT_DEVICE, NTFS_FILE_SYSTEM, and similar stop codes.
# Check drive health via PowerShell (requires admin)
Get-PhysicalDisk | Select-Object FriendlyName, MediaType, OperationalStatus, HealthStatus
For deeper S.M.A.R.T. data, use CrystalDiskInfo (free) or the manufacturer's diagnostic tool (Samsung Magician, Seagate SeaTools, Western Digital Dashboard).
Step 7: Uninstall Recent Windows Updates
Windows 11 cumulative updates occasionally introduce driver conflicts.
- Go to Settings → Windows Update → Update History → Uninstall Updates.
- Sort by date and uninstall the most recent Cumulative Update.
- Restart and test.
- To prevent the update from reinstalling temporarily, use the Show or Hide Updates troubleshooter from Microsoft.
Step 8: System Restore
If you have restore points enabled:
- In WinRE: Troubleshoot → Advanced Options → System Restore.
- Choose a restore point dated before the BSODs began.
- This does not affect personal files but reverts drivers, registry settings, and installed applications to the selected point.
Step 9: Reset or Clean Install Windows 11 (Last Resort)
If all else fails and hardware checks are clean:
- Settings → System → Recovery → Reset this PC.
- Choose Keep my files for a non-destructive reset, or Remove everything for a full clean install.
- Alternatively, boot from a Windows 11 USB created with the Media Creation Tool and perform a fresh installation.
Frequently Asked Questions
# ============================================================
# Windows 11 Stop Code Diagnostic & Fix Commands
# Run from an Elevated Command Prompt or PowerShell (Admin)
# For WinRE commands, boot from Windows 11 USB first
# ============================================================
# --- STEP 1: Repair System Files ---
# Repair the Windows component store first
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
# Then run System File Checker
sfc /scannow
# --- STEP 2: Rebuild Boot Configuration Data (BCD) ---
# Run these from WinRE Command Prompt (Advanced Options > Command Prompt)
# Use when stop code is INACCESSIBLE_BOOT_DEVICE
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
# If bootrec /fixboot returns "Access is Denied", run:
bcdboot C:\Windows /s C: /f ALL
# --- STEP 3: Check and Repair Disk Errors ---
# Schedule a chkdsk on the next reboot (C: is the Windows drive)
chkdsk C: /f /r /x
# --- STEP 4: List and Identify Minidump Files ---
# PowerShell: list recent crash dumps by date
Get-ChildItem -Path "C:\Windows\Minidump" -Filter "*.dmp" | Sort-Object LastWriteTime -Descending | Select-Object Name, LastWriteTime, Length
# --- STEP 5: Check Drive Health via PowerShell ---
Get-PhysicalDisk | Select-Object FriendlyName, MediaType, OperationalStatus, HealthStatus, Size
# --- STEP 6: View Recent BSOD Events in Event Log ---
# PowerShell: pull last 10 BugCheck events (Event ID 1001)
Get-WinEvent -FilterHashtable @{LogName='System'; Id=1001} -MaxEvents 10 | Format-List TimeCreated, Message
# --- STEP 7: Check SATA Controller Driver Status ---
# Verify storahci driver is running (important for INACCESSIBLE_BOOT_DEVICE)
Get-Service -Name storahci | Select-Object Name, Status, StartType
# --- STEP 8: Uninstall a Problematic Windows Update (PowerShell) ---
# List installed KBs sorted by date
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10 HotFixID, Description, InstalledOn
# Remove a specific KB (replace KB5XXXXXX with actual KB number)
wusa /uninstall /kb:5XXXXXX /quiet /norestart
# --- STEP 9: Enable Verbose BSOD Info (disable auto-restart) ---
# Prevent Windows from auto-rebooting so you can read the stop code
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v AutoReboot /t REG_DWORD /d 0 /f
# --- STEP 10: Analyze Minidump with WinDbg (run in WinDbg command window) ---
# !analyze -v
# .symfix C:\Symbols
# .reload
# !analyze -v
# lmvm <driver_name> (e.g., lmvm nvlddmkm)Error Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Windows systems administrators with 10+ years of experience diagnosing and resolving operating system failures across enterprise and consumer environments. Our guides are tested against real crash dumps and live Windows 11 installations before publication.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference
- https://learn.microsoft.com/en-us/windows/client-management/troubleshoot-stop-errors
- https://support.microsoft.com/en-us/windows/fix-windows-stop-errors-or-blue-screens-8f9e3f11-4d57-87ea-84f6-c9e01d5a9a4e
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7b--inaccessible-boot-device
- https://answers.microsoft.com/en-us/windows/forum/all/windows-11-blue-screen-inaccessiblebootdevice/
- https://stackoverflow.com/questions/tagged/bsod