Blue Screen Analyzer

What is a BSOD?

The infamous Blue Screen of Death (formally called a Stop Error) is what Windows shows when it hits a problem so serious it has to shut down rather than risk data corruption. The sad-face screen usually shows a STOP code like IRQL_NOT_LESS_OR_EQUAL or a hex number like 0x0000007E. Those names are meaningful to kernel developers but mean nothing to most people.

Blue Screen Analyzer reads the records Windows keeps of past BSODs and tells you, in plain language, what each one means and what commonly causes it.

Where the data comes from

Windows records BSODs in two places:

• The Event Log — a short record of the STOP code and timestamp.
• The Minidump folder (C:\Windows\Minidump) — a small file snapshot of system state at the moment of the crash.

TuneBit reads both and correlates them so you get a full picture.

What you'll see

For each crash, the analyzer shows:

• Date and time.
• The STOP code (both the hex number and the friendly name, e.g. 0x1E → KMODE_EXCEPTION_NOT_HANDLED).
• The parameter values Windows recorded, if available.
• The dump file path if a minidump was created.
• A plain-English explanation of what that code typically means and the most common causes.

Common BSODs and what they usually mean

• IRQL_NOT_LESS_OR_EQUAL — almost always a bad or outdated driver.
• PAGE_FAULT_IN_NONPAGED_AREA — usually RAM or driver memory issue.
• SYSTEM_SERVICE_EXCEPTION — a driver tried to do something illegal. Check recent driver updates.
• CRITICAL_PROCESS_DIED — a critical Windows process crashed. Sometimes from corrupt system files (try SFC/DISM).
• DRIVER_POWER_STATE_FAILURE — a driver mishandled sleep/wake. Usually fixed by a driver update.
• WHEA_UNCORRECTABLE_ERROR — hardware fault. Check CPU temperatures, overclocks, or bad RAM.

How to investigate a crash

1. Go to Diagnose → Blue Screen Analyzer.
2. Click the most recent crash in the list.
3. Read the description. It'll suggest one of three possible culprits: a driver, a hardware component, or a Windows file.
4. If it blames a driver: open the Driver Manager and check for updates.
5. If it blames hardware: run your system manufacturer's diagnostics, and check for heat / overclocking.
6. If it blames system files: run SFC and DISM from the System Repair Tools page.
7. Click Open Minidump Folder to view dump files. If you want deep analysis, WinDbg or BlueScreenView can crack the minidump open.