Some users installing or upgrading to Windows 10 experienced the theKMODE_EXCEPTION_NOT_HANDLED Blue Screen of Death (or commonly known as BSOD) error. This error can be due to different types of things, ranging from software to driver issues. When you experience this BSOD error while trying to install Windows 10, it will prompt you to restart your computer every single time you experience it. In most cases, you will also not be able to proceed with the Windows 10 set-up.
The “KMODE_EXCEPTION_NOT_HANDLED” error is normally caused by:
You won’t be able to successfully upgrade or set up Windows 10 if you continue to encounter this BSOD error. Note that this error will always prompt your computer to restart every time it happens, preventing you from completing the Windows 10 set-up.
If you’re not tech-savvy or not capable of debugging this issue, it’s highly advisable to proceed with the basic troubleshooting techniques available in this link.
After troubleshooting, below you’ll find a few solutions to rectify the issue.
Two common causes of the KMODE_EXCEPTION_NOT_HANDLED issue are hardware incompatibility and faulty device driver or system service.
If you experience this error, check first if any of your newly installed hardware is compatible with Windows 10. You can find the required hardware for Windows 10 from this link.
If all your hardware is compatible with Windows 10, you might need to check the device driver or system service. Review the bug check message. If any of the drivers you have is listed in the message, either disable or uninstall them before upgrading or setting up Windows 10.
You might also find it useful to check the System Log available in the Event Viewer for other error messages that can help you figure out the driver or device that’s causing the error. Running hardware diagnostics can also be useful.
Other troubleshooting steps include:
If you still experience the error after doing the methods above, you might want to try a powerful and trusted automated tool to fix the job.
Error code 0x80073afc deals with an antivirus program first built into Windows 8/8.1 This error occurs when Windows Defender, the built-in anti-virus software in Windows 8/8.1 and higher, does not start automatically and users attempt to manually start the program. During the initialization period of the program start-up, something goes wrong and users get a 0x80073afc Error message. The error message states there was a problem with the initialization of the program. Windows Defender provides protection of your computer and it is advised by the Microsoft Corporation that you ensure it starts up automatically on every start-up.
Users have found several manual repairs that have fixed the problem without needing to contact technicians for extra help. While the methods below should solve your problem easily, if this is the first time you have encountered the issue you may want to do a simple restart. This has fixed the problem for some users and is the easiest first troubleshooting move. If it doesn’t work move on to the methods listed below, which are easily completed without extra help.
Before trying any of these methods, please make sure that you are logged into a profile that is listed as the administrator of the computer of his administrative powers enabled. If this is not the case you will not be able to complete the following methods. Please log out and log back in on the administrator profile.
First, check to see if you have a third-party anti-virus program installed on your computer. Some users believe that the built-in Windows Defender program is not powerful enough to handle the safety of their computer so they usually download a third-party program. However, that program may have caused a conflict with Windows Defender and may not allow it to open. If you do have a third-party program installed, try uninstalling it then manually starting Windows Defender.
If method one does not work, you may be infected by malware or a virus that has tampered with the settings on your computer and will not allow Windows Defender to start automatically or manually.
First, open Run by holding the “Win” key and pressing the “R” key. Then type “Regedit”. The program will ask for permission to follow through with this action. Click on “Yes” and the Open Registry Editor will open.
Find the HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionImage File Execution Option and check to see if there are any files similar to MSASCui.exe or MpCmdRun.exe. If there are any file entries that resemble that, you will want to right-click on them before selecting the “Delete” option. If you do not see any entries that match, this is not the issue with your Windows Defender and you will want to try another method.
The Registry on your computer is very important. It helps tell your computer what programs are safe to run, what programs should be run, and what programs should not be run. If it is tampered with by a virus or Malware, multiple system operations can be affected.
However, if you did find similar file names, and you deleted them, try to start Windows Defender manually. If it does not work again, move on to the next method.
If the first two methods do not work for your issue, and you are still receiving error code 0x80073afc when attempting to start Windows Defender, this step should solve the problem if you have Restore Point installed on your computer, which you most likely do.
For this method, we will be restoring your computer to a previous Restore Point. First, just like in method two, hold the “Win” key and press the “R” key. This will open run. Next type “Rstrui.exe” and click “ok”. After some time, you will see System Restore Windows. Click “Next” and select the restore point that you would like to go back to. After your computer has restored to the point you selected, check to ensure that Windows Defender has started correctly.
If the above methods aren't able to rectify the issue, you might have to download and install a powerful automated tool to get the job done.
Error Code 35 is a typical Device Manager error. It indicates information missing to properly configure your device. Error code 35 is usually displayed in the following format:
“Your computer's system firmware does not include enough information to properly configure and use this device. To use this device, contact your computer manufacturer to obtain a firmware or BIOS update. Code 35”
The 2 common reasons for Device Manager error code 35 are:
No matter what the reason may be, it is advisable to resolve the problem immediately without any delay otherwise you will be unable to use your hardware device.
Below is the list of the most effective and easy to perform solutions to resolve error code 35 on your PC. These solutions do not require any technical knowledge or understanding. Simply follow the instructions to resolve this error code.
BIOS (Basic Input/Output System) is the embedded software on the computer’s motherboard.
Though not all PCs have the same BIOS manufacturer, but the steps for updating the BIOS are similar for all versions. Before you get started with the updating process, first identify your current BIOS version.
This will hopefully resolve the problem. However, if the error still persists then there is a possibility that the error code is related to outdated drivers. To resolve, try method 2.
Update drivers to repair error code 35 on your PC by simply downloading DriverFIX. This is a cutting-edge program deployed with an intelligent programming system.
It is compatible with all Windows versions.
It scans your PC for problematic drivers and updates them with the latest and compatible versions automatically and in a few seconds thereby repairing all Device Manager error codes including error code 35 generated due to outdated/corrupted drivers.
In addition to this, it updates all device drivers on a regular basis, so you don’t have to stress over and keep a track of what drivers on your PC need to be updated and when.
Click here to download DriverFIX to resolve Device Manager error code 35 today!
netsh int ip reset
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesDPSParametersStep 4: After that, look for the “Parameters” registry key and select Permissions. Step 5: Now select your account under Group or user names. Step 6: Next, make sure that the “Full Control” and “Read” boxes are both checked, and then click on the Apply and OK buttons to save the changes. Step 7: Afterwards, navigate to this registry key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlWDIConfig Step 8: From there, look for the Config key and right-click on it and select Permissions and then click on Add and type “NT Service/DPS in the box and click OK. Step 9: Now select “DPS” and check the Full control box, click OK and exit the Registry Editor. Step 10: Reboot your computer and check if the error is now fixed.
“We’re not sure what happened, but we’re unable to run this tool on your PC, Error code 0x80042405 – 0xA001A”The error 0x80042405 – 0xA001A occurs while creating a bootable USB installation drive. This is a common error faced by many users and it has something to do with the USB hardware. To get this issue fixed, here are some suggestions you could check out.
CHKDSK [volume [[path] filename]] [/F] [/V] [/R] [/X] [/C] [: size]]Note: In the command given above, “[/F]” will try to fix the system errors while “[/R]” will be the one to fix the bad sectors.