Синий экран (BSoD) с кодом KMODE EXCEPTION NOT HANDLED — один из самых сложных в диагностике, особенно в случае, если на экране не сообщается о каких-либо сбойных модулях (.sys), его вызвавших. Однако, попробовать разобраться и решить проблему можно.
В этой инструкции подробно о возможных способах исправить ошибку на синем экране KMODE EXCEPTION NOT HANDLED в Windows 10 в зависимости от ситуации и сопутствующих появлению проблемы нюансов.
- Причины ошибки KMODE EXCEPTION NOT HANDLED
- Исправление в случае, когда возможен вход в Windows 10 или доступен экран входа в систему
- Что делать, если синий экран появляется до появления входа в систему
- Ошибка появляется через некоторое время после чистой установки системы
Причины ошибки KMODE EXCEPTION NOT HANDLED
Самая частая причина появления синего экрана KMODE EXCEPTION NOT HANDLED в Windows 10 — сбои драйверов. Но, здесь есть очень важный нюанс: часто речь идёт не о драйвере какого-то физического устройства, а о драйверах, устанавливаемых сторонними программами для своей работы. Среди таких программ можно выделить:
- Антивирусы, средства автоматической очистки системы, файрволлы, средства VPN и прокси.
- Некоторое ПО, модифицирующее систему.
- Программы, устанавливающие драйверы виртуальных устройств (приводов, сетевых адаптеров для раздачи Wi-Fi и подобные).
- Средства криптографии.
Не обязательно дело в них: причина вполне может крыться и в драйвере реального физического устройства, но стоит помнить и о такой возможности.
Ещё одна возможность — какие-либо проблемы с оборудованием, не обязательно его неисправность. К примеру, плохо подключив жесткий диск или SSD (или подключив его неисправным кабелем), также можно получить рассматриваемую ошибку. Поэтому, если вы что-то делали с оборудованием компьютера (или перевозили его с место на место, что тоже иногда ведет к проблемам из-за тряски), учитывайте этот момент.
И ещё одна важная деталь: если синий экран KMODE EXCEPTION NOT HANDLED указывает на какой-либо файл .sys (в скобках после кода ошибки), обязательно попробуйте найти в Интернете, что это за файл и к какому драйверу или программе он относится (поиск на английском обычно более результативен), возможно это даст необходимую информацию о том, что именно вызывает проблему.
Исправление ошибки в случае, когда Windows 10 запускается или отображается экран входа в систему
Внимание: если ошибка появляется после завершения работы Windows 10 и последующего включения компьютера или ноутбука, но не появляется после перезагрузки, попробуйте отключить быстрый запуск Windows 10.
Относительно простой случай — появление ошибки уже после входа в Windows 10 или хотя бы доступность экрана входа в систему, с которого мы тоже можем выполнить некоторые действия. В этой ситуации рекомендую использовать следующие шаги:
- До очередного появления синего экрана перезагрузите компьютер или ноутбук в безопасном режиме. Если система загружается, для этого вы можете нажать клавиши Win+R, ввести msconfig и нажать Enter, после этого на вкладке «Загрузка» включить безопасный режим, сохранить параметры и выполнить перезагрузку. Если вам доступен только экран блокировки, нажмите по изображенной справа внизу кнопке питания, затем, удерживая Shift, нажмите «Перезагрузка». На синем экране перейдите в «Поиск и устранение неисправностей» — «Параметры загрузки», а в параметрах загрузки нажмите клавишу 4 для входа в безопасный режим. Подробнее: Как зайти в безопасный режим Windows 10.
- Если непосредственно перед появлением проблемы вы обновляли какие-то драйверы, откатите их в диспетчере устройств, удалите, или установите другой драйвер в безопасном режиме.
- Если вам известно, какая программа вызвала сбой, удалите её в безопасном режиме (лучше всего через Панель управления — Программы и компоненты).
- Если вам неизвестно, что вызывает сбой, но синий экран появляется через некоторое время после появления рабочего стола: попробуйте убрать все программы (особенно установленные в последнее время) из автозагрузки. Как это сделать: Автозагрузка в Windows 10 — как убрать программы или добавить их.
- Если недавно проблема не появлялась, а что-либо на компьютере не устанавливалось, попробуйте использовать точки восстановления (Панель управления — Восстановление). Подробнее: Точки восстановления Windows 10.
- Если имя сбойного файла .sys не отображается на экране с ошибкой, попробуйте использовать программу BlueScreenView, доступную на сайте https://www.nirsoft.net/utils/blue_screen_view.html. Она может показать подробную информацию о том, что вызвало (какой файл) ошибку. Например, для написания этой статьи я использовал старую программу Lock Folder, так как точно знал, что драйвер из неё может вызвать указанный синий экран в Windows Синий экран я получил (но с другим кодом) и в BlueScreenView видно, что виноват файл lf40fs64.sys — как раз от этой программы.
Если синий экран KMODE EXCEPTION NOT HANDLED появляется до входа в систему
Случай, когда сбой происходит до входа в систему сложнее, но проблему иногда можно решить, не прибегая к переустановке системы:
- Вам потребуется загрузочная флешка Windows 10 в той же разрядности, которая установлена на вашем компьютере или ноутбуке. Сделать её можно и на другом устройстве. Флешку UEFI можно записать даже на телефоне Android.
- Загрузите проблемный компьютер с этой флешки, выберите язык на первом экране, а затем нажмите «Восстановление системы» слева внизу на следующем экране и выберите «Поиск и устранение неисправностей».
- Далее вы можете попробовать использовать точки восстановления системы или удалить последние обновления Windows 10.
- Запустив командную строку в средствах восстановления, вы можете включить безопасный режим для системы, уже установленной на компьютере, используя команду
bcdedit /set {default} safeboot minimalс последующей перезагрузкой компьютера уже с основного HDD или SSD.
Ошибка появляется через некоторое время после чистой установки системы
Если ошибка KMODE EXCEPTION NOT HANDLED появляется всегда через какое-то время после установки/переустановки Windows 10, возможно, причина в том, что система сама загружает драйверы для оборудования и какие-то из них работают неправильно в вашей системе.
Возможное решение для такой ситуации: заранее разместить скачанные вручную драйверы оборудования с официальных сайтов производителя материнской платы ПК или ноутбука, произвести установку без подключения к Интернету, а затем вручную установить заранее подготовленные драйверы. При желании также можно отключить автоматическое обновление драйверов в Windows 10.
В случае, если всё ещё нужна помощь, постарайтесь подробно описать в комментариях все детали, которые вам известны о появлении ошибки на вашем компьютере: после чего стал появляться синий экран, в какие именно моменты он появляется и любые дополнительные детали. Возможно, решение найдётся.
With help of our Server Management Services support team have created a simple solution article for Windows error kmode exception not handled at Bobcares.
Fix Windows error kmode exception not handled
Kmode Exception Not Handled is a system crash. This crash happens when a Kernel Mode Program is causing an exception. Where the error handler is not able to identify. Generally, there will be an error code 0x0000001E, and sometimes the system falls into a looping reboot.
To fix Kmode Exception Not Handled error effectively, you can try the below ways:
1. Turn off fast startup
2. Run Windows Memory Diagnostics
3. Update device drivers
Method one: Turn off fast startup
Windows fast startup feature, which users can set for their own startup preferences. It’s available for Windows 8 and Windows 10 systems and works similarly to the hybrid sleep mode of the previous Windows versions. By saving the operating system state to a hibernation file, the fast startup can make your computer boot up even quicker.
However, the fast startup can also cause a system crash when there is trouble reloading the kernel, drivers, and system state normally. Few a times BSOD error occurs, similar to the Kmode Exception Not Handled error. Then you may have to turn off fast startup for normal boot.
1. Press on Win + R and input “Control panel”. Then hit Enter.
2. Search for Power Options.
3. Click on Choose what the power buttons do.
4. Next click “Change settings that are currently unavailable”.
5. uncheck the choice “Turn on fast startup”. Then Click Save changes and exit.
After the settings changes done. You can restart your system and check if the Kmode Exception Not Handled error has been repaired.
Method two: Run Windows Memory Diagnostics
Windows Memory Diagnostic is a system memory test. This help to check the system’s RAM for problems. During the test process, there might get a status bar showing if any problems have been detected. Also, Windows Memory Diagnostics helps to check the kmode exception not handled error.
1. Open Windows memory diagnostics by searching from the search box of Windows 10.
2. Click on “Restart now and check for problems”.
Repair the problems that detected and restart Windows.
Method three: Update device drivers
If kmode exception not handled error is caused by the outdated device driver. Then you can select to update the driver manually in Device Manager or automatically update with a driver updater.
Update driver in Device Manager
1. Press Win + X key then select Device Manager.
2. Locate “other devices” and right-click update the driver.
3. Next, click on the “Search automatically for updated driver software” option and wait for the result.
Make sure that the driver must be compatible with the system.
Update the driver with a driver updater
Driver updater help to update the outdated drivers automatically. After updating the drivers, you can restart the system and recheck if the problems are gone.
[Looking for a solution to another query? We are just a click away.]
Conclusion
To conclude, you have checked on simple methods for resolving the Windows error kmode exception not handled. Including update driver in Device Manager and with a driver updater.
PREVENT YOUR SERVER FROM CRASHING!
Never again
lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server
24/7 so that it remains lightning fast and secure.
GET STARTED
Rick Akura
The KMODE_exception_not_handled blue screen error can occur for different reasons on your device. Here’s how to fix KMODE_exception_not_handled BSOD.
If you are experiencing the KMODE_EXCEPTION_NOT_HANDLED blue screen error on Windows, don’t worry, you are not alone. Various factors can cause this error, but there are several ways to fix it. In this blog post, we’ll discuss some of the most common causes of this error and how to fix them.
We will also provide a few tips for preventing the KMODE_EXCEPTION_NOT_HANDLED blue screen error from occurring in the future.
Read on to learn more!
Table of Contents
- What is the KMODE_EXCEPTION_NOT_HANDLED error in Windows?
- What causes the KMODE_EXCEPTION_NOT_HANDLED error?
- Solved: KMODE_EXCEPTION_NOT_HANDLED in Windows
- Method 1. Disable the Fast Startup feature
- Method 2. Clean boot your computer
- Method 3. Update your network drivers
- Method 4. Run the Windows Memory Diagnostics
- Method 5. Temporarily disable your antivirus app
- Method 6. Run the System File Checker
- Method 7. Update your BIOS
- Final thoughts
What is the KMODE_EXCEPTION_NOT_HANDLED error in Windows?
When you get a “blue screen” error on your computer, it can be an unpredictable and frustrating experience. It often occurs when something is wrong with one of the system files in Windows or another program that runs simultaneously that causes this issue.
Most blue screen errors are associated with system-related issues that send a STOP code to Windows, leading to an immediate system crash. This happens without warning, meaning work can be lost, and files can occasionally get corrupted. Make sure to save frequently!
But don’t worry! There’s always a solution to any blue screen error. You will want to check out these things before giving up hope:
- Make sure all system updates are installed;
- Repair any damaged configurable settings using built-in tools like the System File Checker and DISM;
- Update your drivers;
- Check your boot settings.
Windows users have reported many instances of a driver-related blue screen error, one of which is the “KMODE_EXCEPTION_NOT_HANDLED” error code, also known as stop code. Luckily, there are several potential solutions you can apply to get rid of it and return to using your computer as usual.
What causes the KMODE_EXCEPTION_NOT_HANDLED error?
The error message “KMODE EXCEPTION NOT HANDLED” does not appear to be particularly useful at first look. Even users with plenty of Windows experience may have trouble deciding on the next step when this stop code appears as Windows starts up. So, what does it mean?
When software or apps overwrite one other’s memory, the KMODE_EXCEPTION_NOT_HANDLED error occurs. It causes the software to crash and make your system crash with a Blue Screen of Death.
Solved: KMODE_EXCEPTION_NOT_HANDLED in Windows
It’s critical to address this Windows issue as soon as possible because it will almost certainly continue to occur until you resolve it! We’ve developed a list of seven viable options to assist you in quickly restoring your PC.
Method 1. Disable the Fast Startup feature
Fast startup is enabled by default on practically all Windows computers. The function helps your computer boot quicker or recover from hibernation more quickly, but it can also cause Windows to fail to launch correctly or revert to earlier faults.
-
Click on the Windows icon in your taskbar and search for the Control Panel. Launch the application from the search results.
-
Click on Power Options. If you can’t see this, make sure to switch the view mode to either Large icons or Small icons.
-
Click on the Choose what the power button does link in the left-side pane. You’ll be redirected to a new page.
-
Before making changes, you need to click on the “Change settings that are currently unavailable” link. This will unlock your options.
-
Make sure to uncheck the Turn on fast startup (recommended) option. Click the Save changes button to apply the changes before restarting your computer.
Method 2. Clean boot your computer
Start in “clean boot” mode to guarantee that your computer operates without third-party services. Before booting, this will remove any apps and third-party conflicts. Check whether Windows experiences the KMODE_EXCEPTION_NOT_HANDLED BSOD when in this boot mode.
- Press the Windows + R keys on your keyboard to bring up the Run utility in a new window.
-
Type in “msconfig” without the quotation marks and press the Enter key on your keyboard. This will launch the System Configuration window.
-
Switch over to the Services tab. Make sure that you check the Hide all Microsoft services box. This is going to ensure that you only see third-party services.
-
After hiding all system services, click the Disable all button to disable every third-party service on your device.
- Click the Apply button and restart your computer. When you boot next, your computer will only initiate essential Microsoft services.
- Restart your computer. You’ll be in a clean boot state with only official Microsoft services.
If you observe that the KMODE_EXCEPTION_NOT_HANDLED blue screen problem disappears after a clean boot, a service likely is to blame. You must locate it and either replace the linked driver or app or turn off the service entirely.
Method 3. Update your network drivers
Windows Update has a feature that allows you to update outdated drivers automatically. This can help you quickly find and get some of your drivers up-to-date without individually checking for new versions.
Use the steps below to update a network driver that may be outdated manually. Keep in mind that only legitimate sites should be used to download drivers! Some fraudulent websites may try to trick you into downloading malware-infected driver files.
-
Press the Windows + X keys on your keyboard and choose Device Manager from the context menu to access the needed utility.
-
Expand the Network adapters category and right-click on your current network adapter—select Update driver from the context menu.
- Choose how you want to update your driver. You may either let Windows find a driver for you automatically or manually seek a new driver file on your machine.
Method 4. Run the Windows Memory Diagnostics
The Windows Memory Diagnostic tool is a built-in Windows utility for locating and resolving system memory issues. It will test your RAM and notify you if any problems interfere with its operation.
-
Press the Windows + R keys on your keyboard to bring up the Run utility. Here, type in “mdsched.exe” and press the OK button.
-
Choose “Restart now and check for problems (recommended)” to instantly begin a memory scan. Make sure to save any files and close all open applications before clicking on this option.
- Alternatively, choose “Check for problems the next time I start my computer” and restart the device at a more convenient time.
- The Windows Memory Diagnostics Tool interface will then show up and automatically start testing your PC’s memory problems. The process may take a few minutes, so you should be patient and let it run till completion and display the test results.
If the Windows diagnostic tool finds and displays no faults, your PC’s memory is most likely in good condition and functioning as intended. If this is the case, use a different approach from this article to try to fix the KMODE_EXCEPTION_NOT_HANDLED BSOD error.
Method 5. Temporarily disable your antivirus app
Antivirus apps are a necessity on your computer if you want to stay safe while online. However, many of them cause errors, and some may even mess up your drivers. If this happens, you need to disable your antivirus temporarily.
- Right-click on space in your taskbar and choose Task Manager from the context menu.
- Switch to the Startup tab using the header menu located at the top of the window. Find your antivirus application from the list and select it by clicking on it once.
-
Click on the Disable button now visible in the bottom-right of the window. This will disable the application from launching when you start your device.
- Check whether you can use your computer after making this update by restarting it. Remember to restart your antivirus program subsequently, or purchase a new one if your present one was the source of the problem!
Method 6. Run the System File Checker
Corrupted system files can cause various issues on your computer, one of which happens to be blue screen errors and unnatural resource consumption. If some essential Windows files have been tampered with or damaged somehow, they need to be repaired.
Use the built-in System File Checker (SFC scan) to detect and replace any damaged system files you may have.
- Open the search bar in your taskbar by clicking on the magnifying glass icon. You can also bring it up with the Windows + S keyboard shortcut.
-
Type Command Prompt in the search box. When you see it in the results, right-click on it and choose Run as Administrator. If you’re using a local account that doesn’t have administrator permissions, click here first.
- When prompted by the User Account Control (UAC), click Yes to allow the app to launch with administrative permissions.
-
Type in the following command and press Enter to execute it: sfc /scannow
- Wait for the System File Checker to finish scanning your computer. In the case of a discrepancy, the utility will restore system files and fix all errors.
Method 7. Update your BIOS
The computer might not be working correctly because its BIOS has become outdated. You can fix this by updating your system’s software, which could also improve performance and stability issues related to older versions of the BIOS you’re using!
- Press the Windows + R keys on your keyboard. This is going to bring up the Run utility.
-
Type in “cmd” without the quotation marks and press the Enter key on your keyboard. This will launch the Command Prompt application.
-
Next, type the following commands one by one. Hit the Enter key after each command line to execute the command:
- systeminfo | findstr /I /c:bios
- wmic bios get manufacturer, smbiosbiosversion
- These commands will help you identify the BIOS version. Use it to find the latest files required to update your BIOS, unless you’re already on the latest version.
Final thoughts
We hope that this article was able to guide you in resolving the KMODE_EXCEPTION_NOT_HANDLED blue screen error message. Feel free to reach out to us and tell us how we did! If you have any more questions or require assistance, don’t hesitate to contact our team.
If any questions are left unanswered, or problems are not addressed, please feel free to reach out — our team of experts would love to help! In the meantime, keep up with all things tech by checking back for more troubleshooting articles and following us on social media.
Follow our Blog for more great articles like this one! In addition, you can check our Help Center for a wealth of information on how to troubleshoot various issues.
One more thing
Sign up for our newsletter and get early access to our blog posts, promotions, and discount codes. Thank you for reading! We hope to see you again soon.
Feel free to reach out with questions or requests you’d like us to cover.
A blue screen of death (BSOD) is an error which halts the operations of the PC, displays the error condition and forces your computer to restart after collecting diagnostic information. The error message “KMODE EXCEPTION NOT HANDLED” usually occurs when you are having driver issues.
It means some piece of external or internal hardware connected to your computer is causing a driver conflict which is forcing your PC to crash. In some cases, the error window contains the name of the driver which caused your computer to crash. In other cases, you have to manually diagnose which driver is causing the problem and disable/update it accordingly.
Solution 1: Disabling Fast Startup
One of the leading workarounds for this issue is disabling the Fast Startup on your computer. Fast Startup (also called fast boot) works similarly to the hybrid sleep modes of previous versions of windows. It combines the elements of a cold shutdown and the hibernate feature. When you shut down your computer, Windows logs off all users and closes all applications similar to the cold boot. At this point, Window’s state is similar to when it is freshly booted up (as all users are logged off and applications are closed). However, the system session is running and the kernel is already loaded up.
Then Windows sends a notification to device drivers to prepare for hibernation and saves the current system state to hibernation and turns off the computer. When you restart the computer, Windows doesn’t have to reload the kernel, system state or the drivers. It just refreshes your RAM with the loaded image in the hibernation file and navigates you to the startup screen. As we can see, Fast Startup involves all driver modules of your computer and if they are not working properly, may cause them to crash.
Note: This is a potential workaround. Workarounds are different from fixes where they offer a way around the problem. They do not fix the problem completely.
- Press Windows + R to launch the Run application. In the dialogue box type “control panel” and hit Enter. This will launch your computer’s control panel.
- Once in the control panel, select Large icons and click on Power Options.
- Once in the Power Options, click on “Choose what the power buttons do” present at the left side of the screen.
- Now you will see an option which requires administrative privileges named as “Change Settings that are currently unavailable”. Click it.
- Now head to the bottom of the screen and uncheck the box which says “Turn on fast startup”. Save changes and exit.
- You might need to restart your computer. Check if the problem at hand got fixed.
Solution 2: Diagnosing the Faulty Driver
If the first workaround didn’t work for you, you have to manually check each driver present on your computer and see what is causing the BSOD. The problem due to which KMODE EXCEPTION NOT HANDLED occurs may be different computer to computer; this is why we are listing down a generic solution in which you have to diagnose manually what is causing the error message.
There can be two ways due to which the error message occurs; either the problem may reside in services of some module or it may directly be linked to the driver of the device. We will cover both potential solutions starting with drivers.
- Press Windows + R, type “devmgmt.msc” in the dialogue box and press Enter to launch the device manager.
- Once in the device manager, right-click on the device and select Update driver. You have to follow this step for every device listed on your computer.
- There are two ways through which you can update your device drivers. Either you can automatically update the driver using the first option or if that doesn’t work out, you can update it manually. You should head over to the manufacturer’s website, download the latest drivers and install it accordingly using the second options. We recommend using the second option for all the device drivers.
If updating the drivers doesn’t work, you can try disabling the services one by one and see which service is causing the problem. First, boot your device in Safe mode with Networking. After booting, follow the steps mentioned below.
- Press Windows + R, type “msconfig” in the dialogue box and press Enter.
- Check the option Hide all Microsoft services from the dialogue box. Now disable each service one by one and continue using your computer in normal mode. If the BSOD occurs again, it means that the service you disabled wasn’t the correct one and you have to uncheck another service.
Note: Try disabling the services which are connected to some hardware on your computer. This way you will be able to diagnose more quickly and efficiently.
Kevin Arrows
Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.
Windows · December 16, 2023
Windows Server is a powerful and reliable operating system used by many businesses for their hosting needs. However, like any other system, it can encounter errors that can disrupt its operation. One such error is the 0x0000001E – KMODE_EXCEPTION_NOT_HANDLED error. This error can be frustrating, but with the right steps, it can be fixed.
Understanding the Error
The 0x0000001E – KMODE_EXCEPTION_NOT_HANDLED error is a Blue Screen of Death (BSOD) error that occurs when a kernel-mode program generates an exception that the error handler cannot catch. This error is usually caused by a faulty driver or hardware issue.
Steps to Fix the Error
Step 1: Update Drivers
Outdated or corrupt drivers are often the cause of this error. To fix this, you should update all your drivers to the latest version. You can do this manually by going to the manufacturer’s website and downloading the latest drivers or using a driver update tool.
Step 2: Run a Memory Test
Bad memory can also cause this error. To check if this is the case, you can run a memory test using the Windows Memory Diagnostic tool. To do this, type “memory” in the search box and select “Windows Memory Diagnostic.” Follow the prompts to run the test.
Step 3: Check for Hardware Issues
If updating drivers and running a memory test does not fix the error, you may have a hardware issue. Check all your hardware components to ensure they are properly connected and functioning correctly.
Step 4: Perform a System Restore
If the error started occurring after a recent change to your system, you could perform a system restore to revert your system to a previous state. To do this, type “system restore” in the search box and follow the prompts.
Step 5: Reinstall Windows
If all else fails, you may need to reinstall Windows. This will erase all your data, so make sure to back up your files before doing this.
Conclusion
The 0x0000001E – KMODE_EXCEPTION_NOT_HANDLED error can be a headache for VPS users, but with the right steps, it can be fixed. By updating drivers, running a memory test, checking for hardware issues, performing a system restore, or reinstalling Windows, you can get your USA VPS Hosting back up and running smoothly. Remember to always keep your system updated and regularly check for hardware issues to prevent this error from occurring in the future.