SYSTEM_THREAD_EXCEPTION_NOT_HANDLED — 0x7E and parameters
Bug Check 0x7E is the same stop as SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. This page explains what the on-screen parameters mean and which fix branch to open next.
.sys / .exe file name — then follow that branch.
Step 1 — Capture the full stop screen
- Disable automatic restart (System Properties → Startup and Recovery) so the blue screen stays visible.
- Photo the stop code, parameter list, and “What failed” file name.
- If the PC reboots too fast, use WinRE → Startup Settings to turn off automatic restart, or read a minidump later.
Step 2 — Map Bug Check 0x7E parameters
Microsoft’s debugger documentation for Bug Check 0x7E defines the parameter block as:
- Parameter 1 — Exception code that was not handled
- Parameter 2 — Address where the exception occurred
- Parameter 3 — Address of the exception record
- Parameter 4 — Address of the context record
Common parameter-1 exception codes you may see on the screen or in dump summaries:
0xC0000005— Access violation (bad pointer / driver bug)0x80000003— Breakpoint / assertion style fault0x1000007E— Related encoding of the same bugcheck family in some reports
Parameters help experts confirm the exception type. For DIY repair, the failing module name usually matters more than memorizing addresses.
Step 3 — Use the failing module name
Route by the file shown on the stop screen or in a dump summary:
nvlddmkm.sys→ NVIDIA driver pagentoskrnl.exe→ ntoskrnl page (often a third-party driver underneath)etd.sys→ ELAN touchpad driver page- No module readable → home tree or boot loop
Step 4 — Pick the next page by timing
Branches
Symptom map
- SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (start here)
- Enter Safe Mode for this stop code
- Read the minidump / faulting module
- 0x7E parameters and exception codes
- After a Windows Update
- On startup / boot
- Boot loop / keeps restarting
- During Windows install
- Faulting module nvlddmkm.sys
- Faulting module ntoskrnl.exe
- Faulting module etd.sys
- SYSTEM_SERVICE_EXCEPTION (different stop code)
FAQ
What does 0x7E mean?
It is Bug Check 0x7E — SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. A system thread threw an exception the error handler did not catch, almost always inside a driver.
What about 0x1000007E?
Search reports often show 0x1000007E alongside this stop. Treat it as the same family: capture the module name and follow driver/update branches.
Do I need to decode every address?
No. Addresses matter for debugging with symbols. Home users should prioritize module name, recent updates, and Safe Mode driver rollback.