A blue screen is Windows detecting something it cannot recover from and stopping deliberately to avoid damage. It feels catastrophic and usually is not. More importantly, it tells you what went wrong, which puts you far ahead of a machine that simply reboots with no message.
The short answer
Write down the stop code, the text in capitals such as MEMORY_MANAGEMENT or DRIVER_IRQL_NOT_LESS_OR_EQUAL, and the file name if one is shown. That code names the subsystem that failed. Then check whether the crashes are random or tied to one activity, because that distinction separates hardware from software faster than anything else.
Getting the information
If the screen disappears too quickly, turn off automatic restart on system failure in the advanced system settings under startup and recovery. Then the blue screen stays until you acknowledge it.
Windows also keeps a record. Reliability Monitor, reached by searching for it in the start menu, shows a timeline of crashes with the stop codes and what was installed or updated around them. It is far more readable than Event Viewer and it is the first place to look.
What the common codes mean
- MEMORY_MANAGEMENT. Memory, or something writing to memory it should not. Run a memory test.
- IRQL_NOT_LESS_OR_EQUAL and DRIVER_IRQL_NOT_LESS_OR_EQUAL. A driver accessed memory incorrectly. If a file name is shown, it names the driver.
- PAGE_FAULT_IN_NONPAGED_AREA. Memory or storage. Often a failing drive.
- SYSTEM_SERVICE_EXCEPTION. Usually a driver, frequently graphics.
- KERNEL_SECURITY_CHECK_FAILURE. Corrupted system files or a driver conflict.
- CRITICAL_PROCESS_DIED. A core Windows process failed. Often storage or corruption.
- VIDEO_TDR_FAILURE. The graphics driver stopped responding. Reinstall it cleanly.
- INACCESSIBLE_BOOT_DEVICE. Windows cannot reach the drive. Storage driver or a failing drive.
- WHEA_UNCORRECTABLE_ERROR. The processor reported a hardware error. Heat, power, or an unstable overclock.
A file name ending in .sys on the blue screen is the single most useful clue you will get, because searching that name identifies the driver and usually the device it belongs to.
Record the stop code and any file name
Photograph the screen. Then open Reliability Monitor to see the history, because a pattern across several crashes is far more informative than one.
Note what you were doing
Random crashes point at hardware. Crashes tied to one game, one application, or plugging in one device point at software or that device.
Undo whatever changed recently
New hardware, a new driver, a Windows update, new software. Reliability Monitor shows what was installed around the first crash, which is often the answer on its own.
Reinstall the graphics driver cleanly
Graphics drivers cause a disproportionate share of blue screens. Use the manufacturer’s removal tool to strip the old one completely, then install the current version fresh rather than over the top.
Run a memory test
Use the built-in Windows Memory Diagnostic, or better a dedicated bootable tester for several full passes. If you have more than one module, test them individually to identify which is bad. Memory faults produce a wide variety of stop codes and are cheap to rule out.
Check the drive health
Use a monitoring tool to read the drive’s health data. Reallocated sectors or a warning status means the drive is failing, and that produces storage-related stop codes. Back up immediately if you find this.
Run the system file checker
From an administrator command prompt, run the system file checker and then the deployment image servicing tool. These repair corrupted Windows files, which cause several of the codes above.
Check temperatures and remove any overclock
Monitor processor and graphics temperatures under load, and set any tuning back to stock, including memory speed profiles. An overclock that was stable for a year can become unstable as components age.
Boot into safe mode and use the machine for a while. Safe mode loads a minimal set of drivers, so a machine that is stable there almost certainly has a driver problem rather than failing hardware. That one test splits the diagnosis in half.
Hardware or software?
- Different stop codes each time. Leans hardware, usually memory or power.
- The same stop code every time. Leans software, usually one driver.
- Only in one application. That application or its driver.
- Stable in safe mode. Software.
- Crashes in safe mode too. Hardware.
- Started immediately after a hardware change. The new part, or a connector disturbed while fitting it.
- Increasingly frequent over weeks. A component degrading, often memory, storage or the power supply.
Back up now, before troubleshooting. Several of the common causes, particularly failing storage, can go from occasional blue screens to a machine that will not boot with no warning. The window to copy your files closes without notice.
When to reinstall Windows
A clean reinstall is a legitimate step once you have ruled out hardware, and it is the fastest route when the machine has accumulated years of drivers and software. It is not a first move, though: reinstalling Windows on a machine with a failing memory module or a dying drive wastes an afternoon and fixes nothing, and you will get the same blue screens on the fresh install.
Test the memory and check the drive health first. Those two take an hour between them and they determine whether a reinstall is worth doing at all.
What is a stop code?
The text in capitals on the blue screen naming what failed. It points at the subsystem: memory, a driver, storage or the processor. It is the most useful piece of information you will get.
What if the blue screen disappears too fast?
Turn off automatic restart on system failure in the advanced startup and recovery settings, or read the history in Reliability Monitor, which records every crash with its code.
Do different stop codes mean different problems?
Usually. Consistently the same code points at one driver; varying codes across crashes leans toward hardware, most often memory or power delivery.
Can a blue screen damage my computer?
No. It is Windows stopping deliberately to prevent damage. The underlying cause may be damaging, which is why finding it matters, but the blue screen itself is protective.
Should I reinstall Windows to fix blue screens?
Only after testing memory and drive health. Reinstalling on failing hardware wastes an afternoon and produces the same crashes on the fresh install.
The bottom line
Write down the stop code and any .sys file name, because that names the culprit and turns guesswork into a search. Check Reliability Monitor for the pattern, test in safe mode to split hardware from software, and run a memory test and a drive health check before considering a reinstall. Back up first, because failing storage gives no warning before it stops entirely.
