Windows Stop Code on Windows 11: How to Fix Blue Screen Errors (BSOD)
Fix Windows Stop Code errors on Windows 11 including INACCESSIBLE_BOOT_DEVICE. Step-by-step guide with commands to diagnose and resolve BSODs fast.
- Windows Stop Code errors (BSODs) on Windows 11 are triggered by driver conflicts, corrupted system files, failing hardware, faulty RAM, or an inaccessible boot device — each code pinpoints a specific subsystem failure.
- The INACCESSIBLE_BOOT_DEVICE stop code typically means Windows 11 cannot read the boot partition, usually caused by a corrupt BCD store, misconfigured SATA/NVMe drivers, or a disk failure after a bad update.
- Quick fix summary: Boot into Windows Recovery Environment (WinRE), run 'sfc /scannow' and 'DISM /RestoreHealth', rebuild the BCD with 'bootrec /rebuildbcd', roll back recent drivers or updates, and run Windows Memory Diagnostic to rule out RAM issues.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| SFC + DISM Scan | Corrupted system files causing random BSODs | 15-30 min | Low |
| BCD Rebuild (bootrec) | INACCESSIBLE_BOOT_DEVICE or boot loop after update | 10-20 min | Medium |
| Driver Rollback / Uninstall | BSOD started after a driver or Windows update | 5-15 min | Low |
| Windows Memory Diagnostic | Suspected faulty RAM causing random stop codes | 30-60 min | Low |
| Startup Repair (WinRE) | Cannot boot into Windows at all | 10-30 min | Low |
| Reset / Reinstall Windows 11 | Persistent BSODs with no other fix working | 1-3 hrs | High (data loss risk) |
| chkdsk /r /f | Disk errors or bad sectors suspected | 30-120 min | Medium |
| Safe Mode + Antivirus Scan | Malware-induced BSOD or corrupted drivers | 20-60 min | Low |
Understanding Windows Stop Code Errors on Windows 11
A Windows Stop Code — colloquially called a Blue Screen of Death (BSOD) — is Windows 11's way of halting execution when the kernel encounters a condition it cannot safely recover from. The screen displays a sad face emoji, a brief message like "Your PC ran into a problem and needs to restart", and a stop code such as:
INACCESSIBLE_BOOT_DEVICECRITICAL_PROCESS_DIEDSYSTEM_THREAD_EXCEPTION_NOT_HANDLEDMEMORY_MANAGEMENTKERNEL_SECURITY_CHECK_FAILUREPAGE_FAULT_IN_NONPAGED_AREADPC_WATCHDOG_VIOLATION
Each code maps to a specific Windows kernel bug check value (hexadecimal). For example, INACCESSIBLE_BOOT_DEVICE maps to 0x0000007B. Understanding the stop code narrows your diagnosis significantly before you run a single command.
Step 1: Capture and Identify the Stop Code
If you can boot into Windows 11 normally:
- Press Win + R, type
eventvwr.msc, and press Enter. - Navigate to Windows Logs > System.
- Filter for Event ID 41 (unexpected shutdown) and Event ID 1001 (BugCheck) to find the exact stop code and memory dump reference.
You can also read the most recent minidump file:
- Navigate to
C:\Windows\Minidump\ - Use WinDbg (available free from the Microsoft Store) or the BlueScreenView utility to parse
.dmpfiles without symbols.
If you are stuck in a boot loop:
- Force-restart your PC three times in a row — Windows 11 will automatically enter Windows Recovery Environment (WinRE).
- Select Troubleshoot > Advanced Options > Startup Settings to access Safe Mode or the Command Prompt.
- Alternatively, boot from a Windows 11 USB and select Repair your computer.
Step 2: Fix Corrupted System Files (SFC and DISM)
Corrupted Windows system files are a frequent root cause of multiple stop codes. Open an elevated Command Prompt or PowerShell:
sfc /scannow
If SFC reports it cannot fix all errors, run DISM to repair the Windows image itself:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
After DISM completes, re-run sfc /scannow and then restart.
Step 3: Fix INACCESSIBLE_BOOT_DEVICE (0x0000007B)
This is the most disruptive stop code because Windows 11 cannot reach its boot partition. Common triggers include:
- A Windows Update that changed the SATA/NVMe storage controller driver
- A corrupted Boot Configuration Data (BCD) store
- BitLocker recovery state blocking boot
- A failing SSD or HDD
Rebuild the BCD from WinRE Command Prompt:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
If bootrec /fixboot returns "Access is denied", the EFI partition is likely formatted with FAT32 and needs manual assignment:
diskpart
list disk
sel disk 0
list vol
sel vol <EFI volume number>
assign letter=G
exit
bcdboot C:\Windows /s G: /f UEFI
Roll back the storage driver if the BSOD appeared after a Windows Update:
- Boot into Safe Mode (WinRE > Startup Settings > Safe Mode with Networking).
- Open Device Manager (
devmgmt.msc). - Expand IDE ATA/ATAPI controllers or Storage controllers.
- Right-click your controller > Properties > Driver > Roll Back Driver.
Step 4: Diagnose and Fix Memory Issues
Faulty RAM triggers stop codes like MEMORY_MANAGEMENT (0x0000001A) and PAGE_FAULT_IN_NONPAGED_AREA (0x00000050).
Run Windows Memory Diagnostic:
- Press Win + R, type
mdsched.exe, press Enter. - Choose Restart now and check for problems.
- After restart, results appear in Event Viewer under Windows Logs > System, Event ID 1201.
For deeper testing, use MemTest86 (bootable USB) for at least two full passes.
Step 5: Check Disk Health
Run Check Disk to find and repair bad sectors:
chkdsk C: /r /f
Schedule it for next reboot if the drive is in use. Also query disk health via PowerShell:
Get-PhysicalDisk | Select-Object FriendlyName, HealthStatus, OperationalStatus
For NVMe drives, use the manufacturer's tool (Samsung Magician, WD Dashboard, CrystalDiskInfo) to check SMART data.
Step 6: Uninstall Problematic Updates or Drivers
If the BSOD started after a specific Windows Update:
- Go to Settings > Windows Update > Update History > Uninstall Updates.
- Identify the most recent cumulative update (KB number) and uninstall it.
- Pause updates temporarily while you troubleshoot.
To uninstall a driver cleanly (e.g., GPU driver causing SYSTEM_THREAD_EXCEPTION_NOT_HANDLED):
- Boot into Safe Mode.
- Use Display Driver Uninstaller (DDU) in safe mode to fully strip GPU drivers.
- Reinstall a known stable driver version from the manufacturer's site.
Step 7: Last Resort — Startup Repair and Reset
If all else fails:
- Startup Repair: WinRE > Troubleshoot > Advanced Options > Startup Repair. This automates BCD and boot file repair.
- Reset this PC: WinRE > Troubleshoot > Reset this PC. Choose Keep my files to preserve personal data while reinstalling Windows 11 system files.
- Clean Install: Download the Windows 11 ISO from Microsoft, create a bootable USB with the Media Creation Tool, and perform a fresh installation.
Pro Tip: Enable Automatic Memory Dumps for Faster Diagnosis
Ensure Windows 11 writes complete crash dumps so you can analyze them later:
- Right-click This PC > Properties > Advanced system settings.
- Under Startup and Recovery, click Settings.
- Set Write debugging information to Automatic memory dump.
- Confirm dump path is
%SystemRoot%\MEMORY.DMP.
Frequently Asked Questions
# ============================================================
# Windows 11 Stop Code Diagnostic & Fix Commands
# Run in an elevated Command Prompt or PowerShell (Admin)
# ============================================================
# --- 1. System File Checker (repair corrupted Windows files) ---
sfc /scannow
# --- 2. DISM Image Repair (fixes SFC when it can't self-heal) ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
# --- 3. Re-run SFC after DISM ---
sfc /scannow
# --- 4. Check Disk for bad sectors (schedules on next reboot) ---
chkdsk C: /r /f
# --- 5. Rebuild Boot Configuration Data (BCD) ---
# Run these from WinRE Command Prompt for INACCESSIBLE_BOOT_DEVICE
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
# --- 6. Reassign EFI partition if bootrec /fixboot gives Access Denied ---
diskpart
# Inside diskpart:
# list disk
# sel disk 0
# list vol
# sel vol <EFI volume number e.g. 2>
# assign letter=G
# exit
bcdboot C:\Windows /s G: /f UEFI
# --- 7. View recent BSOD events via Event Viewer (PowerShell) ---
Get-WinEvent -LogName System | Where-Object {$_.Id -eq 41 -or $_.Id -eq 1001} | Select-Object TimeCreated, Message | Format-List
# --- 8. Check disk/physical drive health (PowerShell) ---
Get-PhysicalDisk | Select-Object FriendlyName, HealthStatus, OperationalStatus, Size
# --- 9. List installed drivers by date (find recently installed/updated drivers) ---
Get-WindowsDriver -Online | Sort-Object Date -Descending | Select-Object -First 20 Driver, Date, ProviderName | Format-Table -AutoSize
# --- 10. Uninstall a Windows Update by KB number (replace KB5034123 with actual KB) ---
wusa /uninstall /kb:5034123 /quiet /norestart
# --- 11. Enable Automatic Memory Dumps via registry (if not already set) ---
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v CrashDumpEnabled /t REG_DWORD /d 1 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v AutoReboot /t REG_DWORD /d 1 /f
# --- 12. Analyze minidump with WinDbg (run inside WinDbg console) ---
# .sympath srv*C:\Symbols*https://msdl.microsoft.com/download/symbols
# .reload
# !analyze -v
# --- 13. List minidump files to confirm dumps are being created ---
dir C:\Windows\Minidump\ /od
# --- 14. Boot into Safe Mode from Command Prompt (for next reboot) ---
bcdedit /set {current} safeboot minimal
# To undo Safe Mode after troubleshooting:
bcdedit /deletevalue {current} safebootError Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Windows system administrators with over a decade of experience diagnosing kernel failures, boot errors, and system crashes across enterprise and consumer environments. We specialize in translating complex OS internals into actionable, step-by-step troubleshooting guides that actually fix the problem.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference
- https://learn.microsoft.com/en-us/windows/client-management/generate-kernel-or-complete-crash-dump
- https://support.microsoft.com/en-us/windows/fix-blue-screen-errors-in-windows-2cd59a4a-ced8-4b1f-b85b-9c958bdbdba6
- https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/bootrec
- https://stackoverflow.com/questions/tagged/bsod
- https://answers.microsoft.com/en-us/windows/forum/all/inaccessible-boot-device-after-windows-11-update/
- https://github.com/microsoft/winget-cli/issues