0X0000007E
What it means
A system thread generated an error a driver didn't catch — very commonly graphics or Wi-Fi drivers right after an update.
Also seen as: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, 0x7E
Quick fix steps
- Boot into Safe Mode and check whether it stops happening.
- Update your graphics and Wi-Fi drivers first — the two most common causes.
- Roll back any driver updated right before the crashes started.
For the full step-by-step walkthrough, see How to Read and Respond to Any Blue Screen.
Frequently Asked Questions
Is this the same as other driver-related stop codes?
It's in the same general family (a driver causing an unhandled system exception), similar in spirit to IRQL and KMODE_EXCEPTION errors, though the exact technical trigger differs.
Does updating Windows itself help with this?
Yes, sometimes — Microsoft periodically ships driver compatibility fixes through regular Windows updates, so keeping Windows current is a reasonable general step alongside updating the specific driver.
Other error codes
0X0000001A — MEMORY_MANAGEMENT
Points to a problem with how memory is being handled — faulty RAM, a driver mismanaging memory, or disk corruption.
0X0000000A — IRQL_NOT_LESS_OR_EQUAL
Almost always a driver issue — most commonly network, audio, or graphics drivers.
0X000000EF — CRITICAL_PROCESS_DIED
A core Windows process crashed unexpectedly — often tied to a recent update or corrupted system files.
0X0000001E — KMODE_EXCEPTION_NOT_HANDLED
A driver running in kernel mode hit an error it couldn't recover from — usually a specific faulty or outdated driver.