A blue screen is Windows protecting your data, not punishing you. When the kernel detects a fault it cannot safely continue with, it stops - and it leaves the stop code behind as the first sentence of the story. This master guide decodes every major stop error: what it usually means, what it never proves on its own, and the fix order that matches the code.
Most blue screen advice fails because it treats every crash the same. In reality the stop code is a sorting tool: it cuts the list of possible causes from everything in the PC down to two or three suspects. Use this page as the map - find your code in the master list, note which family it belongs to, do the three universal first moves, then follow that code's own case page for its specific fix order. One honest warning before you start: a code narrows the search, it does not finish it. The pattern across several crashes - the same code, the same file named, the same moment - is what finally convicts the culprit.
The blue screen gives you three pieces of evidence, and most people use none of them. First, the stop code name in capitals - that is the family of the failure. Second, on many crashes a line says What failed: followed by a file name ending in .sys - that is the driver that was running when Windows gave up. Third, the timing: does it crash at boot, in a game, at idle, or randomly? Take a photo of the screen before you restart. After the restart, the same code is saved in Event Viewer as BugCheck, Event ID 1001, with the hex value in brackets - for example 0x00000050 for PAGE_FAULT_IN_NONPAGED_AREA. Every case page in this guide is named by that code, so find yours in the master list above and go straight to it.
The nine codes fall into five families, and the family tells you where to look first. Memory family (0x50, 0x1A, and often 0xA): the fault involves RAM or something writing into the wrong memory. Driver family (0x3B, 0x133, and often 0xA): a driver misbehaved or stopped answering. Boot and storage family (0x7B): Windows cannot reach the disk it boots from. Integrity family (0x139, 0xEF): the kernel found its own structures damaged, or a process it depends on has died. Hardware family (0x124): the processor itself reported the error - treat software fixes as a waste of time until hardware is cleared. Notice that 0xA appears in two families. That overlap is normal, and it is the first lesson of this guide: the code narrows the search, it does not end it.
sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow once more. This pair fixes the large share of crashes caused by damaged Windows filesGeneric fix lists are why blue screens drag on for weeks. Reinstalling Windows does nothing for a dying SSD, and a memory test does nothing for a boot-mode change in BIOS. Each family has a correct order: memory codes start with a RAM test, boot codes start in the BIOS storage settings, the watchdog code starts with the storage driver and SSD firmware, and WHEA starts with removing every overclock. The case pages of this guide give each code its own order - work through yours from the top, change one thing at a time, and note what you changed. And when one crash follows another with a different code each time, that pattern itself is a clue: random codes usually mean one unstable thing underneath - RAM, heat, or power - not nine separate faults.
The full BSOD master guide - every major stop error explained with its fix, shown live, step-by-step.
Watch Full VideoOpen Event Viewer, go to Windows Logs, System, and look for the source BugCheck with Event ID 1001 - it lists the hex code, such as 0x00000050. Reliability Monitor (search View reliability history) also shows the same crash as a Windows failure entry with the code.
No. Most blue screens are caused by drivers and damaged system files, which are software. Only one code in this guide, WHEA_UNCORRECTABLE_ERROR (0x124), is the hardware reporting its own fatal error - and even that one asks for tests before you buy parts.
Write down the code and the date, and note what changed just before it - a new driver or update is the usual trigger. A single crash is a note; the same crash twice is a task. Repeated blue screens always deserve the fix order, because the underlying fault does not heal itself.