SYSTEM_THREAD_EXCEPTION_NOT_HANDLED is Windows stop code 0x0000007E (0x7E). Microsoft's reference says it means "a system thread generated an exception that the error handler didn't catch." The sentence is almost the same as the one for 0x1E, and the two codes share exception codes, but they are separate stop codes with different parameter layouts.
Microsoft's advice for people without a debugger runs through the System Log, the named driver, firmware updates from the hardware vendor, BIOS memory caching, hardware diagnostics and hardware compatibility.
This page is built from the Microsoft Learn article "Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" and, where noted, Microsoft's general page on analysing blue screen data, both read on 13 October 2026 and checked against the Microsoft Docs source files. Microsoft marks the 0x7E page as written for programmers and directs customers to https://www.windows.com/stopcode. Anything taken from the general page rather than the 0x7E page is labelled as such.
What do the four parameters say?
As printed in Microsoft's reference for 0x7E:
| Parameter | What Microsoft says it holds |
|---|---|
| 1 | The exception code that wasn't handled |
| 2 | The address where the exception occurred |
| 3 | The address of the exception record |
| 4 | The address of the context record |
Compared with 0x1E, the third and fourth parameters are more useful here: they point to the exception record and the context record themselves, which a debugger can read directly.
How does 0x7E differ from 0x1E?
Both pages describe an exception that nothing handled. Putting Microsoft's two pages side by side:
| Question | 0x1E KMODE_EXCEPTION_NOT_HANDLED | 0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED |
|---|---|---|
| Who raised the exception | A kernel-mode program | A system thread |
| Parameter 3 | Exception information parameter 0 of the exception record | The address of the exception record |
| Parameter 4 | Exception information parameter 0 of the exception record | The address of the context record |
| Common exception codes named | 0x80000002, 0x80000003, 0xC0000005 | 0x80000002, 0x80000003, 0xC0000005 |
The shared exception codes mean the same thing on both pages: a misaligned data reference, a breakpoint hit with no debugger attached, and a memory access violation. The difference is who was running when it happened.
What does Microsoft say about the exception address?
The Resolution section says that, for people who plan to debug, the exception address in parameter 2 "should identify the driver or function that caused this problem." If a driver is listed by name in the message, Microsoft says to disable or remove it. If the issue narrows to one driver, a developer can set breakpoints and single-step to find the failure.
Two debugger extensions are named for deeper work, !thread and the dds, dps and dqs family of memory-display commands, and Microsoft says that technique is reasonable when WinDbg reports "Probably caused by : ntkrnlmp.exe." For a non-programmer, the takeaway is that a name like ntkrnlmp.exe on its own is not a conclusion, it is the point where the debugger stops guessing.
What does each exception code imply for the next step?
The Resolution section ends with short notes on two of the codes. Putting them next to the third:
| Exception code | What Microsoft's Resolution section says |
|---|---|
| 0x80000002 (misaligned data reference) | The trap frame supplies additional information |
| 0x80000003 (breakpoint) | A hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch; if it occurs repeatedly, make sure a kernel debugger is connected and the system is started with the /DEBUG switch |
| 0xC0000005 (access violation) | No separate note on the 0x7E page beyond the exception address in parameter 2 |
Microsoft calls the breakpoint problem rare, so a repeated 0x80000003 in parameter 1 is unusual by Microsoft's own description.
Why does Microsoft bring up firmware and the BIOS?
In the Remarks, Microsoft says to check with the hardware vendor for any ACPI or other firmware updates, because hardware issues such as system incompatibilities, memory conflicts and IRQ conflicts can generate the error. It also says you can disable memory caching or shadowing of the BIOS and run the hardware diagnostics that the system manufacturer supplies. This is the part of the page that goes beyond drivers.
What Microsoft tells non-programmers to do
If you are not equipped to use the Windows debugger, Microsoft says to use basic troubleshooting techniques. The 0x7E page lists them in this order:
- Check the System Log in Event Viewer for more error messages that might identify the device or driver.
- If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
- Check with your hardware vendor for ACPI or other firmware updates.
- Disable memory caching or shadowing of the BIOS, and run the hardware diagnostics that the system manufacturer supplies.
- Confirm that any new hardware is compatible with the installed version of Windows.
That is the whole list on the 0x7E page. There is no step about memory tests from Windows itself, disk checks or system file repair, and this page does not add any under Microsoft's name.
Checklist before changing anything
- Photo of the blue screen, including any driver name it shows
- Parameter 1 from the System Log (the exception code)
- Whether a firmware or BIOS update is available from the maker
- New hardware added recently
- Whether the BIOS has a memory caching or shadowing option
How to work through a 0x7E blue screen
- Photograph the screen and note any driver name
- Check the System Log for related errors
- Disable or update the named driver
- Look for firmware updates and run the manufacturer's diagnostics
Registry edits and paid tools. Microsoft's page does not mention them, so neither does this one.
Which tools does the 0x7E page name for people who do debug?
The Resolution section names specific debugger commands rather than leaving "use a debugger" vague. Microsoft says the !analyze extension displays information about the bug check and can be helpful in determining the root cause, and that more analysis can be done using the !thread extension and the dds, dps and dqs commands, which display words and symbols. Microsoft adds that this second technique is reasonable when WinDbg reports "Probably caused by : ntkrnlmp.exe" — that is, when the automatic answer points at the kernel itself rather than at a named driver. Where the issue is narrowed down to a single driver, the same section suggests setting breakpoints and single-stepping forward in code to locate the failure.
Where does the full list of exception codes live?
The 0x7E page names three common exception codes and then points elsewhere for the rest. For a complete list, Microsoft refers to the NTSTATUS values reference, and says the exception codes are defined in *ntstatus.h*, a header file provided by the Windows Driver Kit. Parameter 1 is therefore not limited to the three codes quoted above. A value that is not one of them is looked up in that reference rather than guessed, which is why this page does not try to list more of them.
Every stop code covered here is listed in our Windows blue screen stop code index.
Sources and how to check
- Microsoft Learn, "Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" — https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7e--system-thread-exception-not-handled. Source file in the MicrosoftDocs/windows-driver-docs repository.
- Microsoft Learn, "Analyze bug check (stop code error) data" — https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/blue-screen-data (general guide).
- Bug check code reference, Microsoft Learn: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
- Troubleshoot blue screen errors (for regular users): https://www.windows.com/stopcode
- Licence and credit: Microsoft Learn documentation is published under CC BY 4.0. This page selects, rewords and reorders it, adds a plain-language reading, and is not endorsed by Microsoft. The original is linked above.
- Checked as of 13 October 2026.
Questions readers ask about SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Blue Screen 0x7E
What is stop code 0x7E?
It is SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x0000007E). Microsoft says a system thread generated an exception that the error handler didn't catch.
How is 0x7E different from 0x1E?
0x1E is raised for a kernel-mode program and 0x7E for a system thread. Their parameters also differ from the third one on.
What does parameter 2 tell me?
Microsoft says the exception address should identify the driver or function that caused the problem.
Should I update firmware?
Microsoft says to check with your hardware vendor for any ACPI or other firmware updates.
Does Microsoft say how to fix it for sure?
No. It lists checks, not a guaranteed fix.