Windows is a relatively stable OS, but the occasional BSOD still annoys users to date. While you can often fix it with a simple reboot, sometimes it sticks around for longer.
In this article, we’re talking about the Kmode exception, why is it being triggered and how you can handle it once and for all.
What is the Kmode exception?
In a nutshell, the exception is triggered when applications start overwriting each other in the computer’s memory. This can indicate a problem with your PC either not having enough memory or your RAM modules failing.
In most cases, you can avoid this by simply not loading your RAM as much, but if it’s a hardware flaw, you’re better off replacing your RAM modules as soon as possible. An out-of-date or corrupt driver can also cause this issue.
Also read: Getting Windows Ready stuck: 5 Fixes
How to fix Kmode exception not handled error?
Here are a few solutions you can try out to fix the issue.
Disable Fast Startup
While fast startup as a feature is usually meant to help users boot their PCs faster, it can sometimes cause issues with your hardware, especially storage devices. Try disabling fast startup to see if that solves your problem.
Step 1: Press the Windows key and search for Power & Sleep Settings. Click the corresponding search result.
Step 2: Click on Additional power settings on the right.
Step 3: Click Choose what the power buttons do on the left.
Step 4: Click the Change settings that are currently unavailable option and then disable the fast startup, sleep and hibernate settings.
Now restart your PC, and it should fix the Kmode exception not handled error.
Run an SFC scan
Corrupt files are the number one reason why your PC might be behaving weirdly. Here’s how you can get rid of them and potentially resolve your issue.
Step 1: Press Windows Key + S to bring up the Cortana/Search box and search for Powershell. Open Windows Powershell from the search results.
Step 2: Type sfc /scannow to scan your system for issues.
Step 3: If the SFC scan finds any problem, use the following command to resolve them.
DISM /Online /Cleanup-Image /RestoreHealth
Restart your PC, and the error should’ve been resolved. If that doesn’t help, you can also run a DISM scan to fix any other errors by using this guide.
Run the Windows Memory Diagnostics tool
If your RAM is seated properly but is failing, it can trigger this error. To check if there’s an issue with your RAM, follow these steps.
Step 1: Press the Windows key and search for Windows Memory Diagnostics. Then, click the corresponding search result.
Step 2: Run the tool and click the Restart now button to check for problems.
If you see some issues, try running the auto-troubleshoot to resolve the Kmode exception not handled error.
Run the Check Disk utility
The BSOD can very well be a sign of your boot drive failing to perform as it should. Try running the check disk utility to check whether or not your storage drives are, in fact, functional.
Update your drivers
Out of date or corrupt drivers can also cause numerous hardware problems leading to BSODs. If you haven’t updated your drivers in a while, now’s the time to do so, especially for your display drivers.
Step 1: Right-click Start and select Device Manager from the menu.
Step 2: Under Display Adaptors, find your graphics card’s name, right-click on it and click on Update Drivers.
Step 3: Click on Search automatically for drivers. Windows will then automatically look for and download the latest drivers for your particular GPU.
While this should help resolve the error, in case it doesn’t, click Uninstall device and restart your PC to force Windows to install the required drivers. You can then update them later.
Repair your system
If nothing else works, the best way to get rid of the error is by simply reinstalling or repairing your OS.
The Windows Media Creation tool is a great way to install Windows and repair the OS. Using this, you can perform a clean installation or repair your OS without affecting your data. This should definitely fix the Kmode exception not handled error if none of the other steps above worked.