Windows Blue Screen Keeps Happening: Reading the Stop Code

What a blue screen actually is

A blue screen is Windows stopping deliberately because something at kernel level did something it cannot recover from. Frequently that something is a driver. Frequently it is hardware misbehaving in a way a driver noticed. The screen shows a stop code and sometimes a file name — both are clues worth writing down.

• A named file such as nvlddmkm.sys or a storage driver points at that driver and its hardware.
• MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA are associated with memory, but can equally come from a driver writing where it should not.
• CRITICAL_PROCESS_DIED and UNEXPECTED_STORE_EXCEPTION often accompany storage or file system problems.
• WHEA_UNCORRECTABLE_ERROR is a hardware-reported error — CPU, memory, power or an unstable overclock.
• INACCESSIBLE_BOOT_DEVICE at startup normally means storage, its driver, or a firmware setting that changed.

Possible causes

• Drivers — graphics, storage, network and vendor utilities, especially just after an update or a Windows feature upgrade.
• Memory — a failing stick, a mismatched pair, or an XMP/EXPO profile the board cannot hold.
• Storage — a failing SSD or hard drive, or a loose or damaged cable.
• Windows corruption — damaged system files, an interrupted update, or two security products conflicting.
• Overheating — a CPU or GPU running at its limit, causing errors under load.
• Power instability — a failing power supply, a bad outlet or a laptop battery that cannot hold load.
• Firmware and motherboard — an old BIOS with known stability issues, or a genuine board fault.
• Overclocks and undervolts, including automatic boost behaviour on an aging processor.

Protect your data before you troubleshoot

Safe, ordered troubleshooting

1. 1

   Record the codes

   Photograph the blue screen, or check Reliability Monitor for the history. A pattern of different codes suggests hardware; the same code every time suggests a specific driver or component.

2. 2

   Note what changed

   A driver update, a Windows update, a new device, a new memory kit, a room that got hotter, or a machine that was moved. Recent changes explain most sudden instability.

3. 3

   Update or roll back the named driver

   If a file name appears, address that driver specifically — update from the hardware vendor, or roll back if the trouble started right after an update.

4. 4

   Test memory

   Run an extended memory test overnight. Any error is meaningful. No error does not fully clear memory, but it moves it down the list.

5. 5

   Check drive health

   Read the SMART data. Reallocated sectors, pending sectors, or a wear indicator near its limit are reasons to plan a replacement and copy data off now.

6. 6

   Return to stock settings

   Disable overclocks and memory profiles. If the blue screens stop, the tuning was the cause.

7. 7

   Watch temperatures

   Log CPU and GPU temperatures during normal use and under load. Crashes clustered at high temperatures point at cooling.

8. 8

   Run the Windows file checks

   From an administrator command prompt, run sfc /scannow and then DISM /Online /Cleanup-Image /RestoreHealth. These repair system files without touching your documents.

What each result may indicate

• Same stop code and same driver file each time — driver or the hardware that driver controls.
• Different codes at random — more consistent with memory, storage, power or heat than with one driver.
• Crashes only under load — thermals or power delivery.
• Crashes during startup or shutdown only — often storage or a service loading early.
• Memory errors found — deal with memory before drawing any other conclusions; unstable memory can also corrupt files and produce misleading symptoms.
• Clean tests everywhere and it still crashes — intermittent hardware, firmware, or a fault that only appears in real use. This is where bench substitution earns its keep.

When to stop DIY troubleshooting

Stop if Windows will not stay up long enough to work in, if you are being prompted to reinstall, or if the drive is making noise or showing SMART warnings. Stop as well if you find yourself about to buy memory, a drive or a power supply on the basis of a stop code alone.

When professional diagnosis makes sense

We start by securing your data, then work through memory, storage, thermals and power with known-good parts to substitute. Repeat blue screens are one of the most common things we see in the shop, and a large share of them turn out to be a component that a stop code never mentioned.