FIX · CRASHES AND BLUE SCREENS
SYSTEM_
This blue screen means a system thread raised an exception that nothing caught. It often gives you a head start: when a driver is identified, its name appears in the bug check message. Note that name before you restart, because it decides what you do next.
Updated .
TECHNICAL SUMMARY
| Stop code | 0x0000007E |
|---|---|
| Meaning | A system thread generated an exception the error handler did not catch |
| Best clue | A driver name in the bug check message |
| Other causes | System incompatibilities, memory conflicts, IRQ conflicts |
| PC Tweaker plan | No control fixes it; Tweaky Driver lists your drivers |
If the screen names a driver
Microsoft's advice is to disable the driver or check with its manufacturer for an update. A file name ending in .sys is the driver's file, so search for which device or program installed it before you remove anything.
If no driver is named
Work through Microsoft's basic checks for people who are not using the Windows debugger.
- Check the System log in Event Viewer for messages that identify a device or driver
- Ask your hardware vendor for ACPI or other firmware updates
- Run the hardware diagnostics your PC's manufacturer supplies
- Confirm that any new hardware is compatible with your version of Windows
- If your firmware offers it, Microsoft also suggests disabling BIOS memory caching or shadowing
When WinDbg blames the kernel
Microsoft notes that WinDbg can report Probably caused by: ntkrnlmp.exe for this code. That is the kernel, and the exception address in parameter 2 should identify the driver or function that caused the problem.
Do it by hand
Check the System log (read-only)
Critical and error entries from the last 24 hours. Move StartTime back if the crash was earlier, and look for a device or driver named close to the time of the blue screen.
PowerShellGet-WinEvent -FilterHashtable @{LogName='System'; Level=1,2; StartTime=(Get-Date).AddDays(-1)} -MaxEvents 30 | Format-Table TimeCreated, ProviderName, Id -AutoSizeList your recent stop errors (read-only)
The message gives the code and its four parameters. An error saying no events were found means Windows has not logged one.
PowerShellGet-WinEvent -FilterHashtable @{LogName='System'; Id=1001; ProviderName='Microsoft-Windows-WER-SystemErrorReporting'} -MaxEvents 5 | Format-List TimeCreated, MessageOpen Device Manager
Find the device that uses the named driver, then update it or disable it from its properties.
cmddevmgmt.msc
With PC Tweaker
PC Tweaker does not read crash dumps, and none of its controls fixes this error. If the logs point to a driver, Tweaky Driver, our free driver update checker, shows that device's driver version, the updates available and where the package comes from before you install anything.
Rather not edit the registry by hand?
PC Tweaker shows the exact change before it runs, records the value it replaces and puts it back with Restore. The Free plan needs no account. If a payment fails or a plan ends, Pro tools lock; changes already applied stay as they are and Restore still undoes them.
Common questions
How do I fix SYSTEM_THREAD_EXCEPTION_NOT_HANDLED?
If the blue screen names a driver, disable it or get an update from its manufacturer. Otherwise check the System log, ask your hardware vendor for firmware updates, run the manufacturer's hardware diagnostics, and confirm new hardware is compatible.
What does SYSTEM_THREAD_EXCEPTION_NOT_HANDLED mean?
A system thread generated an exception that the error handler did not catch. Microsoft says hardware issues such as system incompatibilities, memory conflicts and IRQ conflicts can also cause it.
What if the blue screen names a .sys file?
That is a driver's file. Find which device or program it belongs to, then update it or disable it.
Try PC Tweaker
Free download for Windows 10 and Windows 11.