What Is a Blue Screen of Death?

A Blue Screen of Death (BSOD) — formally called a Stop Error — occurs when Windows encounters a critical error that it cannot recover from safely. Rather than risk data corruption, the OS halts immediately, displays the error screen, and restarts. On modern Windows 10/11, BSODs show a sad face emoji and a stop code in plain text, making them easier to diagnose than older cryptic hex codes.

A single BSOD isn't necessarily alarming — hardware glitches, driver conflicts, and even Windows updates can trigger one-time crashes. Frequent or recurring BSODs always indicate an underlying problem that needs to be resolved.

How to Read a Stop Code

When a BSOD occurs, write down or photograph:

  • The stop code (e.g., MEMORY_MANAGEMENT, IRQL_NOT_LESS_OR_EQUAL)
  • The faulting module if shown (e.g., ntfs.sys, nvlddmkm.sys)
  • The error value in parentheses if visible (e.g., 0x0000001A)

After restart, you can find the full crash dump in Event Viewer: Win+R → eventvwr.msc → Windows Logs → System. Look for Critical events at the time of the crash.

Most Common Stop Codes and What They Mean

Stop CodeLikely CauseFirst Diagnostic Step
MEMORY_MANAGEMENT Faulty RAM, RAM incompatibility, or memory controller issue Run MemTest86 overnight
IRQL_NOT_LESS_OR_EQUAL Driver accessing memory at the wrong interrupt level — usually a bad driver Check recently installed drivers; update chipset and GPU drivers
PAGE_FAULT_IN_NONPAGED_AREA Corrupt system files, bad RAM, or failing drive Run sfc /scannow and check drive health with CrystalDiskInfo
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Driver crash — the faulting .sys file is usually named on screen Identify the .sys file and update or remove that driver
CRITICAL_PROCESS_DIED Core Windows process crashed — corrupt system files or drive failure Run DISM and SFC; check drive health
KERNEL_SECURITY_CHECK_FAILURE Memory corruption — RAM or an overclocked CPU/GPU Reset overclocks to stock; run MemTest86
DPC_WATCHDOG_VIOLATION SSD firmware issue, driver conflict, or outdated storage controller driver Update storage controller and SSD firmware
WHEA_UNCORRECTABLE_ERROR Hardware failure: CPU, RAM, or motherboard issue. Can also be a bad overclock. Reset BIOS to defaults; run hardware stress tests

Universal Fixes to Try

1. Run System File Checker

Open Command Prompt as Administrator and run:

  • sfc /scannow — scans and repairs corrupted Windows system files
  • DISM /Online /Cleanup-Image /RestoreHealth — repairs the Windows component store

Restart after both commands complete.

2. Update Drivers — Especially GPU and Chipset

Download and install the latest GPU driver (NVIDIA/AMD/Intel), chipset driver from your motherboard manufacturer, and NVMe/storage controller driver if applicable. Outdated drivers are the most common cause of recurring BSODs on otherwise healthy hardware.

3. Check Drive Health

Download CrystalDiskInfo and check the S.M.A.R.T. status of all drives. Look for "Caution" or "Bad" status — particularly Reallocated Sectors, Pending Sectors, or Uncorrectable Sector counts above zero. Any drive showing these values needs to be backed up and replaced.

4. Test RAM with MemTest86

Download MemTest86 from memtest86.com, write it to a USB drive, and boot from it. Let it run at least two full passes overnight. Any errors indicate faulty RAM that needs to be replaced.

5. Roll Back a Recent Update

If BSODs started immediately after a Windows Update, go to Settings → Update & Security → View Update History → Uninstall Updates. Remove the most recent update and test. If stable, block that update temporarily through Show or Hide Updates tool.

Backup your data now. If you're getting frequent BSODs, back up your important files before doing anything else. A failing drive can become completely unreadable at any moment, and RAM failure can corrupt file system structures.

When to Bring It In

Bring the machine to us if:

  • MemTest86 finds errors — RAM replacement needs proper identification of which module(s) failed
  • CrystalDiskInfo shows drive errors — the drive needs to be cloned before it fails completely
  • BSODs continue after all software fixes — possible motherboard or CPU issue
  • The machine won't boot long enough to run diagnostics

We read the crash dumps. Our technicians analyze Windows minidump files to identify the exact driver or hardware fault causing your BSODs — then fix it at the source. Free diagnostics, no-fix no-fee.