Skip to content
littleden.blogEvidence-led Windows troubleshooting, without the guesswork
FixesError codesComponentsCommandsWindows updatesWindows 11
Research statusMethodology
Blue screens & stop codes · scoped error record
0x0000007E

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED: an unhandled kernel thread exception

Bug check 0x7E means a system thread generated an exception that the error handler did not catch.

Applies to: Windows stop-code / bug-check contextReviewed: 2026-09-17

What it means in this context

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x7E) is a bug-check class, not a single root cause. Microsoft notes that the exception code and the address/module involved are important to interpretation, so preserve the crash details instead of applying one universal fix.

Start here
  1. Record the stop code, exception information and any driver/module name displayed.
  2. Remove newly added hardware if the crashes began immediately afterward.
  3. Check Device Manager and recent driver changes.
  4. Install current Windows updates.
1

Act on a named driver when the crash identifies one

Medium risk

Why: Microsoft notes that the exception address can identify the driver or function involved.

  1. Record the named driver/module rather than guessing from the stop-code text alone.
  2. Update or roll back that driver according to the change timeline.
  3. Use Safe Mode if the driver prevents stable normal startup.
2

Use general stop-code isolation when no module is named

Medium risk

Why: 0x7E can arise from different exceptions, so hardware/driver isolation is more defensible than an unrelated fixed script.

  1. Remove recent nonessential hardware.
  2. Check Device Manager for errors.
  3. Use Safe Mode to test whether third-party drivers/services are involved.
Scope boundary

When not to use this record

Do not assume 0x7E proves a specific driver or bad RAM without the exception/module evidence.

If it persists

Persistent 0x7E crashes without an obvious module are candidates for memory-dump analysis because the exception code and faulting address matter.

Evidence

Reviewed source

Related authority records

Continue with the same failing system

These links share the same component or repair context; they are not generic keyword suggestions.

Error0x00000050 — PAGE_FAULT_IN_NONPAGED_AREA: invalid system memory was referenced

Microsoft defines bug check 0x50 as an invalid system-memory reference; driver and memory evidence matter.

Error0x000000D1 — DRIVER_IRQL_NOT_LESS_OR_EQUAL: a kernel driver made an invalid high-IRQL memory access

Microsoft describes bug check 0xD1 as a kernel-mode driver accessing pageable or invalid memory at an IRQL that was too high.

Error0x0000009F — DRIVER_POWER_STATE_FAILURE: driver stuck in a power transition

Microsoft defines bug check 0x9F as a driver in an inconsistent or invalid power state.

Error0x00000116 — VIDEO_TDR_FAILURE: Windows could not recover the display driver after a GPU timeout

Bug check 0x116 occurs when Windows attempts to reset the display driver after a timeout and recovery fails.

ErrorEvent ID 1001 — WER-SystemErrorReporting bugcheck: preserve the stop code and dump path

When Event ID 1001 says the computer rebooted from a bugcheck, the useful evidence is the exact bugcheck code, parameters and saved dump.

ErrorIRQL_NOT_LESS_OR_EQUAL — IRQL_NOT_LESS_OR_EQUAL: driver and memory-oriented stop-code diagnosis

Use the stop-code context to check recent drivers and memory rather than treating the crash as a generic Windows error.