KMODE EXCEPTION NOT HANDLED

[Oneiroi]

I had the same issue and had no available restore point available anymore. The regedit procedure worked and saved me.

Thank you so much for taking the time to put all the steps.

I'll keep watching for a permanent solution.

[bibsout]

My affected PC is also an AMD chipset (Ryzen 7) so the Intel update is not the answer.

[Jim32161]

Yesterday, I rolled back to May 18th and from there things seemed to be okay. Tonight, out of the blue three BSODs, so far. Windows Updates were paused, no third-party antivirus software, nothing new at all.

I'm not confident in my computer savvy to attempt registry edits. Any other options?

[wolfdd]

So the other machine that has been working is now getting the BSOD, while the machine that had the BSOD is still working fine... This makes no sense...

[Emma1011]

I wrote a furious tweet that mentioned HP, microsoft and all tech/consumer media I could think of. To humiliate HP I even mentioned Dell! Hope it's of any use! 😛

Things went even worse for me today. Even after resetting my system, the BSOD just showed up 10 sec after loading the login screen. Tried to roll back to the recovery point I set up a few days ago, and it was blocked by an error from Dropbox (which was raised 1.5 years ago and still not solved, I'm sure this week I don't have the best luck). I tried for an entire day to do a fresh install but to no avail. Now I ordered a win 10 installation CD from ebay and am back to using my old Macbookpro until this whole mess gets sorted out.

[maripanya]

Hi, I have the  HP Omen Obelisk Desktop 875-0034.

I was in a BSOD loop with the KMODE error unable to even access Windows, even with safe mode. I tried doing a system restore recovery too, but it ended up with an error. I did a fresh install and kept my files, still had the same problem. Then I did a fresh install, also wiping my files, and I've had no problems.

I did some steps (that I determined from research) for good measure to prevent the BSOD loop from happening again.

 I immediately disabled Windows Defender and then Tamper Protection, too. I immediately searched to uninstall updates KB4556799 and KB4497165. I also disabled sleep, hibernation, and fast boot.

We'll see how it is tomorrow. I will update.

[btschuster]

FWIW, I decided to test the theory that the latest Defender Update fixed this. I have Security Intelligence version 1.315.1096.0 that installed this evening. In an attempt to test this and being either brave or stupid I went to Windows Security settings and attempted to turn off realtime protection. Instant system crash with KMODE error.

[ParalleloSam]

Adding my story to the list. Kmode BSODs started at the first of the month for me on an HP Omen intel i9 and 2080 super desktop purchased last month. First time it happened, I opened a case with HP but they blamed it on me and didn’t want to even do anything other than telling me to reinstall Windows. Reinstalled Windows for a third time tonight as it’s been the BSOD boot loop for me all three times but it also somehow deletes my boot records so a reinstall is all I can do. I tried all night the first time trying to rebuild my boot files various ways with no luck. Start up repairs, feature and quality roll backs, restore points, nothing works other than a full reinstall of Windows for me. Tonight I left the McAfee software installed so it leaves Windows Defender disabled as that seems to be something that works after reading this thread. Last Friday was the second time it happened so I guess I’ll know within a week if this worked or not. This is the first PC I haven’t built myself, mostly because I got a great deal on this and it would have been more expensive if I bought the parts. Kind of regret it now as I haven’t ever had these kinds of problem with a desktop before. Hopefully this is resolved soon. Currently I’m using the built in file history feature to backup files every 20 minutes to a second 1TB M2 drive I installed a few days ago because of this issue. 

[Bruceo1]

HP Omen Obelisk Bootlooping with Kmode. Could not access the system in safe mode and recovery restore options would not work. So I reinstalled with Win 10 USB recovery media. After all updates appeared to be installed and got all my programs reinstalled it worked for about half a day then got the Kmode again and bootloop. Same exact issue none of the recovery techniques worked.

Disabling Windows defender using recovery command prompt regedit with SmurfKongs instructions got me right back in. What a major CF this is....

[ALL-N-1]

I have an Omen too with the exact problem. Can you please share the command you used to disable windows defender in the recovery  command prompt?  Also, what directory does it put you in when you enter the recovery command prompt? It sends me to X:\windows\system32 and won’t recognize some of the commands like “sc” when I try disabling defender there. Thanks for the help. This is a crazy mess.