RunTheTests
/

Windows Stop Code / BSOD Lookup

Look up a Windows blue-screen stop code and get the likely cause and next step.

What you paste

Parsed in your browser — never uploaded

How this reads your output

Enter the stop code shown on the blue screen — either the hex value like 0x0000000A or the name like IRQL_NOT_LESS_OR_EQUAL — and the tool returns what it means, the broad category most likely at fault, and the first thing worth checking. You can paste the whole blue-screen line; the code is picked out of it.

What the results mean

Most likely cause
The broad category — driver, memory, storage or hardware — that this code most often points to. It is a lead, not a diagnosis.
Driver causes
The most common and most fixable. Updating or rolling back a driver resolves a large share of blue screens.
Hardware / memory causes
More serious. Codes like WHEA_UNCORRECTABLE_ERROR point at failing components — worth a memory test and a temperature check before spending money.

Common problems and fixes

The same code keeps pointing at "driver" but I do not know which
The minidump file in C:\Windows\Minidump names the driver involved. A free crash-dump reader will open it, or note any .sys filename shown on the blue screen itself.
It says hardware but everything seems fine
Hardware faults are often intermittent and heat-related. Run a memory test overnight and check temperatures under load before concluding the hardware is healthy.

Frequently asked questions

Does a stop code tell me exactly what is broken?

No, and any tool claiming it does is overreaching. A stop code tells you what kind of failure Windows detected — a driver accessing bad memory, an unrecoverable hardware error — which narrows the search. Pinning it to a specific part still takes the minidump, a memory test, or swapping components.

What should I do first for most blue screens?

Note what changed just before they started — a new driver, a Windows update, new hardware — because that is the fastest lead. Then update your drivers, run "sfc /scannow", and run a memory test. Those three steps resolve the majority of cases.

Put this on your own site

Free to embed, no attribution required beyond the source link the frame carries itself. It runs entirely in your visitor's browser, sets no cookies and loads no third-party script.

Embed code
<iframe src="https://runthetests.com/embed/bsod-stop-code-lookup/" width="100%" height="720" style="border:1px solid #e5e5e5;border-radius:8px" title="Windows Stop Code / BSOD Lookup" loading="lazy"></iframe>

Preview it at https://runthetests.com/embed/bsod-stop-code-lookup/. Embedded pages are marked noindex, so yours stays the canonical copy — not this one.

More in Interpreter