How to Fix Blue Screen of Death (BSOD) on Windows 10 and 11
Getting random blue screen crashes with stop codes like CRITICAL_PROCESS_DIED or IRQL_NOT_LESS_OR_EQUAL? This guide helps you decode the stop code, identify the root cause — driver conflicts, corrupted system files, bad RAM, or overheating — and fix it.
- ✓Checks drivers, system files, disk health, and memory in one automated pass
- ✓Maps stop codes to specific root causes instead of guessing
- ✓Separates software-fixable crashes from hardware failures so you know whether to repair or replace
Best for recurring BSODs, post-update crashes, random stop codes, and driver-related blue screens on Windows 10 and 11.
Main Troubleshooting Guide
How to Fix Driver Issues →Complete symptoms, causes, and step-by-step solutions
Symptoms
You might be experiencing this problem if you notice:
- •Computer crashes to a blue screen displaying a stop code and a sad face emoticon
- •Stop codes like CRITICAL_PROCESS_DIED, IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, or MEMORY_MANAGEMENT
- •System restarts unexpectedly without warning — you lose unsaved work
- •BSOD happens during specific activities like gaming, video editing, or running multiple programs
- •Blue screen appears shortly after installing new hardware, a driver update, or a Windows Update
- •BSOD on every boot attempt — cannot reach the desktop at all
- •Crashes happen at random intervals — sometimes once a day, sometimes every hour
- •Blue screen appears during Windows startup before the login screen loads
- •Computer freezes completely for a few seconds before the blue screen appears
- •BSOD only happens when the system is under heavy load (CPU or GPU at high usage)
- •Minidump files accumulating in C:\Windows\Minidump after each crash
Common types of blue screen crashes on Windows
Driver-Related BSODs
The most common BSOD type. A faulty, incompatible, or recently updated driver causes the kernel to crash. Stop codes like IRQL_NOT_LESS_OR_EQUAL, DRIVER_IRQL_NOT_LESS_OR_EQUAL, and SYSTEM_SERVICE_EXCEPTION usually point here. GPU, network, and USB drivers are the most frequent offenders.
Memory & RAM Failures
Bad RAM causes unpredictable BSODs because corrupted memory data crashes whichever system component reads it. Stop codes change randomly between crashes. MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA are classic RAM-related codes. Windows Memory Diagnostic or MemTest86 confirms the diagnosis.
System File Corruption
Damaged Windows system files (DLLs, registry hives, component store entries) cause crashes when the OS tries to use them. Often caused by improper shutdowns, failed updates, or malware. CRITICAL_PROCESS_DIED is a hallmark code. SFC and DISM repairs usually fix this.
Overheating & Thermal Crashes
When CPU or GPU temperature exceeds safe limits, Windows crashes to prevent physical damage to the hardware. BSODs only during gaming, rendering, or heavy multitasking are a strong indicator. Dust buildup, blocked vents, and degraded thermal paste are common causes.
What RescuePC checks when your PC keeps crashing to a blue screen
Blue screen crashes are one of the hardest Windows problems to diagnose because the stop code only tells you the category — not the specific cause. A single stop code like SYSTEM_SERVICE_EXCEPTION can be caused by a driver, a system file, or a hardware fault. RescuePC narrows down the actual cause systematically.
- →Scans for corrupted or missing system files using SFC and DISM repair sequences
- →Identifies recently changed or incompatible drivers that match common BSOD triggers
- →Checks disk health for bad sectors and SMART warnings that cause read/write crashes
- →Detects pending Windows Updates that may have introduced instability
- →Verifies system file integrity across the Windows component store
Most useful when you're getting repeated BSODs with different stop codes, when you can't identify whether the cause is a driver, system file, or hardware issue, or when you've tried basic fixes and the crashes continue.
Manual troubleshooting vs RescuePC
On your own
- •Searching the stop code online and reading through multiple articles with conflicting advice
- •Manually running SFC, DISM, chkdsk, and Memory Diagnostic one by one — each takes 10-30 minutes
- •Trying to identify the faulty driver by checking Device Manager and rolling back drivers individually
- •Reading minidump files with WinDbg or BlueScreenView to find the faulting module — requires technical knowledge
- •Booting into Safe Mode, uninstalling updates, testing hardware — a multi-hour troubleshooting process
With RescuePC
- →Runs system file integrity checks (SFC/DISM) and driver analysis in a single diagnostic pass
- →Identifies common BSOD-triggering configurations: corrupted files, outdated drivers, pending updates
- →Checks disk health to rule out storage-related crashes
- →Provides targeted repair actions based on the specific issues found, not generic advice
BSODs are intimidating because the error messages look cryptic and the causes range from software to hardware. Manual diagnosis involves multiple separate tools run sequentially. RescuePC consolidates the software-side checks into one pass so you know whether the problem is fixable with software or requires hardware attention.
When this page is most likely to help
- ✓You're getting blue screen crashes with stop codes on Windows 10 or 11
- ✓BSODs started after a driver update, Windows Update, or new hardware installation
- ✓Your PC crashes during specific activities like gaming or video editing
- ✓You're getting random BSODs with different stop codes each time
- ✓The BSOD shows a specific code like CRITICAL_PROCESS_DIED, IRQL_NOT_LESS_OR_EQUAL, or MEMORY_MANAGEMENT
- ✓You've tried restarting but the BSODs keep happening
Most BSOD crashes on Windows are caused by driver conflicts, corrupted system files, or failing RAM — all of which are diagnosable with the right tools and fixable without reinstalling Windows.
When software fixes may not be enough for blue screen crashes
Some BSODs are caused by hardware failures that no software repair can fix.
- ⚠Windows Memory Diagnostic or MemTest86 reports RAM errors — the faulty memory stick needs physical replacement
- ⚠CHKDSK finds bad sectors that keep reappearing — the storage drive is failing and needs replacement
- ⚠CPU or GPU temperatures exceed 90°C even after cleaning dust and replacing thermal paste — the cooling system is damaged or inadequate
- ⚠BSODs persist in Safe Mode and after a clean Windows install — this strongly indicates a hardware fault (RAM, motherboard, or PSU)
- ⚠The BSOD happens during POST or before Windows starts loading — this is a BIOS/firmware or hardware issue, not a Windows problem
Common Causes
- ⚠Faulty or incompatible drivers — GPU drivers (NVIDIA, AMD, Intel), network adapter drivers, and USB controller drivers are the most common BSOD triggers
- ⚠Failing RAM — a bad memory stick causes random data corruption that crashes the kernel
- ⚠Corrupted Windows system files — damage to the component store (WinSxS) or critical DLLs from improper shutdowns, malware, or failed updates
- ⚠Overheating CPU or GPU — when temperatures exceed safe limits, Windows crashes to prevent hardware damage
- ⚠Recent Windows Update introducing a driver incompatibility or replacing a working driver with a broken one
- ⚠Failing storage drive — bad sectors on an HDD or a degrading SSD cause read/write errors that crash the system
- ⚠Third-party antivirus or security software installing kernel-mode drivers that conflict with Windows
- ⚠Overclocked CPU, GPU, or RAM running outside stable parameters — even a minor overclock instability causes BSODs under load
- ⚠BIOS/UEFI firmware bugs — outdated motherboard firmware can cause system instability, especially after a Windows feature update
- ⚠Power supply issues — an underpowered or failing PSU causes voltage drops that crash the system during high power draw
Solutions
Solution 1: Read the Stop Code to Identify the Cause
- 1When the blue screen appears, note the stop code displayed (e.g., CRITICAL_PROCESS_DIED, IRQL_NOT_LESS_OR_EQUAL)
- 2If the PC restarted too fast: go to Settings > System > About > Advanced system settings > Startup and Recovery > Settings > uncheck "Automatically restart" — this keeps the BSOD on screen so you can read it
- 3Check recent minidump files: open C:\Windows\Minidump — each .dmp file is a crash log
- 4Search the exact stop code online to narrow down the cause — each code points to a specific category (driver, memory, disk, etc.)
- 5Common codes: IRQL_NOT_LESS_OR_EQUAL = driver issue, MEMORY_MANAGEMENT = RAM issue, CRITICAL_PROCESS_DIED = system file corruption, SYSTEM_SERVICE_EXCEPTION = driver or software conflict
Solution 2: Update or Roll Back Drivers
- 1Press Windows + X and select Device Manager
- 2Look for devices with yellow warning icons — these have driver problems
- 3Right-click the device > Update driver > Search automatically
- 4If the BSOD started after a driver update: right-click > Properties > Driver tab > Roll Back Driver
- 5Pay special attention to: Display adapters (GPU), Network adapters, USB controllers, and Storage controllers
- 6For GPU drivers: uninstall completely using DDU (Display Driver Uninstaller) in Safe Mode, then install a fresh driver from NVIDIA/AMD/Intel
- 7Restart after making any driver changes
Solution 3: Run SFC and DISM System Repair
- 1Open Command Prompt as Administrator (search "cmd", right-click, Run as administrator)
- 2Run: sfc /scannow — this checks all protected system files and replaces corrupted ones
- 3Wait for the scan to complete (10-15 minutes)
- 4If SFC reports it found and fixed files, restart and test
- 5If SFC reports files it could not fix: run DISM /Online /Cleanup-Image /RestoreHealth — this repairs the component store that SFC uses as its source
- 6Wait for DISM to complete (15-30 minutes, requires internet)
- 7Run sfc /scannow again after DISM to verify all repairs completed
- 8Restart your computer
Solution 4: Test RAM with Windows Memory Diagnostic
- 1Search for "Windows Memory Diagnostic" in the Start menu
- 2Click "Restart now and check for problems"
- 3The test runs automatically before Windows loads (takes 10-20 minutes)
- 4After reboot: press Windows + X > Event Viewer > Windows Logs > System
- 5Look for "MemoryDiagnostics-Results" — it will say "no errors" or report problems
- 6If errors are detected: the faulty RAM stick needs replacement
- 7For more thorough testing: download MemTest86 (free), create a bootable USB, and run for at least 4 passes — Windows Memory Diagnostic misses some errors that MemTest86 catches
- 8If you have multiple RAM sticks, test each one individually to identify which is faulty
Solution 5: Uninstall Recent Windows Updates in Safe Mode
- 1Hold Shift and click Restart from the Start menu (or force 3 hard reboots to trigger recovery)
- 2Go to Troubleshoot > Advanced options > Startup Settings > Restart
- 3Press 4 or F4 for Safe Mode (press 5 or F5 for Safe Mode with Networking if you need internet)
- 4In Safe Mode: open Settings > Windows Update > Update history > Uninstall updates
- 5Remove the most recent quality or feature update — sort by date to find it
- 6If you can't boot to Safe Mode: use Troubleshoot > Advanced options > Uninstall Updates directly from the recovery menu
- 7Restart normally and check if the BSOD is resolved
- 8If it is, pause updates temporarily (Settings > Windows Update > Pause updates) until a fixed update is released
Solution 6: Check Disk Health
- 1Open Command Prompt as Administrator
- 2Run: wmic diskdrive get status — should say "OK" for each drive
- 3Run: chkdsk C: /f /r — this checks for and repairs file system errors and bad sectors
- 4Type Y to schedule the scan on next restart, then restart
- 5Let the scan complete (may take 1-2 hours on large drives)
- 6If bad sectors are found and keep reappearing: the drive is failing — back up data immediately
- 7For SSDs: check the drive manufacturer's tool for SMART health and remaining lifespan percentage
Solution 7: Check for Overheating
- 1Download HWMonitor or Core Temp (both free) to monitor CPU and GPU temperatures
- 2Check idle temps: CPU should be 35-50°C, GPU 30-45°C at idle
- 3Run a stress test or the activity that triggers the BSOD — watch temps in real time
- 4Danger zone: CPU above 90°C or GPU above 95°C will cause thermal shutdowns and BSODs
- 5Clean dust from fans, vents, and heatsinks with compressed air — dust buildup is the #1 cause of overheating
- 6Ensure laptop vents are not blocked (don't use on soft surfaces like beds or couches)
- 7If temps remain high after cleaning: thermal paste between CPU and heatsink may need replacement (common on systems 3+ years old)
- 8If BSODs only happen during gaming or heavy tasks: overheating is a strong suspect
Solution 8: Reset Overclocks to Default
- 1If you've overclocked your CPU, GPU, or RAM — reset everything to default speeds
- 2For CPU/RAM overclocks: enter BIOS (Del or F2 during startup) and load "Optimized Defaults" or "Default Settings"
- 3For GPU overclocks: open MSI Afterburner, EVGA Precision, or your overclocking tool and reset to stock
- 4Even XMP/DOCP RAM profiles can cause instability — try disabling XMP in BIOS and running RAM at its base speed
- 5If BSODs stop after resetting overclocks: incrementally re-apply settings to find the stability threshold
- 6Note: "factory overclock" GPUs and CPUs (like Intel Turbo Boost) are different from manual overclocks and are generally stable
Diagnose and fix a blue screen (BSOD) — the exact commands
A BSOD is almost always a corrupted system file, a failing driver, or bad RAM. These commands (elevated) check all three. Note the stop code shown on the blue screen first — it narrows down which one.
sfc /scannowScans and repairs corrupted protected system files, one of the most common BSOD causes.
DISM /Online /Cleanup-Image /RestoreHealthRepairs the Windows component store that SFC relies on to fix files.
chkdsk C: /f /rChecks the system drive for file-system errors and bad sectors (runs on the next reboot).
mdsched.exeLaunches Windows Memory Diagnostic to test your RAM — a frequent cause of random blue screens.
Minidumps are saved to C:\Windows\Minidump — the stop code plus the named driver there points to the exact culprit. RescuePC reads these automatically and maps the stop code to the matching repair.
What kind of blue screen problem are you experiencing?
BSOD happens at random times with different stop codes each time
Likely cause: Failing RAM is the most likely cause when stop codes change randomly. Bad memory causes unpredictable data corruption that crashes different system components each time. Run Windows Memory Diagnostic or MemTest86 to confirm.
BSOD always shows the same stop code (e.g., IRQL_NOT_LESS_OR_EQUAL or SYSTEM_SERVICE_EXCEPTION)
Likely cause: A specific driver conflict or corrupted system file is triggering the same crash path every time. Check if a driver was recently updated — roll it back. If no recent changes, run SFC /scannow and DISM to repair system files.
BSOD only happens during gaming, video editing, or other GPU-intensive tasks
Likely cause: Overheating GPU or an unstable GPU driver. Check GPU temperature during the activity — if it exceeds 90-95°C, the card is thermal throttling and crashing. If temps are fine, uninstall the GPU driver with DDU in Safe Mode and install a fresh version.
BSOD started happening after a Windows Update
Likely cause: The update replaced a working driver with an incompatible one, or introduced a system file conflict. Boot into Safe Mode, uninstall the most recent update, and pause updates temporarily. Check Device Manager for any devices with yellow warning icons.
BSOD on every boot — cannot reach the desktop
Likely cause: Critical system file corruption, a bad driver loading at startup, or a failing boot drive. Use the Windows Recovery Environment: Troubleshoot > Advanced Options > Startup Repair first. If that fails, try Safe Mode and uninstall recent drivers/updates. If Safe Mode also crashes, the boot drive may be failing.
BSOD with INACCESSIBLE_BOOT_DEVICE or PAGE_FAULT_IN_NONPAGED_AREA
Likely cause: Storage or memory hardware fault. INACCESSIBLE_BOOT_DEVICE means Windows can't read the boot drive — often a failing HDD/SSD or a storage controller driver issue. PAGE_FAULT_IN_NONPAGED_AREA usually points to bad RAM or a driver accessing invalid memory. Test both disk health and RAM.
Best next step
Good fit for recurring blue screen crashes, stop code errors, driver conflicts, system file corruption, and post-update BSODs on Windows 10 and 11.
Why RescuePC handles BSOD diagnosis well
Blue screens are the most feared Windows error because they seem catastrophic and the stop codes are cryptic. In reality, most BSODs are caused by just three categories: driver conflicts, corrupted system files, and hardware faults. The hard part is figuring out which category applies to your specific crash.
- →Checks system file integrity with SFC and DISM to detect and repair corruption
- →Identifies recently changed or incompatible drivers that match known BSOD patterns
- →Verifies disk health to rule out storage-related crash causes
- →Separates software-fixable issues from hardware faults so you know whether a repair or a replacement is needed
Related Error Codes
Browse More Crashes & Blue Screens Guides
Frequently asked questions about blue screen crashes
What does the stop code on the blue screen mean?▼
Is a blue screen dangerous? Can it damage my computer?▼
Why do I get different stop codes each time?▼
Should I reinstall Windows to fix BSODs?▼
Can a Windows update cause blue screen crashes?▼
Related Troubleshooting Guides
These specific guides cover common variations of this problem: