A blue screen of death (BSOD) is Windows crashing hard enough that it can't recover on its own. The screen goes blue, a stop code appears, and your PC restarts. It's alarming the first time it happens. But the stop code isn't just decoration: it tells you exactly what broke, and most common Windows errors have a well-worn path to a fix. This guide covers the errors you're most likely to see, what causes them, and what to do next.
What the stop code is actually telling you
Every BSOD includes a stop code, usually written in uppercase with underscores (for example, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED). Windows 10 and Windows 11 also display a QR code you can scan to go straight to Microsoft's support page for that error. The stop code is the first thing to record. Take a photo with your phone before the machine restarts, or check Event Viewer after the fact: search for "Event Viewer" in the Start menu, then go to Windows Logs and select System. Look for entries marked "Critical" with the source "BugCheck".
The stop code narrows the problem to one of four general categories: a driver conflict, a hardware fault, a corrupted system file, or a software conflict. Getting to the right fix depends on knowing which bucket you're in.
The most common BSODs and what causes them
IRQL_NOT_LESS_OR_EQUAL
This is one of the most frequent stop codes. It means a driver or kernel process tried to access memory it wasn't allowed to touch. The usual suspects are a recently installed or updated driver (most often a graphics, network, or storage driver), a faulty RAM stick, or overclocked hardware running out of spec.
Start by rolling back any driver updated in the 24 hours before the crash. Right-click the Start button, open Device Manager, find the device in question, and choose Properties, then Driver, then Roll Back Driver. If the BSOD appeared after a Windows Update, check if that update included driver changes. You can uninstall it via Settings, Windows Update, Update History, Uninstall Updates.
PAGE_FAULT_IN_NONPAGED_AREA
This one points to bad RAM or a corrupt driver trying to read memory that doesn't exist or isn't mapped correctly. Run Windows Memory Diagnostic (search for it in the Start menu) to test your RAM overnight. If the test returns errors, the RAM needs replacing. Two sticks installed? Try running with one at a time to isolate the fault.
SYSTEM_SERVICE_EXCEPTION
Usually caused by a driver bug or a corrupted system file. Run System File Checker: open Command Prompt as Administrator and type sfc /scannow. Windows scans protected files and replaces any it finds corrupt. Follow that with a DISM check: DISM /Online /Cleanup-Image /RestoreHealth. Both tools together fix the majority of corrupted file problems without reinstalling Windows.
CRITICAL_PROCESS_DIED
Windows killed itself because a process essential to its operation stopped unexpectedly. This is often a software conflict (a third-party security tool or system utility fighting with Windows), but it can also be a failing drive. Check the drive health first.
Open Command Prompt as Administrator and run chkdsk C: /f /r. The scan runs on next reboot and marks bad sectors. If the drive reports many bad sectors, treat it as a hardware warning: a drive that starts failing won't get better on its own, and you'll want a backup before the situation gets worse.
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Similar to its cousin above, but this version names the driver file directly in the stop code (look for a filename ending in .sys). That filename is your lead. Search it online to find which software or hardware it belongs to, then update or uninstall that driver. If the driver belongs to antivirus software, temporarily disabling it is a quick way to confirm whether it's the culprit.
MEMORY_MANAGEMENT
A memory management stop code almost always means RAM. Run Windows Memory Diagnostic as described above, but also check whether your RAM is seated correctly. Power off the PC, open the case, remove each RAM stick, and reseat it firmly. Dusty slots can cause intermittent contact faults that only show up under load.
KERNEL_SECURITY_CHECK_FAILURE
This one appears when Windows detects that a core data structure has been corrupted. It's commonly triggered by outdated drivers, overclocking, or malware. Run sfc /scannow first. Then check whether the system is overclocked: reset BIOS to default settings and see if the crashes stop. If you suspect malware, there are clear signs your computer has a virus or malware worth checking before you assume it's a hardware problem.
How to diagnose a BSOD you can't pin down
Some BSODs don't happen often enough to catch in the act, or they produce a different stop code each time. That second scenario usually means RAM or a failing drive rather than a specific driver. Random stop codes with no pattern are hardware's signature. Run both memory diagnostics and a chkdsk scan, and check the drive's S.M.A.R.T. data using a free tool like CrystalDiskInfo, which reads the drive's built-in health log and flags sectors that are starting to fail.
If the PC BSODs only under load (gaming, video editing, rendering), heat is a strong candidate. Clean the fans and heatsink, reseat the CPU cooler if comfortable doing so, and check temperatures using a monitoring tool like HWiNFO. CPU temperatures above 95°C under sustained load indicate a cooling problem, not a software one.
When a clean Windows install is the right answer
If sfc, DISM, driver rollbacks, and hardware checks all come back clean but the BSODs continue, a clean Windows install is faster than chasing software ghosts. Windows 11 lets you do this while keeping your personal files: go to Settings, System, Recovery, and choose Reset this PC, then Keep my files.
Before you do anything that touches your data, make sure you have a backup. A BSOD that happens frequently is a sign the system is under stress, and stressed systems fail in unpredictable ways. Keeping a 3-2-1 backup strategy in place means that whatever the root cause turns out to be, your files are safe while you work through it.
When to call a technician
Four situations justify getting professional help rather than continuing to troubleshoot:
- The BSOD happens during POST (before Windows loads), which points to hardware failure rather than software.
- Memory Diagnostic or chkdsk confirms bad hardware and you're not comfortable replacing RAM or a drive yourself.
- The PC won't stay on long enough to run any diagnostic tools.
- You've completed every step above and the problem persists.
At that point the fix is likely physical: a RAM replacement, a new drive, or in some cases a failed GPU or motherboard. A technician can run component-level tests in minutes that would take hours to replicate at home.