System Thread Exception Not Handled (0x7E): Fix Guide

To fix SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x7E), identify the failing .sys driver named on your blue screen. Boot into Safe Mode, open Device Manager or run PnPUtil to uninstall the faulty driver, and run DISM to repair corrupt system dependencies. Most crashes stem from corrupted graphics, audio, or network drivers.

Your monitor freezes. Audio stutters into a loud buzz. Seconds later, Windows crashes to a blue screen displaying stop code SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (also logged as 0x0000007E).

For many users, the crash repeats every time Windows attempts to load. The system falls into an endless reboot loop.

In our lab, we diagnose dozens of 0x7E blue screens every month. The root cause is almost never damaged motherboard silicon or a fried CPU.

Instead, an active kernel thread called a device driver that executed an illegal memory instruction.

Here is how our workbench team identifies the failing driver, restores boot stability, and permanently clears error 0x7E.

Step 1: Identify What Failed on the Blue Screen

Modern Windows blue screens often display the culprit directly below the stop code.

Look for a line that reads:

What failed: [filename].sys

Here is a breakdown of the most common driver filenames we encounter in lab crash dumps:

Common 0x7E Failing Drivers Matrix
┌──────────────────┬───────────────────────┬────────────────────────────┐
│ Driver File      │ Component             │ Manufacturer / Source      │
├──────────────────┼───────────────────────┼────────────────────────────┤
│ nvlddmkm.sys     │ Graphics Driver       │ NVIDIA GeForce GPU         │
│ amdkmdag.sys     │ Graphics Driver       │ AMD Radeon GPU             │
│ igdkmd64.sys     │ Graphics Driver       │ Intel Integrated Graphics  │
│ RTKVHD64.sys     │ Audio Driver          │ Realtek High Definition HD │
│ Netwtw10.sys     │ Wi-Fi Adapter         │ Intel Wireless Adapter     │
│ rtwlane.sys      │ Wi-Fi Adapter         │ Realtek Wireless Adapter   │
│ vgc.sys          │ Anti-Cheat Kernel     │ Riot Vanguard              │
│ EasyAntiCheat.sys│ Anti-Cheat Kernel     │ Epic Games / EasyAntiCheat │
│ fltmgr.sys       │ File System Filter    │ Antivirus / Backup Filter  │
└──────────────────┴───────────────────────┴────────────────────────────┘

If your screen rebooted before you could read the filename, do not worry. Windows records the crash parameters inside the System Event Log.

Step 2: How to Escape a 0x7E Boot Loop

If your PC crashes before reaching the Windows desktop, you must enter Safe Mode.

Safe Mode starts Windows with a minimal set of generic drivers. Third-party GPU, audio, and network drivers remain unmounted. This stops the crashing thread from firing during startup.

Recovery Boot Flow
[Power Button ON] → [Hold 5s to Force OFF] (Repeat 2x)
       ↓
[Automatic Repair Screen] → [Advanced Options]
       ↓
[Troubleshoot] → [Advanced Options] → [Startup Settings]
       ↓
[Restart] → [Press 4: Safe Mode] (or Press 5: Safe Mode with Networking)

Follow this sequence to access Safe Mode:

1. Turn on your PC. As soon as you see the spinning Windows loader, press and hold the power button for five seconds to force a shutdown.
2. Repeat this process two times.
3. On the third restart, Windows enters the Automatic Repair environment.
4. Select Advanced options > Troubleshoot > Advanced options > Startup Settings.
5. Click Restart.
6. When the menu appears, press 4 (or F4) to boot into standard Safe Mode. Press 5 if you need internet access to download replacement drivers.

Once your desktop loads in Safe Mode, you can troubleshoot without fear of sudden reboots.

Step 3: Extract the Offending Driver via PowerShell

If your blue screen did not specify which file failed, inspect the crash dump log directly.

Open PowerShell as Administrator and run this command:

Get-WinEvent -FilterHashtable @{LogName='System'; Id=1001} -MaxEvents 5 | Where-Object { $_.Message -match '0x0000007e' } | Format-List TimeCreated, Message

Inspect the Message text. Look for the driver filename ending in .sys near the end of the error string.

If the output lists ntoskrnl.exe instead of a third-party driver, the unhandled exception occurred in the central Windows kernel. This indicates corrupted system files or unstable memory timings.

Step 4: Roll Back or Uninstall the Failing Driver

Once you know the faulty driver, remove it using Device Manager or the Windows CLI.

Method A: Device Manager Rollback (Safe Mode)

1. Right-click the Start button and select Device Manager.
2. Expand the section corresponding to the culprit:
   • For nvlddmkm.sys or amdkmdag.sys, expand Display adapters.
   • For Netwtw10.sys or rtwlane.sys, expand Network adapters.
   • For RTKVHD64.sys, expand Sound, video and game controllers.
3. Right-click the affected device and select Properties.
4. Switch to the Driver tab.
5. Click Roll Back Driver if the button is active. This restores the previous working driver version.
6. If the rollback button is grayed out, click Uninstall Device, check the box to Attempt to remove the driver for this device, and click Uninstall.

Method B: PnPUtil Command-Line Removal (Advanced Recovery)

If Device Manager fails to open or crashes, remove the driver package using the built-in PnPUtil tool.

Open Command Prompt as Administrator and run:

pnputil /enum-drivers

Locate the entry matching the malfunctioning device (for example, oem24.inf).

Force-uninstall the bad driver package with this command:

pnputil /delete-driver oem24.inf /uninstall /force

Restart your computer. Windows will boot normally using standard fallback drivers.

Step 5: Clean GPU Driver Installation with DDU

In our testing lab, display drivers account for over 60 percent of 0x7E crashes.

Standard driver updates often leave orphan registry keys and mismatched DLLs behind. To fix stubborn GPU crashes, perform a clean wipe with Display Driver Uninstaller (DDU).

1. Download the latest version of Display Driver Uninstaller from Wagnardsoft.
2. Download the newest standalone installer for your GPU (NVIDIA Studio/Game Ready or AMD Adrenalin).
3. Disconnect your ethernet cable and turn off Wi-Fi. This prevents Windows Update from auto-installing an older driver.
4. Boot into Safe Mode.
5. Launch DDU, select your GPU type, and click Clean and restart.
6. After Windows boots back into normal mode, run your downloaded GPU installer and choose a Clean Installation.

Reconnect your internet once the installation finishes.

Step 6: Repair Corrupted Kernel Dependencies with DISM and SFC

If the failing file is ntoskrnl.exe or fltmgr.sys, system files on your storage drive are likely damaged.

Repair them using the deployment image servicing tool and system file checker.

Open Command Prompt as Administrator and run these two commands in order:

DISM /Online /Cleanup-Image /RestoreHealth

Let the DISM tool reach 100 percent completion. DISM contacts Windows Update servers to replace damaged system component files with fresh copies.

Next, run the system file checker:

sfc /scannow

Restart your computer when both scans finish.

Summary Checklist

When error 0x7E strikes, follow our four-step triage order:

1. Read the .sys file on the blue screen to identify the failing hardware component.
2. Boot into Safe Mode to bypass third-party drivers if trapped in a restart loop.
3. Roll back or clean-install the responsible driver using Device Manager or DDU.
4. Run DISM and SFC to ensure underlying kernel binaries remain fully intact.