Windows 11 Keeps Blue Screening (BSOD): Complete Troubleshooting Guide
Fix Windows 11 blue screen of death errors fast. Step-by-step guide covering driver updates, memory tests, SFC scans, and registry fixes to stop BSODs.
- Faulty or outdated drivers are the #1 cause of Windows 11 BSODs — especially after a major update or new hardware installation.
- Corrupted system files, failing RAM, overheating hardware, and bad disk sectors are other frequent root causes of repeated blue screens.
- Quick fixes include running 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' in an elevated Command Prompt, checking Windows Event Viewer for the stop code, rolling back recent driver updates, and running Windows Memory Diagnostic to rule out RAM failures.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| SFC & DISM Scan | Corrupted system files suspected; after Windows Update failures | 15–30 min | Low |
| Driver Rollback / Update | BSOD started after new hardware or Windows Update | 10–20 min | Low |
| Windows Memory Diagnostic | Random BSODs with stop codes like MEMORY_MANAGEMENT or PAGE_FAULT | 30–60 min | None |
| Check Disk (chkdsk) | BSODs with NTFS_FILE_SYSTEM or CRITICAL_PROCESS_DIED stop codes | 30–120 min | Low |
| Clean Boot / Safe Mode | Identifying third-party software or service conflicts | 20–40 min | Low |
| System Restore | BSODs began after a recent software or driver change | 20–45 min | Medium |
| Reinstall Windows 11 | All other fixes failed; persistent hardware-unrelated BSODs | 1–3 hours | High — backup data first |
Understanding Why Windows 11 Keeps Blue Screening
A Blue Screen of Death (BSOD) — technically called a Stop Error — occurs when Windows 11 encounters a critical system failure it cannot recover from. The screen displays a stop code such as SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, IRQL_NOT_LESS_OR_EQUAL, MEMORY_MANAGEMENT, CRITICAL_PROCESS_DIED, or KERNEL_SECURITY_CHECK_FAILURE. Each stop code points toward a specific category of failure.
When your PC or laptop keeps blue screening on Windows 11, the underlying cause almost always falls into one of these buckets:
- Driver conflicts or corruption (most common)
- Corrupted Windows system files
- Faulty RAM or storage hardware
- Overheating CPU or GPU
- Incompatible or malicious software
- Recent Windows Update gone wrong
Step 1: Read the Stop Code
Before fixing anything, collect the exact stop code from the blue screen. If the BSOD disappears too quickly:
- Press Win + R, type
sysdm.cpl, press Enter. - Go to Advanced → Startup and Recovery → Settings.
- Under System failure, uncheck Automatically restart.
- Click OK. Now Windows will hold the blue screen so you can read the stop code.
Alternatively, after reboot, check the minidump log:
- Press Win + R, type
eventvwr.msc, press Enter. - Navigate to Windows Logs → System.
- Filter for Critical and Error events around the time of the crash.
- Look for BugCheck events — these contain the stop code and parameters.
You can also use WinDbg (Windows Debugger) to open dump files located at C:\Windows\Minidump\ for a full analysis.
Step 2: Run SFC and DISM to Repair System Files
Corrupted system files are a leading cause of repeated BSODs. The System File Checker (SFC) and Deployment Image Servicing and Management (DISM) tools can detect and repair them.
Open Command Prompt as Administrator (search 'cmd', right-click → Run as administrator) and run:
sfc /scannow
Wait for the scan to complete. If it reports Windows Resource Protection found corrupt files but was unable to fix some of them, proceed with DISM:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
After DISM completes, rerun sfc /scannow and then restart your PC.
Step 3: Update or Roll Back Drivers
Drivers are the most frequent cause of Windows 11 BSODs. Stop codes like DRIVER_IRQL_NOT_LESS_OR_EQUAL, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, and DRIVER_POWER_STATE_FAILURE almost always point to a bad driver.
To 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.
To update all drivers automatically via PowerShell:
Get-WindowsDriver -Online | Where-Object {$_.Driver -like "*.inf"}
For GPU drivers, always download directly from NVIDIA, AMD, or Intel websites rather than Windows Update.
If you recently installed a new driver and the BSODs started, boot into Safe Mode (hold Shift while clicking Restart → Troubleshoot → Advanced Options → Startup Settings → Safe Mode with Networking) and uninstall the problematic driver from Device Manager.
Step 4: Run Windows Memory Diagnostic
Bad RAM causes unpredictable BSODs, often with stop codes like MEMORY_MANAGEMENT, PAGE_FAULT_IN_NONPAGED_AREA, or WHEA_UNCORRECTABLE_ERROR.
- Press Win + R, type
mdsched.exe, press Enter. - Choose Restart now and check for problems.
- Windows will reboot and run a memory test. Results appear after the next login in Event Viewer under Windows Logs → System, source: MemoryDiagnostics-Results.
For a more thorough test, use MemTest86 (bootable USB), which runs outside Windows and catches errors that the built-in tool misses.
Step 5: Check Disk for Errors
A failing or corrupted drive triggers BSODs with codes like NTFS_FILE_SYSTEM, CRITICAL_PROCESS_DIED, or INACCESSIBLE_BOOT_DEVICE.
Run in elevated Command Prompt:
chkdsk C: /f /r /x
Windows will prompt you to schedule the check on next reboot since the C: drive is in use. Type Y and restart. For SSDs, also check the manufacturer's health tool (Samsung Magician, CrystalDiskInfo, etc.) for reallocated sector counts and wear level.
Step 6: Check for Overheating
Thermal throttling and shutdowns can manifest as BSODs, especially on laptops. Use HWiNFO64 or Core Temp to monitor CPU and GPU temperatures under load. Safe operating ranges:
- CPU: below 90°C under full load
- GPU: below 85°C under full load
If temperatures are too high:
- Clean dust from vents and fans
- Reapply thermal paste on CPU (advanced)
- Use a laptop cooling pad
- Check BIOS/UEFI for fan control settings
Step 7: Perform a Clean Boot
Third-party applications and services can conflict with Windows 11 and trigger BSODs. A clean boot loads only Microsoft services:
- Press Win + R, type
msconfig, press Enter. - On the Services tab, check Hide all Microsoft services, then click Disable all.
- Go to the Startup tab → click Open Task Manager → disable all startup items.
- Click OK and restart.
If BSODs stop in clean boot, re-enable services in batches to isolate the culprit.
Step 8: Uninstall Recent Windows Updates
A faulty cumulative update can introduce BSODs across many systems. To uninstall:
- Go to Settings → Windows Update → Update history → Uninstall updates.
- Sort by date and remove the most recently installed update.
- Restart and test.
You can also use the Windows Recovery Environment (WinRE): Troubleshoot → Advanced Options → Uninstall Updates.
Step 9: Use System Restore
If BSODs started after a specific event (driver install, software install, update), System Restore can revert Windows to a stable state without affecting personal files.
- Press Win + R, type
rstrui.exe, press Enter. - Choose a restore point dated before the BSODs began.
- Follow the wizard and restart.
Step 10: Reset or Reinstall Windows 11
If all else fails, use Settings → System → Recovery → Reset this PC. Choose Keep my files for a non-destructive reinstall, or Remove everything for a full clean install. Always back up important data to an external drive or cloud storage before this step.
For persistent hardware-related BSODs that survive a clean install, test the hardware in another system or contact the manufacturer for warranty support.
Frequently Asked Questions
# ============================================================
# Windows 11 BSOD Diagnostic & Fix Script
# Run in elevated PowerShell (Run as Administrator)
# ============================================================
Write-Host "=== Step 1: System File Checker ==" -ForegroundColor Cyan
sfc /scannow
Write-Host "
=== Step 2: DISM Health Restore ===" -ForegroundColor Cyan
DISM /Online /Cleanup-Image /RestoreHealth
Write-Host "
=== Step 3: Schedule Disk Check on C: ===" -ForegroundColor Cyan
echo Y | chkdsk C: /f /r /x
Write-Host "
=== Step 4: List Recent BSOD Events from Event Log ===" -ForegroundColor Cyan
Get-WinEvent -LogName System | Where-Object { $_.Id -eq 41 -or $_.Id -eq 1001 } | Select-Object -First 10 | Format-List TimeCreated, Message
Write-Host "
=== Step 5: List Minidump Files ===" -ForegroundColor Cyan
$dumpPath = "C:\Windows\Minidump"
if (Test-Path $dumpPath) {
Get-ChildItem $dumpPath -Filter *.dmp | Sort-Object LastWriteTime -Descending | Select-Object -First 5 | Format-Table Name, LastWriteTime, Length
} else {
Write-Host "No minidump folder found. Ensure small memory dumps are configured." -ForegroundColor Yellow
}
Write-Host "
=== Step 6: Check Driver Verifier Status ===" -ForegroundColor Cyan
verifier /query
Write-Host "
=== Step 7: Export System Info to Desktop ===" -ForegroundColor Cyan
$reportPath = "$env:USERPROFILE\Desktop\BSODReport_$(Get-Date -Format 'yyyyMMdd_HHmmss').txt"
Get-ComputerInfo | Out-File $reportPath
Write-Host "System info saved to: $reportPath" -ForegroundColor Green
Write-Host "
=== Step 8: Check Windows Update History for Recent Updates ===" -ForegroundColor Cyan
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10 | Format-Table HotFixID, InstalledOn, Description
Write-Host "
=== Step 9: List Installed Drivers Sorted by Date ===" -ForegroundColor Cyan
Get-WindowsDriver -Online | Sort-Object Date -Descending | Select-Object -First 15 | Format-Table ProviderName, ClassName, Version, Date
Write-Host "
Diagnostic complete. Review the output above and check your Desktop for BSODReport file." -ForegroundColor Green
# To enable Driver Verifier for detecting faulty drivers (ADVANCED - causes intentional BSODs):
# verifier /standard /all
# To disable Driver Verifier after testing:
# verifier /resetError Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, Windows systems administrators, and SRE professionals with 10+ years of experience diagnosing OS-level failures, kernel panics, and hardware faults across enterprise and consumer environments. Our guides are tested on real hardware and verified against official Microsoft documentation.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- https://support.microsoft.com/en-us/windows/fix-a-blue-screen-error-in-windows-2f04d0b7-4d6d-4b8e-837c-7b1b1b79c0b3
- 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://answers.microsoft.com/en-us/windows/forum/all/windows-11-random-bsod-issues/
- https://github.com/microsoft/winget-cli/issues/
- https://stackoverflow.com/questions/tagged/bsod+windows-11