Blue Screen of Death Windows 10: Complete Troubleshooting Guide for All BSOD Error Codes
Fix Blue Screen of Death on Windows 10 fast. Covers CRITICAL_PROCESS_DIED, IRQL_NOT_LESS_OR_EQUAL, MEMORY_MANAGEMENT & more with CMD commands and step-by-step f
- The most common BSOD causes on Windows 10 are faulty drivers, corrupt system files, bad RAM, overheating hardware, and problematic Windows updates.
- Stop codes like CRITICAL_PROCESS_DIED, IRQL_NOT_LESS_OR_EQUAL, MEMORY_MANAGEMENT, KERNEL_SECURITY_CHECK_FAILURE, SYSTEM_SERVICE_EXCEPTION, and UNEXPECTED_STORE_EXCEPTION each point to different root causes and require targeted fixes.
- Run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' in an elevated CMD first, then check Event Viewer and update or roll back drivers to resolve most BSODs without reinstalling Windows.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| SFC + DISM Scan (CMD) | Corrupt system files suspected; first-line fix for most BSODs | 10-30 min | Low |
| Driver Rollback / Update | BSOD started after a driver or Windows Update install | 5-15 min | Low |
| Windows Memory Diagnostic | MEMORY_MANAGEMENT or random/unpredictable BSODs | 15-60 min | None |
| Check Disk (chkdsk) | UNEXPECTED_STORE_EXCEPTION or disk-related stop codes | 20-120 min | Low |
| System Restore | BSOD started after a specific update or software install | 15-30 min | Low-Medium |
| Startup Repair / Safe Mode | Cannot boot into Windows; repeated BSODs on startup | 10-20 min | Low |
| Reinstall / Reset Windows | All other methods failed; unrecoverable system corruption | 60-180 min | High (data loss risk) |
Understanding the Blue Screen of Death on Windows 10
A Blue Screen of Death (BSOD), also called a Stop Error, occurs when Windows 10 encounters a critical error from which it cannot safely recover. The system halts, displays a blue screen with a stop code (e.g., CRITICAL_PROCESS_DIED, MEMORY_MANAGEMENT), and automatically restarts. Each stop code is a clue pointing to the underlying cause.
BSODs can be hardware-triggered (faulty RAM, overheating CPU/GPU, failing SSD/HDD) or software-triggered (corrupt drivers, bad Windows updates, malware, system file corruption). ASUS laptops and desktops often see BSODs related to ASUS-specific drivers such as atk0110.sys or asmtxhci.sys. After a Windows Update, BSODs frequently stem from incompatible or partially installed drivers.
Step 1: Note the Stop Code and Collect Crash Dumps
When the BSOD appears, note the exact stop code shown. Common examples:
CRITICAL_PROCESS_DIED— A critical Windows process terminated unexpectedly.IRQL_NOT_LESS_OR_EQUAL— A driver tried to access memory at an invalid IRQL (usually a driver bug).KERNEL_SECURITY_CHECK_FAILURE— Data structures are corrupted; often caused by outdated drivers or hardware failure.MEMORY_MANAGEMENT— RAM or memory subsystem error.SYSTEM_SERVICE_EXCEPTION— A system service generated an unhandled exception (oftenwin32k.sys,ntfs.sys, or a third-party driver).UNEXPECTED_STORE_EXCEPTION— Storage device (SSD/HDD) failure or driver issue.
To read past crash dump files, open Event Viewer or use WinDbg. For quick analysis, use the free tool WhoCrashed or read minidump files located at C:\Windows\Minidump\.
Using Event Viewer:
- Press
Win + Xand select Event Viewer. - Navigate to Windows Logs > System.
- Filter for Critical and Error level events near the time of the BSOD.
- Look for source
BugCheckwhich shows the stop code and parameters.
Step 2: Boot into Safe Mode (If Windows Won't Start)
If Windows 10 crashes on boot or you keep getting repeated BSODs, enter Safe Mode:
- Force-shutdown the PC 3 times in a row during startup to trigger Automatic Repair.
- Click Advanced options > Troubleshoot > Advanced options > Startup Settings > Restart.
- Press 4 to boot in Safe Mode or 5 for Safe Mode with Networking.
In Safe Mode, Windows loads only essential drivers, making it easier to diagnose whether the issue is driver- or software-related.
Step 3: Run SFC and DISM to Repair System Files
Open Command Prompt as Administrator and run these commands in order:
sfc /scannow
This scans and repairs protected Windows system files. Wait for it to complete (10-15 minutes). If it reports corruption it could not fix, proceed with DISM:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
After DISM completes, run sfc /scannow again. Restart and check if the BSOD recurs.
Step 4: Update or Roll Back Drivers
Drivers are the #1 cause of Windows 10 BSODs. If a BSOD started after a Windows Update or driver installation:
Roll back a driver:
- Press
Win + X> Device Manager. - Expand the relevant category (e.g., Display adapters, Network adapters).
- Right-click the device > Properties > Driver tab > Roll Back Driver.
Update drivers:
- For ASUS systems, check ASUS Support (support.asus.com) for the latest chipset, GPU, and ATK drivers.
- For GPU: Download directly from NVIDIA, AMD, or Intel — not Windows Update.
- Use
winget upgrade --allor manually download from the vendor.
Identify the faulty driver from minidump: Use the command below in an elevated PowerShell to list recently installed drivers:
Get-WinEvent -LogName System | Where-Object {$_.Id -eq 7045} | Select-Object TimeCreated, Message | Format-List
Step 5: Run Windows Memory Diagnostic
For MEMORY_MANAGEMENT BSODs or random/unpredictable crashes:
- Press
Win + R, typemdsched.exe, press Enter. - Choose Restart now and check for problems.
- The test runs on reboot and takes 15-60 minutes.
- Results are shown in Event Viewer under Windows Logs > System (source:
MemoryDiagnostics-Results).
If errors are found, reseat your RAM sticks, try one stick at a time, or replace faulty RAM.
Step 6: Check Disk for Errors
For UNEXPECTED_STORE_EXCEPTION or storage-related BSODs, run:
chkdsk C: /f /r /x
Schedule on next reboot if the drive is in use. This scans for bad sectors and file system errors. For SSDs, also check the drive's health using CrystalDiskInfo or the manufacturer's tool.
Step 7: Undo Recent Windows Updates
If a BSOD started after Windows Update:
- Open Settings > Update & Security > View Update History > Uninstall Updates.
- Sort by date and uninstall the most recent Cumulative Update or Feature Update.
- Alternatively, use CMD:
wusa /uninstall /kb:XXXXXXX
Replace XXXXXXX with the KB number shown in update history.
To temporarily pause updates: Settings > Update & Security > Windows Update > Advanced Options > Pause Updates.
Step 8: Check for Overheating
Overheating causes hardware-protection BSODs (especially KERNEL_SECURITY_CHECK_FAILURE and random crashes). Use HWMonitor or Core Temp to check CPU and GPU temperatures. Normal CPU temps: under 80°C under load. If overheating:
- Clean dust from vents and fans.
- Reapply thermal paste on CPU (if older than 3-4 years).
- Ensure proper case airflow.
- Underclock GPU using MSI Afterburner if GPU-related.
Step 9: Scan for Malware
Some malware causes or mimics BSODs. Run Windows Defender offline scan:
Start-MpScan -ScanType OfflineScan
Or boot into Windows Defender Offline mode from Settings > Windows Security > Virus & threat protection > Scan options > Microsoft Defender Offline scan.
Step 10: System Restore or Reset Windows
If all else fails:
- System Restore: Press
Win + R, typerstrui.exe, and restore to a point before BSODs began. - Reset Windows: Settings > Update & Security > Recovery > Reset this PC. Choose Keep my files to preserve personal data while reinstalling Windows.
Frequently Asked Questions
# ============================================================
# Windows 10 BSOD Diagnostic & Fix Script
# Run in an elevated (Administrator) Command Prompt or PowerShell
# ============================================================
# STEP 1: Scan and repair Windows system files
sfc /scannow
# STEP 2: DISM to repair the Windows image (run all three)
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
# STEP 3: Re-run SFC after DISM completes
sfc /scannow
# STEP 4: Schedule disk check on next reboot (fixes bad sectors)
chkdsk C: /f /r /x
# STEP 5: List recent minidump files to identify crash pattern
dir C:\Windows\Minidump /od
# STEP 6: View BugCheck events in Event Log (stop codes)
wevtutil qe System /q:"*[System[Provider[@Name='Microsoft-Windows-WER-SystemErrorReporting']]]" /f:text /rd:true /c:10
# STEP 7: List recently installed drivers (PowerShell)
Get-WinEvent -LogName System | Where-Object {$_.Id -eq 7045} | Select-Object TimeCreated, Message | Format-List
# STEP 8: Check for Windows updates that can be uninstalled
wmic qfe list brief /format:table
# STEP 9: Uninstall a specific KB update (replace KB number)
# wusa /uninstall /kb:5034441
# STEP 10: Run Memory Diagnostic (schedules on reboot)
Start-Process mdsched.exe
# STEP 11: Windows Defender full offline scan (PowerShell)
Start-MpScan -ScanType FullScan
# STEP 12: Export system info for further analysis
msinfo32 /report C:\Users\Public\SystemInfo.txt
# STEP 13: Reset Windows Update components (if update-related BSOD)
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
# ============================================================
# After running these commands, restart and monitor for BSODs.
# If BSODs continue, boot into Safe Mode and test hardware.
# ============================================================Error Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, SRE specialists, and Windows system administrators with 10+ years of experience diagnosing and resolving critical system errors across enterprise and consumer environments. Our guides combine hands-on lab testing, real crash dump analysis, and Microsoft's official documentation to deliver actionable, accurate troubleshooting content for developers and IT professionals.
Sources
- https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- https://support.microsoft.com/en-us/windows/troubleshoot-blue-screen-errors-in-windows-10-and-11-2b2bd3e4-4d25-4f7c-8c01-2d88e97e1eba
- https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/using-the-windows-defender-system-guard-runtime-guide
- https://answers.microsoft.com/en-us/windows/forum/all/blue-screen-of-death-windows-10/
- https://stackoverflow.com/questions/tagged/windows-10+blue-screen
- https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sfc