WindowsTroubleshooting

Blue Screen of Death? How to Fix BSOD on Windows (2026)

TG By The TechFix Guide Editorial Team  ·  Updated  ·  How we check our guides
A person at a home desk looking at a desktop monitor whose screen is entirely blue, soft morning light through the window, coffee mug and notebook on the wooden desk

There are few computer errors as alarming as the Blue Screen of Death — the screen suddenly turns blue, a sad face appears, and Windows restarts without asking permission. The good news: a blue screen (also called a BSOD) is Windows protecting itself from a serious crash, and in most cases the cause is something you can fix in under an hour. This guide walks you through the checks in order, starting with the most likely ones, in plain English and without reinstalling anything first.

What the Blue Screen Actually Tells You

A blue screen appears when Windows hits an error so serious that it cannot keep running safely — usually a bad driver, failing memory, or corrupted system files. Instead of risking your data, Windows stops everything, saves a crash report, and restarts. The most useful clue is the stop code: the short phrase like CRITICAL_PROCESS_DIED shown near the bottom of the blue screen. That stop code is your diagnosis — it tells you which part of the system failed, and it is the first thing to search for when you need a specific fix.

Step 1: Write Down the Stop Code

If the blue screen flashes by too fast to read, let the PC restart and open the search box, type Reliability Monitor, and launch it. This timeline view shows every crash with its stop code and the exact time it happened — which also tells you whether the crashes began right after a particular update or program install. If the machine blue-screens in a loop and never reaches the desktop, jump to the Safe Mode section below; every check in this guide still works from there.

The First Five Things to Check

1. Undo whatever changed recently

Most blue screens begin right after a change: a new graphics driver, a Windows update, a fresh app, or a piece of hardware you plugged in. Roll it back. In Settings, go to Windows Update → Update history → Uninstall updates to remove a recent update. If a new program coincides with the crashes, uninstall it from Settings → Apps → Installed apps. Did you add RAM, a new drive, or a USB device recently? Power off, unplug, and reseat it — a half-seated memory stick is a classic blue screen cause.

2. Boot into Safe Mode

Safe Mode starts Windows with only the basics, so a bad driver or startup program cannot load. To get there when the PC will not start normally: force a shutdown by holding the power button three times in a row during boot — Windows then opens Automatic Repair → Advanced options → Troubleshoot → Startup Settings → Restart. After the restart, press 4 for Safe Mode. If the PC is stable in Safe Mode but crashes normally, that points squarely at a driver or startup program, which makes the next steps much easier.

3. Fix the drivers

Faulty or outdated drivers are the number one cause of blue screens. Right-click the Start button and open Device Manager. Look for any device with a yellow warning triangle. For graphics hardware, download the latest driver directly from NVIDIA, AMD, or Intel — the versions delivered through Windows Update can lag behind. If the crashes started after a driver update, right-click the device, choose Properties → Driver → Roll Back Driver. On laptops, repeat offenders are often the chipset and storage drivers on the manufacturer's support page.

4. Repair system files and check the disk

Corrupted Windows files can crash the system at random. Right-click Start, choose Terminal (Admin), and run these commands one at a time:

  • sfc /scannow — scans and repairs protected system files (takes 10–20 minutes).
  • chkdsk C: /f — checks the system drive for file system errors; it schedules a scan for the next restart, so type Y and reboot.

If SFC reports errors it could not fix, run DISM /Online /Cleanup-Image /RestoreHealth, then run sfc /scannow once more. These three commands quietly resolve a surprising share of recurring blue screens.

5. Test your RAM

Bad memory causes crashes that seem completely random — sometimes a game, sometimes a boot. Search for Windows Memory Diagnostic, run it, and choose Restart now and check for problems. The test takes about 15 minutes and Windows reports the result after login. For a deeper test, the free tool MemTest86 run from a USB stick is the standard choice. If errors appear, reseat the memory sticks one at a time to find the faulty one — or replace it.

The Most Common Stop Codes (and What They Point To)

  • CRITICAL_PROCESS_DIED — a core Windows component crashed. Run the SFC and DISM repairs from check 4.
  • MEMORY_MANAGEMENT — almost always RAM. Go straight to the memory test in check 5.
  • DRIVER_IRQL_NOT_LESS_OR_EQUAL — a driver accessed memory incorrectly. Update or roll back drivers, especially network and graphics.
  • PAGE_FAULT_IN_NONPAGED_AREA — memory or disk trouble. Run the RAM test and chkdsk.
  • DPC_WATCHDOG_VIOLATION — usually an SSD firmware or storage driver issue. Update storage drivers and check the drive maker's site for firmware updates.
  • UNEXPECTED_STORE_EXCEPTION — often tied to the disk or Fast Startup. Disable Fast Startup in Control Panel → Power Options and run chkdsk.

When It Crashes Only Sometimes

Intermittent blue screens are the hardest to pin down, and overheating is a common hidden cause. Install a free temperature-monitoring tool such as HWiNFO and watch CPU temperatures under load — sustained readings in the high 90s °C mean the cooling needs attention: clean the fans, clear the vents, and consider repasting an older laptop. Also study the pattern: crashing only while gaming suggests a graphics driver or heat; crashing on wake from sleep suggests a driver; crashing under heavy multitasking suggests RAM. Patterns narrow the culprit faster than any scan.

When a Reset Is Actually Worth It

If you have worked through drivers, system files, RAM, and disk checks and the blue screens continue, a clean reset resolves lingering software corruption in one move. Use Settings → System → Recovery → Reset this PC and choose Keep my files. Back up anything important first regardless — frequent crashes are themselves a data risk. And if the blue screen appears even during a fresh Windows install, or the memory test keeps failing after replacing sticks, the problem is hardware: suspect the drive, the power supply, or the motherboard, and bring your Reliability Monitor notes to a repair shop.

One blue screen after a driver update is an accident. The same stop code three times in a week is a diagnosis waiting to be made — write it down and let Reliability Monitor tell you when it started.

A blue screen looks dramatic, but it is really Windows handing you a clue. Note the stop code, undo recent changes, and run the five checks above in order — most machines are stable again before the coffee gets cold.