Photo by Clint Patterson on Unsplash

It happened to me on a Tuesday afternoon, right in the middle of a Teams call. Screen goes blue, some cryptic stop code flashes for half a second, machine reboots, and Windows acts like nothing happened. No warning. No helpful message. Just a cold reboot and that sinking feeling in your stomach.

The worst part? Windows 11 doesn't exactly make it easy to figure out what just happened. The blue screen shows up, maybe gives you a stop code if you're fast enough to read it, and then it's gone. You're left staring at your desktop wondering if your hardware is dying or if it was just a one-time thing. Spoiler: it's almost never a one-time thing if it's happened twice.

Here's what I've learned after dealing with these for years, both on my own machines and on other people's machines at the worst possible times. The BSOD itself isn't the problem. It's a symptom. And once you figure out what's actually causing it, fixing it is usually pretty straightforward.

What the Error Screen Actually Looks Like

The stop code you'll see varies depending on the cause, but some of the most common ones in Windows 11 look like this:

CRITICAL_PROCESS_DIED
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
IRQL_NOT_LESS_OR_EQUAL
MEMORY_MANAGEMENT
PAGE_FAULT_IN_NONPAGED_AREA
DRIVER_IRQL_NOT_LESS_OR_EQUAL
WHEA_UNCORRECTABLE_ERROR

Each of these points to a different category of problem. MEMORY_MANAGEMENT and PAGE_FAULT ones usually mean RAM issues. DRIVER_IRQL and SYSTEM_THREAD ones almost always mean a bad driver. WHEA_UNCORRECTABLE_ERROR is the scary one — that's usually hardware. Don't panic yet though.

Photo by Bernd 📷 Dittrich on Unsplash

Why It's Probably a Driver

Honestly, in my experience, bad or outdated drivers cause maybe 70% of BSODs I've seen on Windows 11. Microsoft pushed some pretty aggressive updates in the last couple years that broke compatibility with older drivers, especially GPU drivers, network adapters, and Bluetooth stacks. If your BSOD started happening after a Windows Update or after you installed something new, that's your first suspect.

The thing is, Windows 11 is stricter about driver signing and memory access than Windows 10 was. A driver that worked fine for years can suddenly start causing crashes because the OS tightened something under the hood.

To find out which driver is causing it, open Event Viewer. I know, everyone hates Event Viewer. But it actually tells you exactly what crashed.

Press Win + X > Event Viewer
Navigate to: Windows Logs > System
Look for events marked "Critical" or "Error" with source "BugCheck"

You can also use WinDbg or the built-in !analyze command if you want to dig into the minidump files, which live here:

C:\Windows\Minidump

Those files tell you exactly which process or driver triggered the crash. That's your smoking gun.

Photo by Bernd 📷 Dittrich on Unsplash

Fix 1: Roll Back or Reinstall the Offending Driver

Once you've identified the driver (or if you just want to rule it out), here's what to do. Open Device Manager, find the device, right-click, and hit "Properties" then "Driver" tab. You'll see a "Roll Back Driver" option if there's a previous version to go back to.

If rolling back isn't available, uninstall the driver completely and let Windows reinstall a clean version:

devmgmt.msc > Find device > Right-click > Uninstall device
Check "Delete the driver software for this device"
Restart Windows

For GPU drivers specifically, don't just uninstall from Device Manager. Use DDU (Display Driver Uninstaller) in safe mode. It's a free tool and it actually clears all the leftover registry garbage that a normal uninstall misses. Then install the latest driver fresh from NVIDIA or AMD directly, not through Windows Update.

Fix 2: Check Your RAM

If your stop codes are MEMORY_MANAGEMENT, IRQL_NOT_LESS_OR_EQUAL, or PAGE_FAULT in anything, run a memory test before you do anything else. Bad RAM is sneaky. It can work fine for months and then start causing random crashes when a specific address gets hit.

Windows has a built-in tool for this:

Press Win + R > type: mdsched.exe
Choose "Restart now and check for problems"

That runs on reboot before Windows loads. Let it do a full pass, which takes 20-30 minutes. If it finds errors, you have bad RAM. Full stop.

But honestly, Windows Memory Diagnostic misses things sometimes. MemTest86 is more thorough. It's free, you boot it off a USB drive, and you let it run for at least two full passes. If you get any errors at all, even one, that RAM stick is suspect.

# Download MemTest86 from memtest86.com
# Write to USB with Rufus or their own tool
# Boot from USB, run for 2+ passes
# Zero errors = RAM is probably fine

If you have two sticks, test them one at a time. I've seen cases where two sticks work individually but cause crashes together because of timing or voltage issues.

Fix 3: Undo a Recent Windows Update

Look, sometimes Microsoft ships an update that just breaks things. It happens. And the fix is embarrassingly simple — roll it back.

Settings > Windows Update > Update History > Uninstall Updates

Sort by install date and remove the most recent one. Restart. See if the crashes stop. If they do, you've found your problem. You can pause Windows Updates for up to 5 weeks while Microsoft pushes a fix, which they usually do within a patch cycle.

If the machine won't boot far enough to get into Settings, you can do this from the recovery environment:

Boot into Windows Recovery (hold Shift while restarting)
Troubleshoot > Advanced Options > Uninstall Updates

Fallback: Run SFC and DISM If Nothing Else Works

Sometimes system files get corrupted, especially after a rough crash or a failed update. Before you even think about reinstalling Windows, run these two commands from an elevated command prompt:

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

Run DISM first, then SFC. DISM pulls fresh files from Windows Update to repair the image, then SFC uses that to check and fix system files. This takes a while. Let it finish. Then reboot and see where you're at.

If you're still crashing after all of this and your memory tested clean and your drivers are fresh, that WHEA_UNCORRECTABLE_ERROR starts looking more serious. At that point, check your CPU temperatures under load with HWiNFO64 and look for thermal throttling or overtemperature warnings. Sometimes a dried-out thermal paste and a heatsink that needs reseating is all that's between you and stable operation.

But most of the time? It's a driver. It's almost always a driver. Start there, be methodical, and don't reinstall Windows until you've actually tried everything else. I've seen people wipe machines that just needed a GPU driver rollback and it's painful to watch.

You'll get through this. It's annoying as hell right now, but it's fixable.