A blue screen (stop error) always includes a specific stop code — that code is the single most useful piece of information for narrowing down the cause, so start there rather than guessing at fixes.
Common Symptoms
- PC crashes to a blue screen with a stop code like MEMORY_MANAGEMENT or IRQL_NOT_LESS_OR_EQUAL
- Crashes happen randomly, or only under specific conditions (gaming, waking from sleep)
- PC restarts automatically after the crash with no time to read the code
Possible Causes
- A faulty or incompatible device driver, often after an update
- Failing RAM
- A failing hard drive or SSD
- Overheating hardware
- Corrupted system files
Before You Begin
Disable automatic restart on failure (Settings → System → About → Advanced system settings → Startup and Recovery) so you can actually read the stop code next time it happens.
Method 1 — Identify the stop code and check recent changes
Note the exact stop code
Write down the code shown on the blue screen, e.g. DRIVER_IRQL_NOT_LESS_OR_EQUAL.
Method 2 — Roll back or update recent drivers
Check Device Manager
Look for any device with a warning icon, or any driver updated right before the crashes began.
Roll back or reinstall
Roll back a recently updated driver, or reinstall a known-stable version from the manufacturer.
Method 3 — Test memory and disk health
Method 4 — Run System File Checker
Scan for corrupted files
Run sfc /scannow from an elevated Command Prompt (see command below) and restart once complete.
Useful Commands
sfc /scannowIf the crashes started immediately after installing new RAM or a new drive, reseat the hardware and confirm it’s listed as compatible before assuming it’s a software problem.
Watch the Video
Prefer watching? This tutorial covers the same steps.
How to read a Windows 11 stop code and work through the most likely causes before assuming it's a hardware failure.
Watch on YouTube →Frequently Asked Questions
Does a blue screen always mean hardware failure?
No — a driver conflict or corrupted system file is a more common cause than actual failing hardware, especially if the same stop code repeats.
Where can I find more detail about a specific stop code?
Microsoft publishes documentation for each stop code (e.g., “IRQL_NOT_LESS_OR_EQUAL”) describing its typical causes — search the exact code from your crash for the most relevant detail.
Conclusion
Reading the actual stop code and checking Reliability Monitor turns “random crash” into a specific, fixable problem in most cases — reserve hardware replacement for when memory and disk diagnostics confirm a fault.
Related Articles
