System Thread Exception Not Handled

Home / Safe Mode

Fix SYSTEM_THREAD_EXCEPTION_NOT_HANDLED from Safe Mode

Safe Mode starts Windows with a minimal set of drivers. Microsoft’s stop-code guide uses it early when crashes repeat. Use this page to get in, then do only Safe Mode–safe repairs before branching to a module or update page.

First cut If you can already boot normally, you may not need Safe Mode — go to the matching intent page (after update, nvlddmkm, etc.). Use Safe Mode when normal boot keeps hitting 0x7E or when uninstalling a driver crashes mid-process.

Step 1 — Open Windows Recovery Environment

Microsoft documents these paths:

Windows RE Troubleshoot menu with Advanced options highlighted by a red box
WinRE is the reliable door into Startup Settings when the desktop will not load.

Step 2 — Startup Settings → Safe Mode

  1. Troubleshoot → Advanced options → Startup Settings → Restart.
  2. After reboot, press 4 (or F4) for Safe Mode. Press 5 for Safe Mode with Networking only when this PC has to download a vendor driver. A driver copied from another PC on a USB drive does not need Networking.
  3. Option 9 disables automatic restart on system failure — useful so the next 0x7E stays on screen.

If BitLocker is on, have the recovery key ready — Microsoft notes encryption can block Startup Settings until unlocked.

Step 3 — Repairs that belong in Safe Mode

  1. Roll back or uninstall the suspect driver in Device Manager (Display, Mice/touchpads, Network). Prefer Roll Back when the problem started after an update.
  2. Uninstall a recent quality/feature update if timing matches — continue on after update.
  3. System Restore to a point before the stop codes began (WinRE also offers this).
  4. Optional: open an elevated Command Prompt and run sfc /scannow, then DISM restorehealth when networking is available — only after you know which module is not simply a third-party .sys.
GPU module named Continue nvlddmkm.sys
Touchpad etd.sys Continue etd.sys
Device Manager in Safe Mode with Display adapters selected and Roll Back Driver circled in red
Roll back or remove the named driver while third-party start drivers stay unloaded.

Step 4 — Leave Safe Mode

A normal restart usually exits Safe Mode. If Windows keeps booting into Safe Mode: Win+R → msconfig → Boot tab → clear Safe boot → OK → restart (Microsoft Support).

Branches

Still loops before Safe Mode boot loop
Need the module name from a dump minidump
Only fails after updates after update
Back to overview home decision tree

FAQ

Why Safe Mode for this stop code?

0x7E is frequently a third-party driver. Safe Mode loads a limited driver set, so you can remove or roll back the bad one without immediately re-triggering the crash.

Safe Mode with Networking or plain Safe Mode?

Use plain Safe Mode first. Use Networking only if you must fetch a vendor driver on that PC; otherwise download on another machine and use USB.

How do I get out of Safe Mode?

Restart normally, or clear the Safe boot checkbox in msconfig as Microsoft documents.

Official and primary sources

  1. Microsoft Support — Windows startup settings (Safe Mode)
  2. Microsoft Support — Windows Recovery Environment
  3. Microsoft Support — Unexpected restarts and stop codes

Symptom map