SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Stop Code: SYSTEM THREAD EXCEPTION NOT HANDLED fix

Windows Errors Intermediate 👁 0 views 📅 May 25, 2026

This blue screen usually shows up after a driver or Windows update. It's a conflict between a driver and your hardware.

You're working on your Windows 10 machine — say, a Dell XPS 13 or a custom-built desktop with an Nvidia GeForce RTX 3060 — and it crashes hard. The screen goes blue. The stop code reads: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. Maybe you just installed a Windows Update (like KB5036893) or updated your graphics driver through GeForce Experience. Or maybe you plugged in a new USB Wi-Fi adapter. That's the exact trigger: a new driver or update that doesn't play nice with your hardware.

Root cause in plain English

Every driver in Windows runs as a thread — a small program inside the system. When that thread tries to do something the hardware doesn't support (like accessing a memory address that doesn't exist), the CPU throws an exception. If the driver doesn't handle that exception gracefully, the system panics. That's the blue screen you're staring at.

Common culprits: graphics drivers (nvidia, amd, intel), network drivers (realtek, intel), or storage drivers (especially those from motherboard chipset updates). The error message might name the driver — like nvlddmkm.sys for Nvidia or rtwlanu.sys for Realtek wireless. If it doesn't, you'll need to dig into the minidump file to find the name.

The fix: remove the bad driver

You don't need to reinstall Windows. You don't need to run a system restore. The real fix is to get rid of the driver or update that caused this. Here's how to do it without pulling your hair out.

Step 1: Boot into Safe Mode

  1. Restart your PC. As soon as it starts loading (before Windows logo appears), press and hold the power button to force shutdown. Do this 3 times.
  2. On the 4th boot, you'll see a blue screen that says "Automatic Repair." Click Advanced options.
  3. Choose TroubleshootAdvanced optionsStartup SettingsRestart.
  4. After the restart, press 4 or F4 to select Enable Safe Mode.
  5. Wait for Safe Mode to load. The screen will say "Safe Mode" in the corners. This might take a few minutes.

Step 2: Uninstall the recent driver or update

If you know what changed — maybe you installed an Nvidia driver yesterday — skip to the device manager method below. If you're not sure, check the installed updates first.

Option A: Remove a Windows Update

  1. In Safe Mode, click the Start button and type View installed updates. Open that control panel item.
  2. Look for any update with a recent install date (the day the crashes started). Right-click it and choose Uninstall.
  3. After the uninstall finishes, restart your PC normally. If the blue screen doesn't come back, you're done.

Option B: Roll back or uninstall a driver

  1. Press Win + X and choose Device Manager.
  2. Expand the category for the device you suspect — for graphics, it's Display adapters. For Wi-Fi, it's Network adapters.
  3. Right-click the device and choose Properties.
  4. Go to the Driver tab. If the Roll Back Driver button is available, click it. That reverts to the previous driver version that worked.
  5. If the button is grayed out, you'll need to uninstall the driver instead. Click Uninstall Device. Check the box that says Delete the driver software for this device.
  6. Restart your PC. Windows will install a generic driver that won't crash.

Step 3: If you don't see the driver name in the error

Some BSODs don't show the driver name on the blue screen. You'll need to check the minidump file.

  1. Boot back into Safe Mode.
  2. Open File Explorer. Navigate to C:\Windows\Minidump. If that folder doesn't exist, you're out of luck — skip to step 4.
  3. Inside you'll see one or more .dmp files. The most recent one matches your crash. To read it, you need a tool like BlueScreenView (free). Download it from a working PC onto a USB stick, then run it in Safe Mode. BlueScreenView will list the driver that caused the crash under the Filename column.
  4. Once you know the driver file (like nvlddmkm.sys), search online for which device it belongs to. Then go back to Device Manager, find that device, and roll back or uninstall the driver.

Step 4: Still failing? Disable the driver at boot

If you can't boot into Safe Mode at all (rare, but happens), you can disable the offending driver from the recovery environment.

  1. Boot from a Windows installation USB. Choose your language, then click Repair your computer at the bottom-left.
  2. Go to TroubleshootAdvanced optionsCommand Prompt.
  3. Type regedit and press Enter. In Registry Editor, highlight HKEY_LOCAL_MACHINE, then click FileLoad Hive.
  4. Browse to C:\Windows\System32\config and select the file named SYSTEM (no extension). Give it a key name like TempHive.
  5. Navigate to HKEY_LOCAL_MACHINE\TempHive\ControlSet001\Services. Find the subkey named after your driver (like nvlddmkm). Change Start value to 4 (disabled).
  6. Highlight HKEY_LOCAL_MACHINE\TempHive, click FileUnload Hive. Close everything and restart.

What to check if it still fails

If you've uninstalled the driver and the BSOD still happens, the problem isn't the driver — it's the hardware itself. Test your RAM with MemTest86 (boot from a USB, let it run for at least one full pass). Check your hard drive with chkdsk C: /f /r from a command prompt. If those pass, you might have a failing motherboard component — time to call the manufacturer for warranty service.

One more thing: if the error mentions hal.dll or ntoskrnl.exe without a driver name, your system files might be corrupted. Run sfc /scannow in Safe Mode, then DISM /Online /Cleanup-Image /RestoreHealth. That fixes most corruption BSODs I've seen.

Was this solution helpful?