Home / Guides / Blue Screen of Death (BSOD)

How to Read and Respond to Any Blue Screen

Intermediate Blue Screen of Death (BSOD) Applies to: Windows 7, Windows 10, Windows 11

A general framework for any stop code you don't recognize.

Before you start: save any open work and note down what you were doing when the problem started — that context helps if you need to search further or ask for help.
📝 From a real case study: this page was updated after Meera Iyer investigated How to Actually Read a Blue Screen Stop Code — a real reader-reported problem, not a hypothetical one.
  1. Write down the stop code exactly as shown (e.g., "IRQL_NOT_LESS_OR_EQUAL") — it's the single most useful piece of information for diagnosing the crash.
  2. Note what you were doing right before it happened — gaming, waking from sleep, plugging in a device — since that often points straight to the cause.
  3. Check Reliability Monitor (search "reliability" in the Start menu) for a timeline of crashes and what else failed around the same time.
  4. Look at the actual minidump file for more detail than the stop code alone gives you: they're saved to C:\Windows\Minidump, and a free tool like WhoCrashed can read one and usually name the specific driver file responsible, in plain terms.
  5. If it started after installing a new driver or piece of hardware, that's the first thing to remove or roll back.
  6. If crashes are frequent and random with no clear trigger, run Windows Memory Diagnostic (search "memory diagnostic") to rule out failing RAM.
  7. Feel the laptop or case for unusual heat, or check temperatures with a monitoring tool — a crash under load that doesn't happen at idle can point to overheating rather than software at all.
Mentioned above: How to Perform a Clean Boot to Isolate a Stubborn Problem
Still not fixed? Send us the details and we'll help you dig further, or browse related guides in Blue Screen of Death (BSOD).

Frequently Asked Questions

Will a blue screen delete my files?
No, a blue screen crash by itself doesn't delete files. The real risk is losing unsaved work in whatever you were actively working on at the moment it happened, since the crash forces an immediate restart.
Is it safe to keep using my PC if I only get a blue screen occasionally?
An occasional, isolated blue screen (once every few weeks with no clear pattern) usually isn't worth deep investigation. Frequent or worsening crashes are what warrant working through the steps above — they're more likely to point to a real, ongoing hardware or driver problem.
Do I need to pay for anything to diagnose a blue screen?
No. Everything in this guide — Reliability Monitor, Windows Memory Diagnostic, and WhoCrashed — is either built into Windows or free. You shouldn't need to buy software to diagnose a crash.

Related guides

MEMORY_MANAGEMENT Blue Screen

Usually points to RAM, a driver conflict, or disk corruption.

Intermediate

IRQL_NOT_LESS_OR_EQUAL Blue Screen

Almost always a driver issue — most often network, audio, or graphics.

Intermediate

CRITICAL_PROCESS_DIED Blue Screen

A core Windows process crashed — often tied to a recent update or corrupted system file.

Intermediate