What is Kmode Exception Not Handled, and how do I fix it?

Although far less common today, the “blue screen of death” error screen that appears in Windows when something goes wrong has long been a part of the PC experience. It’s not always serious and is often fixed with a simple reboot, but sometimes you run into a problem that repeats itself over and over. “Kmode Exception Not Handled” is one such problem.

Fortunately, though, this isn’t a serious issue and it’s one that can be fixed in a matter of minutes if you take the right steps. Follow along below to find out how.

Note: Whether you’re running Windows 10 or an older version of Windows, if the blue screen doesn’t allow you to boot to Windows to try the fixes listed below, boot to Safe Mode instead and perform the changes there.

What is Kmode Exception and why isn’t it being handled?

The technicalities of what the Kmode Exception error is are in-depth and more than a little dry. In a nutshell, though, it’s when applications overwrite each other’s memory, causing errors or crashing software, and in the case of a blue screen, a full system crash.

Essentially, some software has been corrupted and the Windows error handler isn’t entirely sure what’s gone wrong. It just knows that something has, and it’s caused the system to fail.

The most likely culprit is a problematic driver.

The quick fix: disable Fast Startup

Windows 10’s Fast Startup feature can be a catalyst for this issue. It’s a Windows feature that allows for fast recovery from hibernation and shutdown, but that can mean it loads back in any driver problems that were present.

Oftentimes disabling Fast Startup can make it so that your system stays up for longer, or even fixes the problem entirely.

To disable Fast Startup follow these steps:

  • Search for “Control Panel” in the Windows search bar and select the corresponding result.
  • Click “System and Security,” followed by “Power Options.”
  • On the left-hand menu, select “Choose what the power buttons do.”
  • If prompted, select the “Change settings that are currently available,” blue link at the top of the page.
  • Under the heading “Shutdown settings,” untick the box that says “Turn on Fast Startup.”
  • When done, click “Save changes.”

If you’re still getting the Kmode Exception error after disabling Fast Startup or want to fix the problem without losing its benefits, you can try tackling the problem at its source.

Updating the problem driver

Since the Kmode Exception Not Handled error is most likely caused by a driver problem, updating the driver can often fix it. To do that, though, you need to know which driver is giving you trouble.

That’s very much dependent on your system, but fortunately, Windows usually gives you a good indication of what the culprit might be. When the blue screen occurs, you will typically see “Error: Kmode_Exception_Not_Handled,” followed by a name in brackets. That name is the driver that’s causing the problem and the one we want to update.

Play out a quest for that driver to discover what equipment it identifies with and afterward follow the means underneath.

  • Type “Device Manager” into the Windows search bar and click the corresponding entry.
  • Find the hardware that corresponds to the driver error and right click it. Choose “Update driver” from the drop-down menu.
  • When given the choice, select “Search automatically for updated driver software,” and wait for the process to complete.

If that doesn’t work, you can always check your motherboard manufacturer’s website to see if there is a new driver release there, or Google the hardware if the driver belongs to an add-in card or other hardware. If so, download it, and perform the driver update manually by selecting “Browse my computer for driver software” instead during the third step.

The process can take a little bit of time, but once complete, you should have a system that no longer throws up Kmode Exception blue screen errors.

It could be your RAM

If you’re still running into problems after the above fixes, you’re either extremely unlucky, or you may have a hardware issue that’s causing the driver corruption. If it turns out to be the latter, the most likely culprit is your RAM. In order to find out if that’s the case, you can use Windows’ own memory diagnostics tool.

  • Search for “Memory Diagnostic” in the Windows search bar and select the corresponding result.
  • If you’re ready to, click “Restart now and check for problems.” Or alternatively, “Check for problems the next time I start my computer,” if you need to save any existing work.

Trust that the output will finish during the reboot. In the event that any hard blunders happen, you probably have flawed RAM that could well the reason for the blue screen(s) you’ve been supplanting. First have a go at eliminating and reseating the RAM to guarantee there was certifiably not a free association. In the event that that fizzles, your smartest choice by then is to supplant the tricky stick or purchase a totally different kit. These are our top picks.