The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →A Windows stop code is a useful diagnostic clue, not a diagnosis of a failed part. Record the exact code and any “What failed” name, then compare them with recent changes, device or driver warnings, and crash-time logs. On Windows 11 version 24H2 and later, the error screen may be black rather than blue, so use the displayed error—not its color—to identify a stop-code restart.
What to record from the stop-code screen
Before the screen disappears, photograph it or write down the stop-code text exactly as shown. Examples include PAGE_FAULT_IN_NONPAGED_AREA and MEMORY_MANAGEMENT. If the screen also shows “What failed,” preserve that module name and spelling too. Microsoft says the code and, when available, the module name can help determine the cause; neither item by itself proves that a particular component is defective.
As an Amazon Associate I earn from qualifying purchases.
Microsoft refers to these events as stop-code errors, bug checks, kernel errors, blue-screen errors, or BSODs. Windows 11 version 24H2 and later may display a black screen for the error. The relevant Microsoft guidance covers Windows 10 and Windows 11; check Microsoft’s current instructions for later interface or support changes.
What the code can—and cannot—tell you
Microsoft says a hardware device, its driver, or software might have caused the error. The displayed code labels the error Windows reported, but it does not establish a universal code-to-part mapping or identify the root cause on its own. A “What failed” entry names a module involved at the time of failure; it is a lead to investigate, not proof that the named module or its associated hardware is at fault.
#1 Best Overall
To narrow the possibilities, compare the screen details with what changed before the crashes began, whether the same code recurs, device warnings, and Event Viewer entries near the crash time. If those clues do not resolve the issue, additional logs, dump analysis, or hardware testing may be needed; the general Microsoft guidance does not specify which is necessary for an individual PC.
Work through the basic checks in a sensible order
For a one-time unexpected restart, Microsoft says restarting often resolves the issue and no further action is needed. If the error returns frequently, use this sequence and note whether the crashes stop after each change.
- Undo a recent hardware change. If the crashes began after adding hardware, shut down, remove the new device, and see whether Windows starts and runs normally.
- Use Safe Mode if Windows is difficult to start. Start Windows in Safe Mode, then continue with the checks below. Follow Microsoft’s current startup instructions for the Windows version on the PC.
- Check Device Manager. Look for devices marked with an exclamation point. Check for driver updates. If updating does not help, Microsoft suggests trying to disable or uninstall the device.
- Check available disk space. Microsoft gives 10% to 15% free space as a general rule of thumb because Windows and some applications need room for swap files and other functions. The exact need varies with system configuration; this is guidance, not a universal minimum. Microsoft Support’s cited page does not display a publication year.
- Install available Windows updates. Then see whether the stop-code errors recur.
- Consider recovery only if the earlier checks do not help. Choose a Windows recovery option suited to the situation. Back up important files first where possible because some recovery options can cause data loss.
Microsoft’s detailed steps are in Troubleshooting Windows unexpected restarts and stop code errors and Resolving Blue Screen errors in Windows.
Free tools Windows power users keep installed
One-click scans. No signup required.
Collect evidence if crashes continue
For repeated crashes, keep a short record of the exact code, any “What failed” name, and the time of each restart. Then compare those times with related events and diagnostic results:
- Event Viewer: Check the System log for critical errors at the time of the crash. Entries clustered around a restart may help connect the stop code to another event.
- Windows Memory Diagnostic: Run the diagnostic and inspect its result in Event Viewer under MemoryDiagnostics-Results.
- Memory-dump analysis: Dump analysis is an advanced step intended for IT professionals and developers; it can provide evidence beyond the text on the error screen.
Microsoft’s overview of these investigation steps is Resolving Blue Screen errors in Windows.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Use the clues to choose what to investigate next
| Diagnostic axis | Evidence to collect | How it helps |
|---|---|---|
| Recent change | New hardware, driver, app, or update before the first crash | Helps prioritize a reversible change to investigate; Microsoft names these categories in its troubleshooting advice. |
| Device or driver clue | “What failed” name, Device Manager warning, and driver update history | Narrows what to check, but does not establish root cause by itself. |
| Timing and recurrence | Exact code, crash time, and whether the same code returns | Helps compare related entries in Event Viewer’s System log. |
| Memory evidence | Windows Memory Diagnostic result or, for advanced users, dump analysis | Adds diagnostic evidence beyond the stop-code label. |
| Recovery risk | Whether important files are backed up and which recovery option is proposed | Helps account for potential data loss when choosing a recovery path. |
For recovery choices and their implications, see Microsoft’s Recovery options in Windows.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →
