Blue Screen (BSOD) Diagnostic
Different stop codes have different, specific causes. If you caught the code name on the crash screen, this gets you to the exact guide fast — if you didn't, start with the first question.
Did you catch the stop code's name or number before it restarted?
This is genuinely common, and there's a real way to find out after the fact. Our general BSOD guide covers checking the crash minidump to identify exactly what happened, plus the broad first steps that apply no matter which stop code it turns out to be.
Good — move through the next questions to find the guide built for your exact code.
Does the code mention "IRQL" (like IRQL_NOT_LESS_OR_EQUAL or IRQL_UNEXPECTED_VALUE)?
Go straight to our IRQL_NOT_LESS_OR_EQUAL guide — it covers both this code and IRQL_UNEXPECTED_VALUE, since the underlying causes and fixes overlap almost completely.
Move to the next question.
Does the code say MEMORY_MANAGEMENT?
Go straight to our MEMORY_MANAGEMENT guide.
Move to the next question.
Does the code say CRITICAL_PROCESS_DIED?
Go straight to our CRITICAL_PROCESS_DIED guide.
Move to the last question.
Does the code mention HYPERVISOR, or the number 0x20001?
Go straight to our HYPERVISOR_ERROR guide — this one is specifically tied to virtualization software (VMware, VirtualBox) conflicting with Windows' own hypervisor features.
Whatever the exact code, our general BSOD guide covers the broad causes and diagnostic steps (minidump analysis, driver checks, memory and disk testing) that apply across nearly every stop code, including ones without their own dedicated guide yet.