kmode exception not handled

kmode exception not handled in windows 10, how to fix?

This message indicates that a kernel-mode process tried to execute an incorrect or unknown processor instruction. This error handler is a default error handler that catches errors not associated with other specific error handlers. The KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.

kmode exception not handled


The following parameters are displayed on the blue screen.

Parameter Description
1 The exception code that was not handled
2 The address at which the exception occurred
3 Parameter 0 of the exception
4 Parameter 1 of the exception

kmode exception not handled Cause

This is a common bug check. To interpret it, you must identify which exception was generated.

Common exception codes include:

  • 0x80000002: STATUS_DATATYPE_MISALIGNMENTAn unaligned data reference was encountered.
  • 0x80000003: STATUS_BREAKPOINTA breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.
  • 0xC0000005: STATUS_ACCESS_VIOLATIONA memory access violation occurred. (Parameter 4 of the bug check is the address that the driver attempted to access.)

How to Fix

Unplug any peripheral devices – printer, microphone, etc…

While in Safe Mode with Networking. Go to computer manufacturer’s site and look for updates.

Open Device Manager

  • In main menu Click on View > Show Hidden Devices.
  • Do you see any yellow exclamation or question marks? If so, post back code errors associated with the device

Check disk for errors

  • Open a command prompt (CMD.exe)¬†using Run As Administrator. Windows logo + X then type cmd.
  • Type chkdsk /F /R.
  • Press Enter.
  • You will receive a message regarding volume needs to be locked and would you like to start scan on reboot.¬† Press Y and Press Enter.
  • Reboot Computer for scan to begin.
  • Scan log can be found when Windows reloads in Event Viewer > Windows Logs > Application Log.
  • Look for Winninit.

Run System file checker to verify the integrity of Windows File

  • Again open a command prompt window using Run As Administrator.
  • Type sfc /scannow.
  • Press Enter

Leave a Reply

Your email address will not be published. Required fields are marked *