Blue Screen of Death Windows 11: Complete Fix Guide (BSOD Troubleshooting)
Fix Blue Screen of Death on Windows 11 with step-by-step diagnostics, PowerShell commands, driver rollbacks, and memory checks. Resolve BSODs fast.
- Root cause 1: Faulty, outdated, or incompatible device drivers (especially GPU, network, and storage drivers) are the #1 cause of Windows 11 BSODs, often showing stop codes like DRIVER_IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA.
- Root cause 2: Corrupted system files, bad Windows updates, or failing RAM/SSD hardware trigger stop codes such as CRITICAL_PROCESS_DIED, SYSTEM_SERVICE_EXCEPTION, MEMORY_MANAGEMENT, and WHEA_UNCORRECTABLE_ERROR.
- Quick fix summary: Boot into Safe Mode if the system won't start, run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' to repair system files, check the Event Viewer and minidump files in C:\Windows\Minidump for the exact stop code, roll back or update suspect drivers, run Windows Memory Diagnostic, and as a last resort perform a Windows 11 Startup Repair or Reset.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| SFC + DISM Repair | Corrupted system files, random BSODs after Windows Update | 15-30 min | Low |
| Driver Rollback / Update | BSOD after installing new hardware or driver update (DRIVER_IRQL, DPC_WATCHDOG_VIOLATION) | 10-20 min | Low |
| Windows Memory Diagnostic | MEMORY_MANAGEMENT or WHEA_UNCORRECTABLE_ERROR stop codes, system crashes under load | 30-60 min | None |
| Safe Mode Boot + Uninstall | System won't boot normally, recent software/driver installation caused BSOD loop | 10-15 min | Low |
| Startup Repair (WinRE) | System stuck in BSOD boot loop, cannot reach desktop at all | 20-40 min | Low-Medium |
| Check Disk (CHKDSK) | NTFS_FILE_SYSTEM or BAD_SYSTEM_CONFIG_INFO stop codes, disk-related errors | 30-90 min | Low |
| Windows 11 Reset (Keep Files) | Persistent BSODs with no identifiable cause, all other methods failed | 60-120 min | Medium |
| Clean Windows 11 Reinstall | Hardware is healthy but OS is severely corrupted, last resort | 120-180 min | High (data loss risk) |
Understanding the Blue Screen of Death on Windows 11
The Blue Screen of Death (BSOD) in Windows 11 presents as a solid blue screen with a frowning emoji, a brief error message, and a QR code. Unlike Windows 10, Windows 11 BSODs may also appear as a black screen briefly before the system restarts. The operating system halts entirely to prevent data corruption when a critical error occurs in kernel space.
When a BSOD occurs, Windows writes a minidump file to C:\Windows\Minidump\ and optionally a full memory dump to C:\Windows\MEMORY.DMP. These files are your primary diagnostic source.
Common stop codes you will encounter include:
CRITICAL_PROCESS_DIED— a core Windows process terminated unexpectedlySYSTEM_SERVICE_EXCEPTION— usually a faulty driver calling a system service incorrectlyDRIVER_IRQL_NOT_LESS_OR_EQUAL— a driver accessed memory at the wrong interrupt request levelPAGE_FAULT_IN_NONPAGED_AREA— a driver or component tried to access a non-existent memory pageMEMORY_MANAGEMENT— RAM hardware failure or memory addressing errorWHEA_UNCORRECTABLE_ERROR— hardware-level error (CPU, GPU, or RAM)DPC_WATCHDOG_VIOLATION— a deferred procedure call ran too long, often GPU or SSD driver relatedBAD_SYSTEM_CONFIG_INFO— corrupted registry or BCD storeNTFS_FILE_SYSTEM— disk/filesystem corruption
Step 1: Collect the Stop Code and Minidump
If your PC reboots too fast to read the stop code, disable automatic restart:
- Press
Win + R, typesysdm.cpl, press Enter. - Go to Advanced → Startup and Recovery → Settings.
- Uncheck Automatically restart under System failure.
- Click OK.
Now open Event Viewer (eventvwr.msc) → Windows Logs → System and look for critical errors with the source BugCheck. The Event ID 1001 entry will contain the full stop code and parameters.
To read minidump files, install WinDbg from the Microsoft Store or use the free WhoCrashed tool (resplendence.com). WhoCrashed will analyze all minidumps and identify the likely culprit driver in plain English.
Step 2: Boot Into Safe Mode (If System Won't Start)
If your PC is in a BSOD boot loop:
- Force-shutdown the PC 3 times during the Windows logo to trigger Windows Recovery Environment (WinRE).
- Select Troubleshoot → Advanced Options → Startup Settings → Restart.
- Press F4 for Safe Mode or F5 for Safe Mode with Networking.
In Safe Mode, only essential drivers load. If the BSOD stops in Safe Mode, a third-party driver or startup program is the culprit.
Step 3: Repair System Files with SFC and DISM
Open an elevated PowerShell or Command Prompt and run the following commands in order:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
DISM repairs the Windows Component Store first; SFC then uses the repaired store to fix individual corrupted system files. After both complete, restart the PC and check whether the BSOD recurs.
Step 4: Update or Roll Back Drivers
Driver issues cause the majority of Windows 11 BSODs. Focus on:
- GPU drivers: Open Device Manager (
devmgmt.msc) → Display Adapters → right-click your GPU → Update Driver or Roll Back Driver. - Network adapter drivers: Especially Realtek and Intel Wi-Fi drivers are known to cause
DRIVER_IRQL_NOT_LESS_OR_EQUALon Windows 11. - Storage/NVMe drivers:
DPC_WATCHDOG_VIOLATIONis frequently caused by Samsung or Intel NVMe drivers conflicting with the Windows 11 inbox driver.
To identify which driver caused the crash, check the minidump module name in WhoCrashed or WinDbg. If the offending .sys file is identified (e.g., nvlddmkm.sys for NVIDIA, iaStorA.sys for Intel RST), uninstall that driver from Device Manager and either reinstall the latest version from the manufacturer's website or use the Windows default driver.
Step 5: Check RAM with Windows Memory Diagnostic
For MEMORY_MANAGEMENT, WHEA_UNCORRECTABLE_ERROR, or random BSODs:
- Press
Win + R, typemdsched.exe, press Enter. - Choose Restart now and check for problems.
- Windows will run the test on next boot (takes 15-30 minutes).
- Results appear in Event Viewer → Windows Logs → System, source
MemoryDiagnostics-Results.
For more thorough testing, boot MemTest86 (memtest86.com) from a USB drive and run at least 2 full passes. Any errors indicate failing RAM that must be replaced.
Step 6: Run CHKDSK for Disk Errors
For NTFS_FILE_SYSTEM, BAD_SYSTEM_CONFIG_INFO, or storage-related BSODs:
chkdsk C: /f /r /x
This schedules a disk check on next reboot (/f fixes errors, /r locates bad sectors, /x forces dismount). Allow it to complete fully — this can take 1-2 hours on large drives.
Also check your SSD/HDD health using CrystalDiskInfo (free tool). A drive showing Caution or Bad reallocated sectors should be replaced immediately.
Step 7: Check for Windows Update Issues
A faulty cumulative update can introduce BSODs. Check installed updates:
- Open Settings → Windows Update → Update History.
- Click Uninstall Updates and remove the most recently installed KB update.
- Restart and observe stability.
Alternatively, use the Windows Update Troubleshooter in Settings → System → Troubleshoot → Other troubleshooters.
Step 8: Startup Repair and Last Resorts
If all else fails, boot into WinRE and run Startup Repair (Troubleshoot → Advanced Options → Startup Repair). This fixes BCD store corruption and missing boot files.
If Startup Repair doesn't work, use System Restore to roll back to a point before BSODs started (only available if restore points exist).
As a final option, perform a Windows 11 Reset (Settings → System → Recovery → Reset this PC → Keep my files). This reinstalls Windows while preserving personal data but removes installed applications.
Frequently Asked Questions
# ============================================================
# Windows 11 BSOD Diagnostic & Fix Script
# Run in an elevated PowerShell (Run as Administrator)
# ============================================================
# --- Step 1: Display the last 10 BugCheck events from Event Log ---
Write-Host "=== Recent BugCheck (BSOD) Events ==="
Get-WinEvent -LogName System -MaxEvents 500 |Where-Object { $_.Id -eq 1001 -and $_.ProviderName -eq 'Microsoft-Windows-WER-SystemErrorReporting' } |Select-Object -First 10 TimeCreated, Message |Format-List
# --- Step 2: List all minidump files with timestamps ---
Write-Host "`n=== Minidump Files ==="
Get-ChildItem -Path "C:\Windows\Minidump" -Filter "*.dmp" -ErrorAction SilentlyContinue |Sort-Object LastWriteTime -Descending |Select-Object Name, LastWriteTime, @{N='SizeMB';E={[math]::Round($_.Length/1MB,2)}}
# --- Step 3: Run DISM health check and repair ---
Write-Host "`n=== Running DISM RestoreHealth ==="
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
# --- Step 4: Run System File Checker ---
Write-Host "`n=== Running SFC Scan ==="
sfc /scannow
# --- Step 5: Schedule CHKDSK on next reboot for C: drive ---
Write-Host "`n=== Scheduling CHKDSK ==="
echo Y | chkdsk C: /f /r /x
# --- Step 6: Check for driver issues using DriverQuery ---
Write-Host "`n=== Non-Microsoft Kernel Drivers (potential BSOD culprits) ==="
driverquery /v /fo csv |ConvertFrom-Csv |Where-Object { $_.State -eq 'Running' -and $_.'Start Mode' -eq 'System' } |Select-Object 'Display Name','Module Name','Driver Type','Link Date' |Sort-Object 'Link Date' -Descending |Select-Object -First 20 |Format-Table -AutoSize
# --- Step 7: Check RAM slots and memory info ---
Write-Host "`n=== Memory Information ==="
Get-WmiObject -Class Win32_PhysicalMemory |Select-Object BankLabel, DeviceLocator, @{N='CapacityGB';E={[math]::Round($_.Capacity/1GB,2)}}, Speed, Manufacturer |Format-Table -AutoSize
# --- Step 8: Check disk health via SMART status ---
Write-Host "`n=== Disk Health Status ==="
Get-WmiObject -Namespace root\wmi -Class MSStorageDriver_FailurePredictStatus |Select-Object InstanceName, PredictFailure, Reason |Format-Table -AutoSize
# --- Step 9: List recent Windows Updates (check for problematic KB) ---
Write-Host "`n=== Last 10 Installed Windows Updates ==="
Get-HotFix |Sort-Object InstalledOn -Descending |Select-Object -First 10 HotFixID, Description, InstalledOn |Format-Table -AutoSize
# --- Step 10: Enable Driver Verifier for non-MS drivers (CAUTION: may cause BSOD to identify bad driver) ---
# Uncomment the line below ONLY if you want to enable Driver Verifier:
# verifier /standard /all
# To disable Driver Verifier after testing:
# verifier /reset
Write-Host "`n=== Diagnostics Complete. Review output above and check C:\Windows\Minidump with WhoCrashed or WinDbg ==="
Write-Host "Next steps: Reboot to complete CHKDSK, then run Windows Memory Diagnostic (mdsched.exe) if RAM issues are suspected."Error Medic Editorial
The Error Medic Editorial team consists of senior DevOps engineers, SREs, and Windows systems administrators with 10+ years of experience diagnosing OS-level failures, kernel crashes, and production system incidents. We specialize in translating cryptic stop codes and system errors into clear, actionable remediation steps for both developers and IT professionals.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/driver-verifier
- https://support.microsoft.com/en-us/windows/fix-blue-screen-errors-in-windows-0dfdf5a8-4c6e-b37a-a1c8-68f6a3d5e8e6
- https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sfc
- https://stackoverflow.com/questions/tagged/bsod
- https://answers.microsoft.com/en-us/windows/forum/all/windows-11-blue-screen-of-death/
- https://github.com/MicrosoftDocs/windows-driver-docs/blob/staging/windows-driver-docs-pr/debugger/bug-check-0x3b--system-service-exception.md