A blue screen crash always shows a stop code, and that code narrows down the cause significantly — most BSODs aren't random, they point to a specific driver, hardware issue, or system file problem.
1. Note the exact stop code
The blue screen shows a code like DRIVER_IRQL_NOT_LESS_OR_EQUAL or MEMORY_MANAGEMENT. Write it down or photograph it before restarting — this is the single most useful piece of information for diagnosing the actual cause, and searching it specifically gets you much further than searching "blue screen" generically.
2. Check Reliability Monitor after rebooting
Search for Reliability Monitor from the Start menu. It logs crashes with timestamps and often more detail than the blue screen itself showed, including which specific driver or app was involved.
3. Driver-related codes point to recently changed hardware or drivers
If the stop code mentions a driver (many do, directly or indirectly), think about what changed recently — a new peripheral, a graphics driver update, a new printer. Roll back or update the specific driver via Device Manager rather than guessing broadly.
Tip: if the crash started right after a Windows Update, especially with a graphics or storage driver code, try rolling back the update via Settings > Windows Update > Update history > Uninstall updates.
4. Run Windows Memory Diagnostic
Search for Windows Memory Diagnostic and run it — it restarts your PC and tests RAM for errors. Memory-related stop codes specifically benefit from this, since faulty RAM is a genuinely common cause of intermittent, hard-to-diagnose crashes.
5. Run an SFC and CHKDSK scan
Open Command Prompt as administrator and run sfc /scannow to check for corrupted system files, then chkdsk /f (requires a restart to run) to check your drive for file system errors. Both are common underlying causes of crashes that don't point to an obvious single driver.
6. Boot into Safe Mode if crashes prevent normal use
If your PC crashes too quickly or frequently to troubleshoot normally, boot into Safe Mode (hold Shift while clicking Restart, then Troubleshoot > Advanced options > Startup Settings). Safe Mode loads minimal drivers, which lets you determine if a specific driver is the cause by seeing if it's stable there.
7. Check for recent hardware changes
If you've recently added RAM, a new drive, or any internal component, reseat it to rule out a loose connection — a surprisingly common, simple cause of crashes that look like a software problem.
The bottom line
The stop code is genuinely useful information, not just an error message to dismiss. Note it, check Reliability Monitor for more context, and focus on what changed recently before assuming a deeper hardware failure.