Home › Windows Fixes

Windows 11 Blue Screen of Death? How to Fix It Step by Step

Updated November 2, 2026 · 9 min read

A blue screen of death (BSOD) on Windows 11 looks alarming, but it's just Windows hitting an error it can't recover from and stopping to protect itself. The vast majority of blue screens are caused by bad drivers, corrupt system files, or failing RAM — all fixable. Work through these eight steps in order. Most blue screens are resolved by step 4, and by step 8 you'll know exactly whether it's software (fixable tonight) or hardware (needs a part).

Step 1: Write down the stop code

Before the blue screen disappears, look at the bottom of the screen. There's a stop code in ALL CAPS with underscores — something like MEMORY_MANAGEMENT, DRIVER_IRQL_NOT_LESS_OR_EQUAL, or CRITICAL_PROCESS_DIED. Take a photo of the screen with your phone. This code is the single most useful clue you have, and it vanishes when the PC restarts.

Common codes and what they usually mean:

• MEMORY_MANAGEMENT / PAGE_FAULT_IN_NONPAGED_AREA — bad RAM or a bad RAM driver. Go to step 5.
• DRIVER_IRQL_NOT_LESS_OR_EQUAL / SYSTEM_THREAD_EXCEPTION_NOT_HANDLED — a faulty driver. Go to step 3 and step 7.
• CRITICAL_PROCESS_DIED / UNEXPECTED_STORE_EXCEPTION — corrupt system files or a failing drive. Go to step 4 and step 6.
• A different code every time — the classic signature of failing RAM. Go to step 5 first.

Even if the code means nothing to you now, work the steps below anyway — they're ordered to catch the most common causes first.

Step 2: Boot into Safe Mode

Safe Mode starts Windows with only the essential drivers. If the blue screens stop in Safe Mode, the problem is a third-party driver or startup program — not Windows itself and not (usually) hardware.

1. If Windows still boots: go to Settings → System → Recovery → Advanced startup → Restart now.
2. If Windows won't boot: turn the PC on, then hold the power button to force it off as soon as you see the Windows logo. Repeat three times. On the fourth boot, Windows enters Automatic Repair → Advanced options → Troubleshoot → Advanced options → Startup Settings → Restart.
3. Press 4 for Safe Mode (or 5 for Safe Mode with Networking, so you can download drivers).

Do steps 3–7 from Safe Mode if normal mode keeps crashing — it's stable ground to work from.

Step 3: Undo the last change

Blue screens that started right after something changed have an obvious suspect. Undo it:

1. After a Windows update: Settings → Windows Update → Update history → Uninstall updates. Remove the most recent update and restart.
2. After a driver update: open Device Manager, right-click the device, → Properties → Driver → Roll Back Driver.
3. After installing software: Settings → Apps → Installed apps, sort by install date, and uninstall the newest entries — especially antivirus tools, VPN clients, and "system optimizer" utilities, which install deep drivers.
4. After adding hardware: unplug the new device (USB hardware, new RAM stick, new drive) and see if the crashes stop.

If you can't pinpoint a recent change, keep going — the next steps catch the silent causes.

Step 4: Repair system files with SFC and DISM

Corrupt Windows system files are one of the most common BSOD causes, and Windows ships with two built-in tools that fix them. Run both, in this order.

1. Open Terminal as administrator: right-click Start → Terminal (Admin).
2. First, repair the Windows image itself:

   DISM /Online /Cleanup-Image /RestoreHealth

   This downloads clean copies of damaged components. It takes 5–20 minutes — let it finish.
3. Then scan and repair protected system files:

   sfc /scannow

   This takes another 10–15 minutes. If it reports "found corrupt files and successfully repaired them," restart and test.
4. If SFC says it couldn't fix everything, run the DISM command once more, then sfc /scannow again — the second pass often succeeds.

This step alone resolves a huge share of blue screens, especially CRITICAL_PROCESS_DIED and errors that appeared out of nowhere.

Step 5: Test your RAM

Bad RAM causes the most confusing blue screens — a different stop code almost every crash, because whichever data happened to be in the bad memory cells corrupts randomly. Windows has a built-in tester.

1. Press Win + R, type mdsched.exe, and press Enter.
2. Choose Restart now and check for problems. The PC reboots into the Windows Memory Diagnostic.
3. Let the standard test finish (10–20 minutes). Results appear after Windows boots back up — check them in Event Viewer, or just watch: if the tool reports hardware errors, you have bad RAM.

If errors are found: power off, open the case, and reseat the RAM sticks (remove and firmly reinsert them — loose sticks cause errors too). Test again. Still errors? Test one stick at a time to find the bad one, and replace it. Our RAM upgrade walkthrough covers the replacement process: see fix #9.

Step 6: Check the disk for errors

A drive with bad sectors can corrupt the exact system files Windows needs at boot, producing UNEXPECTED_STORE_EXCEPTION and similar codes.

1. Open Terminal as administrator.
2. Run:

   chkdsk C: /f /r

3. Type Y when asked to schedule the check, then restart. The scan runs before Windows loads and can take 30 minutes to several hours on large drives — don't interrupt it.
4. If chkdsk finds and repairs bad sectors but crashes continue, the drive is deteriorating. Back up immediately and plan a replacement — an SSD upgrade both fixes the crashes and speeds everything up (see fix #10).

Step 7: Update drivers from the manufacturer

Windows Update's drivers are often months out of date, and graphics, chipset, and storage drivers are the ones most likely to blue-screen when buggy.

1. Go to your laptop or motherboard maker's support site (Dell, HP, Lenovo, ASUS, MSI) and download the latest chipset, storage/SATA, and graphics drivers for your exact model.
2. Install the chipset driver first, then storage, then graphics. Restart between them if asked.
3. For a stubborn graphics-related crash (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED naming nvlddmkm.sys or amdkmdag.sys), do a clean GPU driver install: download Display Driver Uninstaller (DDU), run it in Safe Mode to wipe the old driver completely, then install the fresh driver from NVIDIA/AMD/Intel.
4. In Device Manager, check for any device with a yellow warning triangle — that's Windows telling you exactly which driver is unhappy.

Step 8: Use System Restore (the easy rollback)

If the crashes started recently and nothing above nailed it, roll the whole system back to before the problem began. System Restore doesn't touch your personal files — only system files, drivers, and settings.

1. Press Win + R, type rstrui.exe, and press Enter.
2. Click Next and pick a restore point dated before the blue screens started. Check "Show more restore points" if you need an older one.
3. Click Finish and let it run — the PC restarts a couple of times.

If there are no restore points (System Protection is off by default on some installs — worth turning on afterward), the nuclear option is a clean Windows install, which rules out software causes entirely.

When it's failing hardware

If you've worked all eight steps and the crashes continue, the pattern of the crashes tells you which part is dying:

• Random different stop codes every crash → RAM. Replace the sticks (step 5's one-at-a-time test identifies the bad one).
• The same stop code every time → a specific driver or device. The code plus the driver name on the blue screen (often shown in small text) points at the culprit.
• Crashes only under heavy load, with heat and loud fans → cooling failure. Clean the vents; a CPU or GPU protecting itself from heat looks exactly like instability.
• Crashes when the drive is working hard, plus slow file access → the drive is dying. Back up now, replace with an SSD.

The moment hardware failure is on the table, back up your data first — troubleshooting second. A dying drive doesn't wait for you to finish step 8.

Frequently asked questions

Will a blue screen damage my computer?

No. The blue screen is the protection — Windows stops everything before the error can corrupt data or damage hardware. The casualty is unsaved work, not the machine. Repeated blue screens are a symptom worth fixing, but each individual crash is harmless to the hardware.

Why does my PC only blue screen when gaming?

Gaming stresses the GPU driver, thermals, and power delivery all at once. Update the graphics driver first (step 7's clean install), then check temperatures — a GPU hitting 90°C+ will crash. On desktops, an aging or underpowered power supply is the next suspect; on laptops, blocked vents.

Should I just reinstall Windows to fix blue screens?

It's the definitive test — a clean install rules out every software cause at once — but try steps 1–8 first, because a reinstall won't fix bad RAM or a dying drive, and it costs you hours of setup. Reinstall when the steps point at software but nothing specific, or as the final confirmation before buying replacement hardware.

How do I stop Windows from restarting so fast I can't read the blue screen?

Disable automatic restart: press Win + R, type sysdm.cpl, go to Advanced → Startup and Recovery → Settings, and uncheck Automatically restart. The blue screen will stay up until you power off, so you can photograph the stop code. (Your phone photo from step 1 works just as well.)