Blue Screen of Death Windows 11: Complete Fix Guide for BSOD Errors
Fix Blue Screen of Death on Windows 11 with step-by-step diagnostics, driver rollbacks, memory checks, and registry repairs. Stop codes explained.
- Most Windows 11 BSODs are caused by incompatible or corrupted drivers, especially after a major update or new hardware installation.
- Faulty RAM, overheating hardware, corrupted system files, and misconfigured kernel settings are the other primary root causes.
- Quick fixes include running 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' in an elevated Command Prompt, booting into Safe Mode to uninstall problem drivers, and running Windows Memory Diagnostic to rule out RAM issues.
- Advanced recovery options include System Restore, Startup Repair from WinRE, and analyzing minidump files with WinDbg to identify the exact failing component.
- If all else fails, a clean reinstall of Windows 11 while preserving personal files is the nuclear option that resolves nearly every persistent BSOD scenario.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| SFC & DISM Scan | Corrupted system files, recent update issues | 15-30 min | Low |
| Driver Rollback / Uninstall | BSOD after hardware install or Windows Update | 10-20 min | Low |
| Windows Memory Diagnostic | Suspected RAM failure, random BSODs | 20-60 min | None |
| System Restore | BSOD started after a specific date or install | 20-40 min | Low |
| WinRE Startup Repair | PC cannot boot to desktop at all | 15-30 min | Low |
| Registry Repair via Command Prompt | Boot loop, corrupted hive errors | 30-60 min | Medium |
| WinDbg Minidump Analysis | Recurring BSOD, need exact stop code cause | 30-90 min | None |
| Clean Reinstall (Keep Files) | All other methods failed, persistent BSOD | 60-120 min | Medium |
| Full Format & Reinstall | Malware-related BSOD or drive corruption | 90-180 min | High (data loss) |
Understanding the Blue Screen of Death on Windows 11
The Blue Screen of Death (BSOD) in Windows 11 is a critical system error that forces the OS to halt to prevent hardware or data damage. Unlike Windows 10's older style, Windows 11 BSODs display a dark blue or black screen with a sad emoji, a brief error message, and a QR code. Common stop codes you will encounter include:
- CRITICAL_PROCESS_DIED — A critical system process terminated unexpectedly.
- SYSTEM_THREAD_EXCEPTION_NOT_HANDLED — A system thread generated an exception that the error handler did not catch, often tied to a driver.
- IRQL_NOT_LESS_OR_EQUAL — A kernel-mode process attempted to access memory at an invalid address, typically a driver bug.
- PAGE_FAULT_IN_NONPAGED_AREA — The system tried to access paged memory that wasn't available, usually bad RAM or a driver.
- KERNEL_SECURITY_CHECK_FAILURE — Data corruption detected in kernel-level code.
- MEMORY_MANAGEMENT — A severe memory management error, often pointing to failing RAM or driver conflicts.
- WHEA_UNCORRECTABLE_ERROR — A hardware error reported by Windows Hardware Error Architecture, often CPU or RAM overheating or instability.
- DPC_WATCHDOG_VIOLATION — A Deferred Procedure Call took too long, usually from a driver or SSD firmware issue.
Before attempting any fix, note the full stop code displayed on the BSOD. This is the most important diagnostic clue.
Step 1: Collect Diagnostic Information
1a. Read the Stop Code
When a BSOD occurs, Windows displays a stop code in the format STOP: 0x0000007E or as a named string like IRQL_NOT_LESS_OR_EQUAL. Write this down. If the screen disappears too quickly, disable automatic restart:
- Press Win + R, type
sysdm.cpl, press Enter. - Go to Advanced > Startup and Recovery > Settings.
- Uncheck Automatically restart under System failure.
- Click OK.
1b. Locate Minidump Files
Windows 11 writes crash dumps to C:\Windows\Minidump. These .dmp files contain the full crash context and are invaluable for diagnosis. If the folder is empty, ensure crash dump generation is enabled:
- Open System Properties > Advanced > Startup and Recovery.
- Under Write debugging information, select Small memory dump (256 KB).
- Confirm the dump directory is
%SystemRoot%\Minidump.
1c. Check Event Viewer
Open Event Viewer (eventvwr.msc) and navigate to Windows Logs > System. Filter by Critical and Error level events around the time of the crash. Look for source names like BugCheck, Kernel-Power, or driver names.
Step 2: Run Built-in Repair Tools
2a. System File Checker (SFC) Corrupted Windows system files are a frequent BSOD trigger, especially after failed updates. Open Command Prompt as Administrator and run:
sfc /scannow
This scans all protected system files and replaces corrupted ones. Restart after completion.
2b. DISM Health Restore If SFC reports it cannot fix all errors, the component store itself may be damaged. Run:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
This downloads and restores the component store from Windows Update. Requires an internet connection. After completion, run SFC again.
2c. Check Disk Disk corruption can cause BSODs. Run a full disk check on your system drive:
chkdsk C: /f /r /x
You will be prompted to schedule it on next boot. Type Y, then restart.
Step 3: Driver Troubleshooting
Drivers are the number one cause of Windows 11 BSODs. After a Windows Update or new hardware installation, an incompatible driver can immediately destabilize the kernel.
3a. Boot into Safe Mode If your PC repeatedly crashes before reaching the desktop, boot into Safe Mode:
- Hold Shift and click Restart from the login screen.
- Navigate to Troubleshoot > Advanced Options > Startup Settings > Restart.
- Press 4 or F4 for Safe Mode, or 5/F5 for Safe Mode with Networking.
3b. Identify the Offending Driver
In Safe Mode or after a successful boot, open Device Manager (devmgmt.msc). Look for devices with a yellow warning icon. Additionally, use the WinDbg command in the code block below to analyze your minidump and pinpoint the exact driver module.
3c. Roll Back a Driver
- In Device Manager, right-click the suspect device.
- Select Properties > Driver > Roll Back Driver.
3d. Uninstall and Reinstall the Driver If rollback is unavailable, right-click the device and select Uninstall device. Check Delete the driver software for this device. Restart and let Windows reinstall a generic driver, or download the latest stable version from the manufacturer's website.
3e. Use Display Driver Uninstaller (DDU)
For GPU driver BSODs (nvlddmkm.sys for NVIDIA, atikmdag.sys for AMD), use DDU in Safe Mode for a clean removal before reinstalling the driver.
Step 4: Hardware Diagnostics
4a. Test RAM with Windows Memory Diagnostic
- Press Win + R, type
mdsched.exe, press Enter. - Choose Restart now and check for problems.
- The system will reboot and run an extended memory test. Results appear in Event Viewer after the next login under Windows Logs > System with source MemoryDiagnostics-Results.
For more thorough testing, use MemTest86 from a bootable USB.
4b. Monitor Temperatures Overheating CPUs and GPUs cause immediate BSODs, especially under load. Download HWiNFO64 or Core Temp and monitor temperatures. CPU should stay below 90°C under load; GPU below 85°C. Clean dust from heatsinks and reapply thermal paste if temperatures are excessive.
4c. Check Storage Health Use CrystalDiskInfo to check your SSD or HDD SMART status. A drive showing Caution or Bad status must be replaced immediately.
Step 5: System Restore and Advanced Recovery
5a. System Restore If BSODs started after a specific date:
- Boot into WinRE (hold Shift + Restart).
- Navigate to Troubleshoot > Advanced Options > System Restore.
- Select a restore point predating the BSOD.
5b. Startup Repair For persistent boot loops:
- Boot into WinRE.
- Navigate to Troubleshoot > Advanced Options > Startup Repair.
- Follow the on-screen prompts.
5c. Reset or Reinstall Windows 11 If all else fails:
- Go to Settings > System > Recovery.
- Under Reset this PC, click Reset PC.
- Choose Keep my files to preserve personal data, or Remove everything for a full wipe.
Alternatively, create a Windows 11 installation USB via the Media Creation Tool and perform an in-place upgrade repair, which replaces system files while keeping apps and data.
Frequently Asked Questions
# ============================================================
# Windows 11 BSOD Diagnostic & Repair Script
# Run PowerShell as Administrator
# ============================================================
Write-Host "=== Step 1: Collecting Recent BSOD Events from Event Log ==="
Get-WinEvent -LogName System | Where-Object { $_.Id -eq 41 -or $_.Id -eq 1001 -or $_.Id -eq 6008 } | Select-Object TimeCreated, Id, Message | Format-List
Write-Host "=== Step 2: Listing Minidump Files ==="
$dumpPath = "C:\Windows\Minidump"
if (Test-Path $dumpPath) {
Get-ChildItem -Path $dumpPath -Filter "*.dmp" | Sort-Object LastWriteTime -Descending | Select-Object Name, LastWriteTime, Length
} else {
Write-Host "No minidump directory found. Ensure crash dump is configured."
}
Write-Host "=== Step 3: Running System File Checker ==="
Start-Process -FilePath "sfc" -ArgumentList "/scannow" -Wait -NoNewWindow
Write-Host "=== Step 4: Running DISM Health Restore ==="
Start-Process -FilePath "DISM" -ArgumentList "/Online /Cleanup-Image /RestoreHealth" -Wait -NoNewWindow
Write-Host "=== Step 5: Checking Disk for Errors (Schedule on Reboot) ==="
# This schedules chkdsk on C: at next boot
cmd /c "echo Y | chkdsk C: /f /r /x"
Write-Host "=== Step 6: Exporting Driver List to Desktop ==="
$desktopPath = [Environment]::GetFolderPath("Desktop")
Get-WmiObject Win32_PnPSignedDriver | Select-Object DeviceName, DriverVersion, DriverDate, Manufacturer | Export-Csv -Path "$desktopPath\InstalledDrivers.csv" -NoTypeInformation
Write-Host "Driver list saved to $desktopPath\InstalledDrivers.csv"
Write-Host "=== Step 7: Checking for Recently Installed or Updated Drivers ==="
Get-WmiObject Win32_PnPSignedDriver | Where-Object { $_.DriverDate -gt (Get-Date).AddDays(-30).ToString("yyyyMMdd000000.000000+000") } | Select-Object DeviceName, DriverVersion, DriverDate | Format-Table -AutoSize
Write-Host "=== Step 8: Checking RAM via Windows Memory Diagnostic (Scheduled) ==="
# Schedules memory test on next reboot
cmd /c "mdsched.exe"
Write-Host "=== Step 9: Checking for Pending Windows Updates ==="
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10 | Format-Table HotFixID, InstalledOn, Description -AutoSize
Write-Host "=== Step 10: Verifying Boot Configuration ==="
bcdedit /enum all
Write-Host ""
Write-Host "=== Diagnostic Script Complete. Review output above. ==="
Write-Host "For WinDbg analysis: Install from Microsoft Store, open latest .dmp file, run: !analyze -v"
Write-Host "Safe Mode entry: Hold Shift + Restart > Troubleshoot > Advanced Options > Startup Settings"
# ---- OPTIONAL: Force Safe Mode on Next Boot (uncomment to use) ----
# bcdedit /set safeboot minimal
# Write-Host "Safe mode forced on next boot. To revert: bcdedit /deletevalue safeboot"
# ---- OPTIONAL: Check Thermal Data via WMI ----
# Get-WmiObject MSAcpi_ThermalZoneTemperature -Namespace "root/wmi" | Select-Object InstanceName, CurrentTemperature | ForEach-Object { [PSCustomObject]@{ Zone = $_.InstanceName; TempCelsius = ($_.CurrentTemperature - 2732) / 10 } }Error Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Windows system administrators with 10+ years of experience diagnosing and resolving operating system failures across enterprise and consumer environments. Our guides are built from real incident postmortems, vendor documentation, and hands-on lab testing to ensure every step is actionable and accurate.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- https://support.microsoft.com/en-us/windows/fix-blue-screen-errors-in-windows-2ea60822-0b53-0d7e-e9f2-2b8a63a5dc6c
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/analyzing-a-kernel-mode-dump-file-with-windbg
- https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sfc
- https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-recovery-environment--windows-re--technical-reference
- https://stackoverflow.com/questions/tagged/bsod+windows-11