System Thread Exception Not Handled? Read the Driver (2026)

By LK Wood IV · 2026-07-13 · ~8 min read · St. Louis County, MO

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (stop code 0x0000007E) is one of the friendlier blue screens, because it usually tells you what broke. A system thread threw an error nothing caught — and that thread almost always belongs to a driver. Better still, Windows often prints the guilty driver’s filename right there in parentheses. Your job is to read that name and fix that one driver, not to reinstall everything and hope.

The one thing that makes this error easy: the parentheses

Most blue screens give you a cryptic code and nothing else. This one frequently shows something like:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (nvlddmkm.sys)

That .sys in parentheses is the driver that crashed. It turns a vague “something’s wrong” into a one-driver fix. If you see a name, you’re most of the way there. If you don’t see one (the screen flashes too fast, or it’s blank), the minidump gives you the same answer — covered in Step 3.

Step 1: Get into Safe Mode

If the system boots normally between crashes, you can work from the desktop. If it’s boot-looping, you need Safe Mode first:

1. Force-power-off during boot three times (hold the power button as Windows starts to load) to trigger Automatic Repair.
2. Choose Advanced options → Startup Settings → Restart.
3. Press 5 for Safe Mode with Networking (so you can download a driver).

Safe Mode loads Windows with generic drivers, so the crashing driver is inactive and you can replace it.

Step 2: Fix the named driver

With the .sys name in hand:

• Graphics driver (nvlddmkm.sys / atikmdag.sys): the clean fix is DDU (Display Driver Uninstaller) in Safe Mode, then install a fresh driver — the full process is in our GPU driver crash fix guide. If the crash started right after a driver update, install the previous stable version rather than the newest.
• Network / Wi-Fi driver (netwtw*.sys, rt*.sys): update it from the laptop or adapter maker’s site (Intel, Realtek, Qualcomm), which is usually newer than Windows Update’s build.
• Any other driver: in Device Manager, find the device, open the Driver tab, and either Roll Back Driver (if it broke after an update) or Update driver. Roll Back is the fastest fix when a recent update caused it.

Step 3: If no driver is named, read the minidump

When the blue screen doesn’t show a name, the crash dump has it:

1. Install BlueScreenView (free, portable) and point it at C:\Windows\Minidump.
2. It lists the .sys that was executing when the thread threw — the same driver you’d have read on the blue screen.

Then fix that driver per Step 2. This is why you almost never need to reinstall every driver for 0x7E — the system tells you which one, one way or another.

Going deeper: the exception code inside the 0x7E

0x7E is a wrapper — a thread inside a driver threw an exception nobody caught — and the first parameter of the bug check is the actual exception code, which changes the diagnosis (parameter layout per Microsoft’s bug-check 0x7E reference; the code meanings are standard Windows NTSTATUS values):

To read it, open the .dmp from C:\Windows\Minidump in WinDbg (free in the Microsoft Store, Ctrl+D) and run !analyze -v: the exception code is the first bug-check argument, and MODULE_NAME at the bottom confirms the .sys. A 0xC0000005 points you back at Step 2’s driver fixes; a 0xC000001D sends you to the RAM test first — that ordering difference is the whole value of reading the code.

Step 4: System files, then hardware (last)

If the driver path is genuinely exhausted:

• Repair system files: in an admin Terminal, run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, and reboot — useful when a bad update damaged a system driver.
• Test RAM: unstable memory can make a driver throw exceptions. Run MemTest86 overnight, and if you run XMP/EXPO, test at default JEDEC speed.
• Check GPU temperature: an overheating graphics card can crash its own driver — confirm temps are in range under load before blaming the card itself.

The fix order, in one list

1. Read the .sys in parentheses (or from the minidump).
2. Boot Safe Mode (Automatic Repair → Startup Settings → Safe Mode with Networking).
3. Fix that one driver — DDU for graphics, vendor update for network, Roll Back for a post-update break.
4. System files / hardware last — sfc + DISM, then MemTest86 and GPU temps.

Because 0x7E is a driver throwing an uncaught exception — and it usually names the driver — this is one of the fastest blue screens to fix once you know to read the parentheses. If it shows up alongside other stop codes or random reboots, the whole-system flow in PC keeps restarting and computer keeps freezing maps each code to its fix, and the storage-driver sibling DPC watchdog violation covers the other common driver-timeout blue screen.

Sources

• Stop code identity: Microsoft’s Bug Check 0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED — a system thread generated an exception the error handler did not catch; the parameters identify the exception and the driver. The driver-first ordering and the parenthetical-.sys behaviour are standard and self-verifiable, corroborated across Microsoft Q&A, Tom’s Hardware and Level1Techs threads that repeatedly trace 0x7E to a graphics or device driver.
• Tools: BlueScreenView (NirSoft) for C:\Windows\Minidump; DDU (Wagnardsoft) for clean GPU-driver reinstalls; Windows Safe Mode and Device Manager Roll Back Driver are built-in. Driver identifiers nvlddmkm.sys (NVIDIA) and atikmdag.sys (AMD) are standard, verifiable names.

Valid for Windows 10 and 11 in 2026. If an update relocated a setting referenced here, email hello@techfuelhq.com with the article URL.