Blue Screen of Death Windows 11: Complete Fix Guide for BSOD Crashes
Fix the Blue Screen of Death on Windows 11 with step-by-step diagnostics, stop codes, driver fixes, memory checks, and registry repairs. Updated 2024.
- Root Cause 1: Faulty or outdated device drivers (graphics, network, storage) are responsible for over 70% of BSOD crashes on Windows 11, especially after OS upgrades.
- Root Cause 2: Corrupt system files, bad RAM modules, or failing SSD/HDD sectors trigger CRITICAL_PROCESS_DIED, MEMORY_MANAGEMENT, and PAGE_FAULT_IN_NONPAGED_AREA stop codes.
- Root Cause 3: Incompatible third-party software, antivirus kernel hooks, or overclocking instability can cause IRQL_NOT_LESS_OR_EQUAL and SYSTEM_SERVICE_EXCEPTION blue screens.
- Quick Fix Summary: Boot into Safe Mode, run 'sfc /scannow' and 'DISM /RestoreHealth' to repair system files, update or roll back problematic drivers via Device Manager, run Windows Memory Diagnostic for RAM issues, and check the Event Viewer minidump logs to identify the exact offending module (.sys file).
| Method | When to Use | Time | Risk |
|---|---|---|---|
| SFC & DISM Scan | System files are corrupt; Windows Update fails; random BSODs | 15–30 min | Low |
| Driver Rollback / Update | BSOD started after a driver or Windows update; stop code mentions a .sys file | 10–20 min | Low |
| Windows Memory Diagnostic | MEMORY_MANAGEMENT or PAGE_FAULT stop codes; RAM was recently changed | 30–60 min | Low |
| Startup Repair (WinRE) | System won't boot past BSOD; cannot reach desktop at all | 20–40 min | Low |
| System Restore | BSOD began after a specific software install or update | 20–45 min | Medium (rolls back changes) |
| CHKDSK Disk Scan | NTFS_FILE_SYSTEM or disk-related stop codes; drive errors in Event Viewer | 30–120 min | Low |
| Clean Boot / Safe Mode | Isolating third-party software or startup service conflicts | 10–15 min | Low |
| Windows Reset (Keep Files) | All other fixes failed; system is too corrupt to repair | 60–180 min | Medium (reinstalls Windows) |
| Full Reinstall (Wipe) | Hardware-verified good but OS is completely unrecoverable | 90–240 min | High (data loss if not backed up) |
Understanding the Blue Screen of Death on Windows 11
The Blue Screen of Death (BSOD) — officially called a Stop Error — appears when Windows 11 encounters a critical fault it cannot recover from safely. Unlike Windows 10, Windows 11 displays a QR code alongside the stop code, making it easier to identify the issue. The screen reads:
Your PC ran into a problem and needs to restart.
We're just collecting some error info, and then we'll restart for you.
Stop code: CRITICAL_PROCESS_DIED
Common stop codes include:
CRITICAL_PROCESS_DIED— a core Windows process terminated unexpectedlyMEMORY_MANAGEMENT— RAM corruption or bad memoryPAGE_FAULT_IN_NONPAGED_AREA— invalid memory access, often driver-relatedIRQL_NOT_LESS_OR_EQUAL— driver tried to access memory at wrong interrupt levelSYSTEM_SERVICE_EXCEPTION— kernel-mode exception from a system serviceNTFS_FILE_SYSTEM— file system or disk controller errorWHEA_UNCORRECTABLE_ERROR— hardware-level CPU/memory errorDPC_WATCHDOG_VIOLATION— a driver took too long to respond
Step 1: Identify the Stop Code and Offending Module
The first step is reading the crash dump. If you can reach the desktop:
- Press Win + X → Event Viewer
- Navigate to Windows Logs → System
- Filter by Critical events around the time of the crash
- Look for BugCheck events and note the stop code and parameter values
Alternatively, use WinDbg or the built-in minidump viewer:
Minidump files are stored at: C:\Windows\Minidump\
You can also check the stop code directly in Settings → System → About → Advanced system settings → Startup and Recovery → Write debugging information. Ensure this is set to Small memory dump (256 KB).
Step 2: Boot into Safe Mode (if you can't reach the desktop)
If your PC loops on the BSOD and won't boot:
- Force three consecutive hard reboots (hold power button during boot) — Windows will auto-boot into 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, Windows loads only essential drivers, which helps isolate whether a third-party driver is causing the crash.
Step 3: Run SFC and DISM to Repair System Files
Corrupt Windows system files are a leading cause of BSODs. Run these commands as Administrator:
sfc /scannow
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
After completion, restart and test for stability.
Step 4: Update or Roll Back Drivers
Driver-related BSODs often reference a .sys file in the stop code (e.g., nvlddmkm.sys for NVIDIA, iaStorA.sys for Intel storage). To fix:
Roll back a driver:
- Press Win + X → Device Manager
- Expand the relevant category (Display Adapters, Network Adapters, etc.)
- Right-click the device → Properties → Driver tab → Roll Back Driver
Update drivers via PowerShell:
Get-WindowsDriver -Online -All | Where-Object {$_.DriverSignature -ne "Signed"}
For NVIDIA GPUs specifically, download the latest driver from nvidia.com and perform a Clean Installation (check "Perform a clean installation" in the installer).
Step 5: Check RAM with Windows Memory Diagnostic
Memory issues cause MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA BSODs.
- Press Win + R → type
mdsched.exe→ Enter - Choose Restart now and check for problems
- The tool runs two passes — results appear after reboot in Event Viewer under MemoryDiagnostics-Results
For more thorough testing, use MemTest86 (bootable USB) which runs outside Windows and tests all RAM banks independently.
Step 6: Run CHKDSK on Your System Drive
Disk errors trigger NTFS_FILE_SYSTEM and related stop codes:
chkdsk C: /f /r /x
You'll be prompted to schedule the scan on next restart since the system drive is in use. Type Y and reboot.
Step 7: Use System Restore
If the BSOD started after a specific change:
- Boot into WinRE (or press Win + R → rstrui.exe)
- Select a restore point dated before the issue began
- Follow the wizard — your personal files are preserved
Step 8: Perform a Startup Repair
For BSODs during boot:
- Boot into WinRE → Troubleshoot → Advanced Options → Startup Repair
- Windows scans and attempts automatic repair of boot configuration
You can also manually repair the BCD (Boot Configuration Data):
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
Step 9: Reset Windows 11 (Last Resort)
If all else fails:
- Win + I → System → Recovery → Reset this PC
- Choose Keep my files to preserve personal data
- Select Cloud download for a fresh Windows image from Microsoft's servers
This reinstalls Windows while keeping your personal files intact but removing installed applications.
Step 10: Hardware Diagnostics (WHEA_UNCORRECTABLE_ERROR)
If you see WHEA_UNCORRECTABLE_ERROR, the issue is likely hardware:
- CPU: Check for overheating (use HWiNFO64 to monitor temps — throttle should not exceed TJMax)
- RAM: Try reseating sticks; test one stick at a time
- GPU: Reseat the graphics card; check PCIe slot
- PSU: A failing power supply causes intermittent hardware faults
- Motherboard: Check for capacitor damage or bent CPU socket pins
For overclocking users: reset BIOS to defaults (load optimized defaults) as unstable overclocks are a primary cause of WHEA_UNCORRECTABLE_ERROR and CLOCK_WATCHDOG_TIMEOUT.
Frequently Asked Questions
# ============================================================
# Windows 11 BSOD Diagnostic & Fix Script
# Run as Administrator in PowerShell or Command Prompt
# ============================================================
# STEP 1: Check for recent BSOD stop codes in Event Viewer
Write-Host "=== Recent BSOD Events ==="
Get-WinEvent -LogName System -MaxEvents 100 | Where-Object {$_.Id -eq 41 -or $_.Id -eq 1001} | Select-Object TimeCreated, Id, Message | Format-List
# STEP 2: List all minidump files (crash dumps)
Write-Host "`n=== Minidump Files ==="
Get-ChildItem -Path "C:\Windows\Minidump" -Filter "*.dmp" | Sort-Object LastWriteTime -Descending | Select-Object Name, LastWriteTime, Length
# STEP 3: Run System File Checker
Write-Host "`n=== Running SFC Scan ==="
sfc /scannow
# STEP 4: Run DISM to repair the component store
Write-Host "`n=== Running DISM Health Check ==="
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /RestoreHealth
# STEP 5: Check disk for errors (schedules on next reboot for C: drive)
Write-Host "`n=== Scheduling CHKDSK on next boot ==="
# Uncomment the line below to schedule CHKDSK
# echo Y | chkdsk C: /f /r /x
# STEP 6: List unsigned / potentially problematic drivers
Write-Host "`n=== Checking for Unsigned Drivers ==="
Get-WindowsDriver -Online -All | Where-Object {$_.DriverSignature -ne "Signed"} | Select-Object OriginalFileName, ProviderName, Version, Date
# STEP 7: List recently installed drivers (last 30 days)
Write-Host "`n=== Drivers Installed in Last 30 Days ==="
$cutoff = (Get-Date).AddDays(-30)
Get-WindowsDriver -Online -All | Where-Object {$_.Date -gt $cutoff} | Select-Object OriginalFileName, ProviderName, Version, Date | Sort-Object Date -Descending
# STEP 8: Check RAM for errors using built-in tool
Write-Host "`n=== Launching Windows Memory Diagnostic ==="
# Uncomment to run immediately:
# Start-Process -FilePath "mdsched.exe"
# STEP 9: Check for pending Windows Updates
Write-Host "`n=== Checking Windows Update Status ==="
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10
# STEP 10: Export system info to a file for further analysis
Write-Host "`n=== Exporting System Info ==="
msinfo32 /report "$env:USERPROFILE\Desktop\SystemInfo.txt"
Write-Host "System info saved to Desktop\SystemInfo.txt"
# STEP 11: Check disk health via SMART data (requires admin)
Write-Host "`n=== Disk Health Check ==="
Get-PhysicalDisk | Select-Object FriendlyName, MediaType, HealthStatus, OperationalStatus, Size | Format-Table -AutoSize
# STEP 12: Check CPU temperature (requires HWiNFO or third-party; placeholder)
Write-Host "`n=== Thermal Check (manual step) ==="
Write-Host "Download HWiNFO64 from https://www.hwinfo.com to monitor CPU/GPU temps."
Write-Host "Ensure CPU stays below TJMax (typically 100C) and GPU below 90C under load."
Write-Host "`n=== BSOD Diagnostic Complete. Review output above and act on findings. ==="Error Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, Windows system administrators, and SRE professionals with combined decades of experience diagnosing OS-level failures, kernel panics, and system crashes across enterprise and consumer environments. Our guides are based on hands-on lab testing, official Microsoft documentation, and real-world incident post-mortems. We specialize in translating complex stop codes and crash dumps into plain-English, actionable troubleshooting steps.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- https://support.microsoft.com/en-us/windows/resolving-stop-blue-screen-errors-in-windows-a9e1a5b7-2a6d-87af-b5d8-0e50b3a1d5d0
- https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference
- https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sfc
- https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism-image-management-command-line-options-s14
- https://stackoverflow.com/questions/tagged/bsod
- https://answers.microsoft.com/en-us/windows/forum/all/blue-screen-of-death-bsod-windows-11/topics