Kmode_Exception_Not_Handled on Windows 11 or 10 (Fix)

The scariest and most frustrating issue that can happen to your Windows computer is a Blue screen of death error that appears out of nowhere. It usually happens when your Windows crashed entirely, which as a result, you can’t do anything except to restart your computer.

Blue screen often comes with a STOP code error to help identify the source and cause of the BSOD problem. This post explains what the BSOD STOP code KMode Exception Not Handled indicates in Windows 11 or Windows 10 (particularly after Windows Update or fresh Windows installation) and how to fix the issue.

Related issueHow to Fix Blue Screen With Sad Face on Windows 10 or 11 PC


The KMode Exception Not Handled blue screen error, in most cases, is a result of conflicts in memory overwriting between programs and Windows when they run in the Kernel mode. Thus, the STOP code can be caused by invalid, corrupted or missing Windows system files, registry and drivers.

An incorrectly installed software or a faulty hardware such as RAM or HDD could also be the reason why the blue screen error appears.

Some users from various forums also reported that the KMODE_EXCEPTION_NOT_HANDLED error may occur in Windows 11 or 10 and may caused by a driver file called ntfs.sys. Some also reported that the error could be caused by overclocking of hardware.

Since the reasons that can cause this specific blue screen error is vast, it can become very complicated when troubleshooting the error. However, we’ve sorted out the most common causes of this error and have listed the most working solutions below.

KMode Exception Not Handled Windows 10

Disable Fast Startup

In most cases, the STOP code KMode Exception Not Handled error in Windows 11 or 10 can be caused by a boot option called Fast Startup when it’s enabled in Windows. Disabling it should fix the issue. Here’s how to do so.

  1. Go to start menu or Cortana.
  2. Search for and open Control Panel.
  3. Click on System and Security.
  4. Then, click on Power Options.KMode Exception Not Handled Windows 10 overclock vmware workstation
  5. From the left pane, click on Choose what the power buttons do.Windows 10 Choose what the power buttons do
  6. On the right, click Change settings that are currently unavailable to unlock the Shutdown settings.Power options Change settings that are currently unavailable
  7. Uncheck Turn on fast startup option to disable fast startup.KMode Exception Not Handled Windows 10 Update Fix 2018
  8. Restart your computer.

If you can’t boot into Windows to perform the changes in the first place, read how to enter Safe Mode in Windows 11/10 from BIOS.

Update your hardware drivers

If you have problem trying to make changes in Windows before the blue screen kicks in, or you can’t even boot into Windows due to the blue screen error, go to the link shown above to force your PC to enter safe mode without logging in.

Then, in safe mode, go to start menu. Search for and open Device Manager. In Device Manager, click on View from the menu, then click Show hidden devices. This is to ensure every connected hardware is shown on the list.

From the list look for devices with yellow exclamation mark beside it, usually named Unknown device, under Other devices category. Right-click these devices and then select Update driver software to allow Windows to update the driver automatically.

Since the BSOD error directly relates to drivers of your connected hardware, updating these missing or corrupted drivers may help to fix the issue.

KMode Exception Not Handled Windows 10 Ntfs.sys fresh install

Remove recently installed programs

If the methods above fail to resolve your issue, try to recall what program or software you’ve recently installed right before the error started to occur. Try to uninstall these programs and see if it fixes the error.

The KMODE_EXCEPTION_NOT_HANDLED error also implies that there could be conflicts between Windows and installed program when handling memory used. If a program is incompatible with how Windows works, it may indirectly cause the BSOD error.

Published by Nyau Wai Hoe - Updated on