SYSTEM_THREAD_EXCEPTION_NOT_HANDLED — stop code 0x0000007E — means a thread running in the Windows kernel hit an error nobody caught, so the system crashed. Threads in kernel mode are usually drivers doing work on behalf of the system, which is why this stop code is a driver problem in the overwhelming majority of cases.

The genuinely useful thing about this particular blue screen is that Windows often prints the culprit right on the screen: “What failed: somefile.sys.” If you caught that name, you are halfway done. If the screen vanished too fast, the minidump has the same information. Here is the practical path from crash to fix.

Why this happens

  • A driver crashes inside a system thread. The core mechanism — a driver throws an unhandled exception while executing as a system thread.
  • Buggy graphics drivers. The single most common named culprit across crash reports, especially after driver updates.
  • Corrupted driver files. A damaged .sys on disk crashes the same way a buggy one does.
  • Incompatible driver after a Windows update. The update changes kernel behavior the old driver was not built for.
  • Overclocked GPU or unstable drivers. Factory-overclocked laptop GPUs with marginal stability crash their drivers under load.
  • Conflicting drivers. Two drivers for related hardware stepping on each other inside the same thread.
  • Failing hardware behind the driver. Rare, but a dying GPU or storage device can crash its driver repeatedly.

How to fix it

Work through these in order, from least to most invasive. If the blue screen named a file, skip straight to the fix for that driver.

Fix 1: Note the “What failed” file name

Before changing anything, capture the clue Windows gives you for free.

  1. The next time it crashes, look for the “What failed:” line on the blue screen — for example, nvlddmkm.sys (NVIDIA), igdkmd64.sys (Intel graphics), or rtwlane.sys (Realtek Wi-Fi).
  2. Photograph the screen with your phone so you have the exact spelling.
  3. If the screen reboots too fast to read, disable auto-restart first — our guide on disabling automatic restart after a blue screen shows how.
  4. That file name maps directly to a device and driver — everything below targets it.

Fix 2: Boot into Safe Mode to confirm it is a driver

Safe Mode loads only Microsoft’s essential drivers, which makes it a perfect diagnostic.

  1. Interrupt boot three times to reach recovery, then Troubleshoot > Advanced options > Startup Settings > Restart, and press 4.
  2. If the laptop is stable in Safe Mode, a third-party driver is confirmed as the cause.
  3. If it crashes in Safe Mode too, the problem is deeper — skip to Fix 6 for system file repair.
  4. While in Safe Mode, you can safely perform the driver updates and removals in the fixes below.
  5. Our Safe Mode troubleshooting guide covers alternative entry methods if the standard path fails.

Fix 3: Update or clean-reinstall the named driver

Target the exact driver from the “What failed” line or the dump analysis.

  1. Open Device Manager and find the device matching the file name.
  2. Right-click > Update driver > Search automatically for drivers.
  3. If that does not resolve it, download the latest stable driver from the laptop maker’s support page or the GPU vendor.
  4. For graphics drivers, do a full clean reinstall: boot to Safe Mode, run Display Driver Uninstaller (DDU), then install the fresh driver — use the NVIDIA download page or AMD driver page for the new copy.
  5. Restart normally and test with the workload that used to crash.

Fix 4: Roll back if the crash followed an update

A driver or Windows update that arrived just before the crashes is guilty until proven innocent.

  1. In Device Manager, open the device’s Properties > Driver tab.
  2. Click Roll Back Driver, choose a reason, and restart.
  3. For a Windows update cause, go to Settings > Windows Update > Update history > Uninstall updates and remove the recent one.
  4. Pause updates for a couple of weeks while the vendor ships a fixed driver.
  5. Reinstall the update only after confirming a fixed driver version is available.

Fix 5: Read the minidump when no file was shown

If the blue screen never named a file, the dump will.

  1. Press Win + R, type %SystemRoot%\Minidump, and press Enter.
  2. Open the newest dump in WinDbg Preview and run !analyze -v.
  3. The MODULE_NAME line names the faulting driver even when the blue screen did not.
  4. Take that name back to Fix 3 and treat it as the target.
  5. If the dump names ntoskrnl.exe with no third-party driver in the stack, suspect hardware or system corruption — continue below.

Fix 6: Repair system files with SFC and DISM

When the faulting module is a Windows component, repair the OS files.

  1. Open an elevated Command Prompt.
  2. Run sfc /scannow and wait for completion.
  3. Then run DISM /Online /Cleanup-Image /RestoreHealth and restart.
  4. Test stability for a day or two of normal use.
  5. Microsoft documents both repair tools on the Windows support hub .

Fix 7: Test hardware as a last resort

If no driver is ever named and repairs change nothing, check the hardware.

  1. Run mdsched.exe and choose the Extended memory test.
  2. Run chkdsk C: /f /r from an elevated Command Prompt (type Y and restart).
  3. Check drive SMART health with CrystalDiskInfo.
  4. For laptops with discrete GPUs, stress-test the GPU with a tool like FurMark briefly — artifacts or crashes under load point at the GPU hardware.
  5. Persistent 0x7E crashes with clean software and healthy RAM/drive mean professional diagnosis — likely the motherboard or GPU.

Closing

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED is Windows telling you a driver crashed inside a system thread — and half the time it even names the file on the blue screen. Photograph that name, update or clean-reinstall that driver, and confirm stability in Safe Mode along the way. It is one of the most straightforward blue screens to fix once you stop treating it as a mystery and start treating it as a driver with a name.

Frequently asked questions

What does SYSTEM_THREAD_EXCEPTION_NOT_HANDLED mean?
It is a blue screen stop code (0x0000007E) meaning a system thread threw an exception the error handler did not catch. In practice, a driver crashed inside a system thread — the dump usually names which one.
Why does the blue screen sometimes show a file name?
When Windows can identify the faulting module, it prints it on the blue screen — something like ‘What failed: nvlddmkm.sys’. That file name is your biggest clue; photograph it before the screen disappears.
Is this error always a driver problem?
Almost always. System threads are kernel territory, so when one crashes it is typically a driver running inside it. Hardware causes exist but are rare — start with drivers and only test hardware if dumps are inconclusive.
Can I fix it from Safe Mode?
Yes — Safe Mode loads only essential drivers, so if the crashes stop there, you have confirmed a third-party driver is the cause. Update or remove drivers from Safe Mode, then reboot normally to verify.