Windows 10: What's causing kmode exception not found

Hi all, I am trying to figure out what is causing Kmode exception not handled errors with my computer. To add a little detail, I just bought a new computer, which uses a gigabyte H470 mobo with 10th gen core I7 processor. I work from home, and my job requires me to use Cisco Anyconnect VPN to connect to their remote desktop. Lastly, I am totally blind, so I use a screen reader called Jaws to interact with the computer. From what I've found, antivirus software can cause this, so I've uninstalled AVG Internet Security. I don't want to leave my computer in this state, although I do have Malware B

:)

 

KMODE EXCEPTION NOT HANDLED

I had done essentially the same thing with my PC, which is also a new HP computer, but this did not solve the problem. Here's more history:

I first started and setup the PC on 4/1/20, and disabled use of McAfee software. I did not have any problems with the machine until 5/8/20, when it started having Kmode exceptions which became so frequent that Windows said I had to reset the PC's Windows
installation. I tried a partial reset that kept my data files, but the PC still had the Kmode exceptions, so I did a complete reset of the PC on 5/8/20. I again removed McAfee software, and continued using the PC. The PC ran without problems until 5/18/20,
when it starting having Kmode exceptions again. The Kmode exceptions again became so frequent that Windows said I needed to reset the PC.

So, I reset the PC on 5/19/20 and again removed McAfee software from the control panel. I discovered that I could cause the Kmode exceptions to happen at will, just by trying to perform a Windows system update, after Windows had installed all the above updates
that I described in my initial post yesterday.

I think others may have the same problem. You can easily test it, by trying to perform a Windows system update using the following menus and selections:

control panel

system and security

security and maintenance

maintenance

start maintenance

I suspect that after Windows installs KB4052623, it then has a problem trying to install KB2267602 that causes a Kmode exception. This might happen for other PC's, whenever they get to a point in their update cycle that causes them to try these updates.
The latest version of KB4052623 was released on 4/30/20, about a week before my PC started having Kmode exception crashes.

Phil

 

Windows 10 - BSOD: KMODE EXCEPTION NOT HANDLED (cng.sys)

Hi,

We suggest that you try the workaround suggested on DonchakVS's reply on August 5, 2015 and check if it resolves the issue:

Windows 10 - BSOD: KMODE EXCEPTION NOT HANDLED (cng.sys).

 

KMODE EXCEPTION NOT HANDLED

Earlier today I spent about 90 minutes on the phone with a Microsoft Technical Support person named Krishna. He was very patient and helpful, and was able to see the Windows history on my PC showing that it had failed to install KB2267602. He checked and
found that KB2267602 is no longer available from Microsoft - apparently Microsoft has realized KB2267602 doesn't install correctly, and removed it. He wanted to perform more tests, but my PC started having Kmode exceptions about as fast as I could logon to
Windows after each restart -- apparently it was trying to automatically perform system maintenance and load KB2267602 each time it restarted.

Using my other, older PC, he downloaded a new copy of Windows 10 to a USB drive for me. I then did a fresh install of Windows 10 to the new PC, and so far it has run fine. I can now perform system maintenance and install Windows updates, without Kmode exceptions,
although the updates installed so far only date to January 2020. Hopefully, the PC won't later run into problems installing more current updates. Maybe my new PC will now run reliably for the next several years, like my older PC. (Knock on wood.)

My suggestion for people currently having Kmode exceptions is to call Microsoft technical support at 1-877-696-7786 and ask them to see if your PC failed to install KB2267602, which may have caused a Kmode exception, and ask for help installing a new copy
of Windows 10. It helps to be as friendly and patient as possible during the phone call.

I agree that Microsoft should take the initiative to stop the Blue Screen errors, and suggested this to Krishna. Of course, he couldn't say when this larger problem might be fixed. Spamming Nadella might help, or the spam tweets might be ignored... Individual
conversations during phone calls may eventually have more effect.

Good Luck, everyone!

Phil