- Software and digital services
- Operating system
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x7E) on Windows: unhandled exception
Risk level
Medium
Proceed carefully and stop if the check is unclear.
Urgency
High
Quick answer
Windows stopped because a system thread raised an exception nothing caught. Note the driver name shown on screen and remove or undo the last hardware or driver you installed.
Safety first
Stop and check this first
- Before restoring or resetting Windows, copy your files: 0x7E alone does not prove a part is faulty, and the deeper recovery options can erase data.
Safe checks you can perform
- Stop code and driver name
- Recently added hardware
- Device Manager and Safe Mode
- Updates and System Restore
Leave these tasks to a qualified professional
- Do not attempt this professional task: Analyse the memory dump
- Do not attempt this professional task: Firmware and maker diagnostics
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Analyse the memory dump
What they doThe technician opens MEMORY.DMP or the minidump in WinDbg, runs !analyze -v and checks the exception code (parameter 1) and address (parameter 2) to identify the driver.
They must show youthe !analyze -v output with the module it points to.
In writingwhich driver was identified and what was done with it (updated, uninstalled).
Firmware and maker diagnostics
What they doThey check with the PC maker for newer ACPI or BIOS firmware and run the maker's hardware diagnostics.
They must show youfirmware versions before and after and the diagnostic report.
In writingwhether the hardware passed and, if a part is replaced, its reference and reason.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Stop code and driver name
- Who:
- you.
- How:
- take a photo of the blue screen; back in Windows, open Event Viewer, Windows Logs, System, and look for errors at the same time.
- Result that matters:
- whether a specific driver or device is named.
- If one is named:
- that driver is the first suspect; update it from its maker's site or uninstall it.
- If none is named:
- go on to recent hardware.
- Evidence to keep:
- photo of the screen and a screenshot of the event with its time.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Recently added hardware
- Who:
- you, with the PC shut down and unplugged.
- How:
- disconnect what you added last and can remove without tools (USB peripherals, memory cards) and start again.
- Result that matters:
- whether the blue screens stop without that device.
- If they stop:
- that device or its driver triggers the exception; ask the maker about compatibility.
- If they continue:
- it was not that device; do not open the case to pull internal parts.
- Evidence to keep:
- what you removed and how many days it stayed stable.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Device Manager and Safe Mode
- Who:
- you.
- How:
- if Windows keeps restarting, start in Safe Mode; open Device Manager (right-click Start) and look for devices with an exclamation mark; choose Update driver and, if that does not help, disable or uninstall it.
- Result that matters:
- whether any device shows an error and whether the problem stops after updating it.
- If it stops:
- that device's driver was the cause.
- If no device shows an error:
- go on to updates and restore.
- Evidence to keep:
- screenshot of the device with the error and the driver version.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors
Updates and System Restore
- Who:
- you.
- How:
- install the latest updates in Settings, Windows Update; if it continues, use a restore point from before the first crash.
- Result that matters:
- whether crashes stop after updating or restoring.
- If they stop:
- a software or driver change made after that point was the cause.
- If they continue:
- hand the case to a technician with the memory dump.
- Evidence to keep:
- date of the restore point and of the updates installed.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- Microsoft Windows
- Product type
- Operating system
Known code variants
- 0x0000007E
- 0x7E
- STOP 0x0000007E
- stop code SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
- SYSTEM THREAD EXCEPTION NOT HANDLED
What it means
Microsoft defines bug check 0x0000007E as an exception raised by a system thread that the error handler did not catch. Parameter 1 is the exception code (for example 0xC0000005, a memory access violation) and parameter 2 the address where it occurred, which usually identifies the responsible driver. Microsoft names a driver, outdated ACPI or BIOS firmware and hardware issues such as incompatibilities or memory or IRQ conflicts as possible origins. The code does not say which: only that the kernel could not handle the exception.
Warnings and stop conditions
- Mediumeditorial warning
Before restoring or resetting Windows, copy your files: 0x7E alone does not prove a part is faulty, and the deeper recovery options can erase data.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Symptoms and causes
Probable causes · in order
- Driver named on the blue screenCommon
If the screen or Event Viewer names a specific driver, Microsoft says to disable it or ask its maker for an updated version.
Evidence: Bug Check 0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
- New hardware that is not compatiblePossible
Suspected if the crashes started after installing a part or peripheral; Microsoft asks you to confirm it is compatible with your Windows version.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
- Outdated ACPI or BIOS firmwarePossible
With no named driver and no recent changes, Microsoft says to ask the PC maker for firmware updates.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Bug Check 0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
- Memory or IRQ conflictLess common
Microsoft lists it among the hardware issues that cause this code; only a maker or technician diagnostic confirms it.
Evidence: Bug Check 0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Virtual technician
Does SYSTEM_THREAD_EXCEPTION_NOT_HANDLED still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Stop code error or bug check troubleshooting (IT professionals)
Microsoft · 2026 · official_doc
- 2
Troubleshooting Windows unexpected restarts and stop code errors
Microsoft · 2026 · official_doc
- 3
Bug Check 0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Microsoft · 2026 · official_doc
Was this entry useful?