How to Troubleshoot Blue Screen of Death Errors in 2026?
Quick Summary
Troubleshooting blue screen errors starts with recording the stop code and its parameters before restarting, then checking whether the crash happens at startup, during use, or at random. Roll back any recently updated driver from Safe Mode, run SFC and DISM repairs, and test RAM and the drive before reinstalling Windows.
Back up important files first, since a failing drive can worsen with each restart.
Photograph the stop code and its parameters before the machine reboots.
If the same third-party driver appears in three or more dumps, roll it back first.
Run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, then chkdsk C: /f /r.
Avoid reinstalling Windows right away, because that can erase the clues needed to find the cause.
Still getting blue screens?
PhoneProbs tests hardware and software to find the real cause of your crashes.
Table of Contents
What a Blue Screen of Death Is and Why It Happens
Last Updated: November 17, 2026
A blue screen of death (BSOD) is the error screen Windows shows when it hits a problem it cannot safely recover from (Troubleshooting Windows unexpected restarts and stop code errors).
When Windows detects a critical system error, it stops all work to protect your files. The screen shows a sad face or QR code, a short message, and a stop code like IRQL_NOT_LESS_OR_EQUAL or MEMORY_MANAGEMENT. The system then restarts, or waits for you to do it.
Most blue screens come from a short list of causes:
Driver conflicts: A graphics, network or storage driver fails or clashes with Windows
Failing RAM or storage: Bad memory sticks and dying hard drives or SSDs cause crashes
Overheating: A hot CPU or GPU can trigger shutdowns and crashes under load
Corrupt system files: Damaged Windows files stop critical processes from running
Recent software or updates: New apps, patches or updates sometimes conflict with the system
A common mistake is reinstalling Windows right away. That can erase the clues you need to find the real cause. Start by identifying the pattern instead.
Before You Start: Protect Your Data and Note the Stop Code
Before you change anything, protect your files. A failing drive can get worse with every restart, and a bad repair attempt can make data loss permanent.

Follow these steps first:
Copy important files to an external drive or cloud storage
Write down the stop code exactly as it appears, such as CRITICAL_PROCESS_DIED
Note what you were doing just before the crash, including any recent installs or updates
Check whether the crash repeats on a schedule or during specific tasks
Watch out: running disk repair tools on a drive that is clicking or failing can lose data. Back up first.
Windows Blue Screen Stop Codes and What They Tell You
Stop codes are the best clue you have, but they are a category, not a diagnosis.
Step 1: Capture the stop code and its parameters.
The screen shows a stop code such as IRQL_NOT_LESS_OR_EQUAL plus up to four hexadecimal parameters in parentheses. Photograph the screen before the machine restarts. The parameters often name the faulting address or the driver file, and they are the detail most people lose by rebooting too quickly.
Common codes and the category they point to:
MEMORY_MANAGEMENT: Often bad RAM or a faulty driver writing outside its memory.
IRQL_NOT_LESS_OR_EQUAL: Usually a driver accessing memory at the wrong interrupt level; the fourth parameter frequently names the driver.
PAGE_FAULT_IN_NONPAGED_AREA: Can mean failing RAM, a damaged drive, or a bad driver.
KERNEL_DATA_INPAGE_ERROR: Often a failing storage drive, a bad cable, or a loose connection.
CRITICAL_PROCESS_DIED: Usually corrupted system files or a critical service that was terminated.
WHEA_UNCORRECTABLE_ERROR: A hardware error reported by the platform, treat it as a strong signal of CPU, memory, or power-supply trouble, not a software bug.
Treat each code as a starting direction, then confirm with a test.
Step 2: Make sure minidumps are being written.
Windows writes a small memory dump after most crashes to C:\Windows\Minidump.
Step 3: Read the dump instead of guessing.
Open the most recent .dmp file with a reader such as BlueScreenView, WhoCrashed, or WinDbg. Look for the module named in the crash stack.
A practical rule most technicians use: if the same third-party driver appears in three or more dumps, roll that driver back first.
Step 4: Correlate with recent changes.
Match the first crash timestamp against Windows Update history, driver installs, and new hardware.
Stop code | What it usually points to | Next step |
MEMORY_MANAGEMENT | Bad RAM or a driver writing outside its memory | Test RAM |
IRQL_NOT_LESS_OR_EQUAL | Driver accessing memory at the wrong interrupt level | Check the fourth parameter for the driver |
PAGE_FAULT_IN_NONPAGED_AREA | Failing RAM, a damaged drive, or a bad driver | Test RAM and drive |
KERNEL_DATA_INPAGE_ERROR | Failing storage drive, bad cable, or loose connection | Check cables and drive health |
CRITICAL_PROCESS_DIED | Corrupted system files or a terminated critical service | Run SFC and DISM |
WHEA_UNCORRECTABLE_ERROR | Hardware error from CPU, memory, or power supply | Treat as hardware trouble |
Start Here: Does Windows Boot, Crash at Startup, or Crash Randomly?
Your next step depends on how the crash behaves, not on which stop code looks scariest.
Branch 1: Windows boots normally and crashes later, while you are using it.
This is the safest branch. Stay in normal Windows and collect evidence before changing anything.
Open Event Viewer (press Windows key + X, choose Event Viewer) and look under Windows Logs > System for red Critical events with source BugCheck. The timestamp tells you which driver or component was active.
Note whether crashes cluster around a specific task, gaming, video calls, large file copies, sleep/wake. A pattern under load points to heat or power; a pattern at idle points to a driver or memory.
Check Reliability Monitor (search "Reliability" in the Start menu) for the exact day a new driver, app, or update landed before the first crash.
Only then move to the Safe Mode driver rollback and Command Prompt repair sections below.
Branch 2: Windows starts to load but crashes during startup, before the desktop appears.
Here the goal is to reach a repair environment, not to boot normally.
Restart and interrupt the boot three times in a row (hold the power button once the logo appears) to trigger Windows Recovery Environment (WinRE). On Windows 11 you can also hold Shift while choosing Restart from the sign-in screen.
In WinRE choose Troubleshoot > Advanced options. Run Startup Repair first; it is non-destructive.
If Startup Repair fails, open Command Prompt from the same menu and run the SFC and DISM commands from the section below against the offline image.
If the machine still will not boot, use System Restore to a point before the first crash, but only if you have already copied files off the drive or confirmed a recent backup exists.
Branch 3: Crashes at random times with no visible pattern, including from a cold boot.
Random crashes are the strongest signal of a hardware fault, so test hardware before touching software.
Run Windows Memory Diagnostic (search "Memory" in the Start menu, choose Restart now and check for problems). A single pass takes roughly 20-40 minutes; run at least two passes if the first is clean.
Check drive health with the manufacturer's tool or by running chkdsk C: /f /r from an elevated Command Prompt. Reallocated sectors or a SMART warning means back up immediately and plan a replacement.
Monitor temperatures under load with a tool such as HWiNFO or the vendor's utility. Sustained CPU or GPU temperatures near the thermal limit before a crash point to cooling, not drivers.
Remove any recently added RAM stick, GPU, or USB device and retest. Isolate one component at a time so you know which change stopped the crashes.
Stop conditions, when to stop troubleshooting and escalate.
Once you know which branch you are in, pick the matching fix from the sections below. You can see our repair options for laptops and PCs at book a drain inspection for general diagnostics, but for laptop-specific crash recovery, review our 7 steps to recover corrupted system files.
Using Windows Safe Mode to Roll Back a Bad Driver
Safe Mode loads Windows with only basic drivers. That makes it the best place to remove a driver causing a blue screen.
To start Safe Mode on Windows 10 or 11:
Open Settings, then go to System, then Recovery
Click Restart now under Advanced startup
Choose Troubleshoot, then Advanced options, then Startup Settings
Press 4 or F4 to enable Safe Mode
Once in Safe Mode, open Device Manager, find the device with the recent driver update, right-click it, and choose Properties, then Roll Back Driver if the option is available. If it is greyed out, uninstall the driver and restart.
After the rollback, pause automatic driver updates for that device until you find a stable version.
Fix Blue Screen Errors Using Command Prompt
Command Prompt tools can repair damaged system files and check the drive. If you are unsure what is causing random crashes, you can compare tested diagnostic software options for Windows to check hardware and system health.
Run these commands in order:
sfc /scannow checks and repairs protected Windows files
DISM /Online /Cleanup-Image /RestoreHealth repairs the Windows image that SFC relies on
chkdsk C: /f /r checks the system drive for errors (this may require a restart)
Each step can take 10 to 30 minutes. Let each finish before starting the next.
Run sfc /scannow again after DISM finishes so the repaired image is used (Use the System File Checker tool to repair missing or corrupted system files). If chkdsk reports bad sectors on a drive, that is a sign to back up and consider replacement.
Blue Screen After Driver Update? Next Steps and When to Get Help
If the blue screens started right after a driver update, roll that driver back first, then confirm the crashes stop. If they continue, the cause may be hardware or a deeper system problem.
Consider professional help when:
Stop codes point to RAM or the drive, and you cannot test them safely
Windows will not boot even after startup repair
You hear clicking from the drive or see overheating
Crashes continue after the steps above
Bring your stop codes, the minidump files and a note of when the crashes started. That evidence speeds up diagnosis and reduces guesswork. PhoneProbs covers laptops and consoles, and you can stop by for a professional quote. You can book your laptop repair directly once the DIY steps have been exhausted.
Book Your Repair at PhoneProbs
If you have tried these steps and the blue screens continue, PhoneProbs can diagnose the problem. We repair phones, consoles, computers and laptops, and we handle water damage and unwanted software issues as well. Stop by for a professional quote before you spend more time guessing.
Frequently Asked Questions
How do I troubleshoot a Blue Screen of Death in Windows 11?
Start by noting the stop code on the blue screen, then restart and see whether Windows boots normally. If it crashes during startup, open Windows Recovery Environment and choose Startup Repair or Safe Mode. Once you are in, uninstall any driver or update installed just before the crashes began, run a memory test, and check the drive with a disk scan. Keep your files backed up throughout, since repair steps occasionally fail. If the crashes continue after these steps, a professional diagnostic can identify failing hardware faster.
Can a faulty driver cause a Blue Screen of Death?
Yes. Driver conflicts are one of the most common causes of blue screens, especially graphics, network, and storage drivers. If the crashes started right after a driver update, open Device Manager, right-click the device, and choose Properties, then Roll Back Driver. If that option is grayed out, uninstall the driver in Safe Mode and let Windows reinstall a stable version. Checking the minidump file or stop code often names the driver responsible.
Can I fix a blue screen error using Command Prompt?
You can. Open Command Prompt as administrator from the Windows Recovery Environment and run sfc /scannow to repair corrupted system files, then DISM /Online /Cleanup-Image /RestoreHealth to repair the Windows image. Run chkdsk C: /f to check the drive for errors. These commands fix many crashes caused by damaged files, but they will not resolve failing RAM or a dying drive, so test those separately if the blue screens return.
When should I reset or reinstall Windows after repeated blue screens?
Consider a reset only after you have ruled out hardware failure and driver problems. If the blue screens continue after Safe Mode troubleshooting, Command Prompt repairs, and driver rollbacks, a reset can clear software corruption. Back up your files first, since a reset may remove apps. If you suspect a failing drive or memory, a reset will not help, and a repair shop can run hardware diagnostics to confirm the cause.






Comments