STOP 0x0000001E
KMODE_EXCEPTION_NOT_HANDLED
A program error happened deep inside Windows (kernel mode) and nothing caught it. The address in the crash data usually points straight at the driver responsible.
Likely causes, most common first
- A buggy or outdated device driver
- Antivirus or anti-cheat software hooking the kernel
- Faulty RAM
- Corrupted system files after a failed update
How to fix it
1. Update or reinstall the identified driver easy
- Update the driver named in the report from the vendor's own site.
- If it's an antivirus or anti-cheat component, update or reinstall that software instead — or remove it temporarily to confirm it's the cause.
2. General cleanup easy
- Run Windows Update including optional driver updates.
- Run Windows Memory Diagnostic to rule out RAM.
- In an admin terminal run: sfc /scannow
The four parameters on the blue screen
Windows shows four hex numbers with this stop code. Here's what each means — our analyzer decodes them automatically from your dump file.
| Parameter 1 | Exception code that was not handled |
| Parameter 2 | Address where the exception occurred |
| Parameter 3 | Parameter 0 of the exception |
| Parameter 4 | Parameter 1 of the exception |
Got a crash dump? Get your verdict in seconds
Drop the .dmp file into our analyzer — it runs entirely in your browser. No upload, no size limit, no account.
Analyze my dump file →