System thread exception not handled

Windows stop code SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (bug check 0x7E) means a system thread raised an exception the kernel did not catch — often a bad or outdated driver. Confirm the stop code and any faulting file name, then follow the matching branch. Do not jump to a full reinstall first.

Do not skip the first cut Microsoft documents 0x7E as an unhandled exception in a system thread. Parameter 1 is the exception code; the blue screen may also name a driver (.sys). Write those down before changing anything. Official reference: Bug Check 0x7E. If the stop code is SYSTEM_SERVICE_EXCEPTION instead, leave this tree → system service exception.

Step 1 — Read the blue screen once

Stop code text — Must say SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (spaces or underscores). Variant spellings on Win10/11 still map to 0x7E.
Faulting file — If shown (for example nvlddmkm.sys, etd.sys, ntoskrnl.exe), that name picks the driver branch.
When it hit — After a Windows Update, only at startup, in a reboot loop, or during install each go to different pages.

Windows blue screen with stop code SYSTEM_THREAD_EXCEPTION_NOT_HANDLED and a faulting .sys filename circled in red — Note the stop code and any module name before the PC reboots.

Need the four bugcheck parameters decoded? See bugcheck codes.

Step 2 — Stop automatic restart if the screen flashes by

Microsoft’s consumer stop-code guide starts by removing new hardware and entering Safe Mode when crashes repeat. If the PC reboots too fast to read the screen:

If you can reach desktop briefly: System Properties → Advanced → Startup and Recovery → uncheck Automatically restart.
If you cannot: use Windows RE → Troubleshoot → Advanced options → Startup Settings → choose Disable automatic restart on system failure.

Startup Settings / Safe Mode steps: Safe Mode guide.

Step 3 — Branch on timing and module

Right after Windows Update
→ after update

Only at startup / login
→ on startup

Keeps BSOD-rebooting
→ boot loop

During Windows setup
→ during install

Module nvlddmkm.sys
→ NVIDIA driver

Module etd.sys
→ touchpad driver

Module ntoskrnl.exe
→ ntoskrnl

Have a .dmp file
→ analyze minidump

Step 4 — First diagnostic branches (do these early)

Need a stable environment to remove a driver
→ Safe Mode

Need the exact faulting module from a dump
→ minidump analysis

Microsoft’s basic stop-code steps include Safe Mode, Device Manager updates, free disk space, and Windows Update — then restore if needed. Prefer OEM or GPU-vendor packages; never random “driver packs.”

Decision tree diagram from blue screen to Safe Mode, minidump, update, and driver module branches with red arrows — Timing and module name choose the next page — not a one-click tool.

Step 5 — Safe basics while you decide

Unplug recently added hardware (USB devices, docks, new GPUs) and retest — Microsoft’s first consumer step for repeating stop codes.
In Device Manager, fix any device with a yellow bang: update from the vendor, or roll back if the problem started after a driver change.
Keep free space on the system drive; install pending quality updates only after you can boot stably.
Run Windows Memory Diagnostic if dumps or forums point at RAM / access violations (common 0xC0000005 exception under 0x7E).

Wrong stop code? SYSTEM_SERVICE_EXCEPTION (0x3B) is a different bug check. Cross-link only — do not merge the pages.

Symptom map

FAQ

What does SYSTEM_THREAD_EXCEPTION_NOT_HANDLED mean?

Microsoft’s bug-check reference: a system thread generated an exception that the error handler did not catch. Bug check value is 0x0000007E. Interpreting it requires identifying the exception (parameter 1) and often the driver named on the blue screen.

How do I fix system thread exception not handled?

There is no single switch. Read the module name, enter Safe Mode if needed, then follow the matching branch (update rollback, GPU driver, touchpad driver, boot loop). Analyze a minidump when the screen does not name a file.

Is this the same as system service exception?

No. SYSTEM_SERVICE_EXCEPTION is bug check 0x3B. Related troubleshooting ideas overlap (drivers, dumps), but the stop codes differ — use that page.

What if Windows 10 and Windows 11 both show this?

Same bug check. Win10/11 wording and recovery UI differ slightly; the decision tree (module → Safe Mode → driver/update) still applies. Variants like “SYSTEM_THREAD_EXCEPTION_NOT_HANDLED” with underscores are the same stop code.

Should I download a “BSOD fix” tool?

No. This site does not sell one-click fixes or driver packs. Use Microsoft Safe Mode, Device Manager, vendor drivers, and documented dump analysis.

System thread exception not handled

Step 1 — Read the blue screen once

Step 2 — Stop automatic restart if the screen flashes by

Step 3 — Branch on timing and module

Step 4 — First diagnostic branches (do these early)

Step 5 — Safe basics while you decide

Symptom map

FAQ

Official and primary sources