KMODE EXCEPTION NOT HANDLED

[philip42h_2]

---

@August_Fields wrote:

The switched drive issue happened with me during one of my reinstalls. The troubleshooting recovery environment showed the d drive instead of the c drive. I wonder what's up with that to add to all this mess?

---

and yes ... Is this a part of the same issue? Or an entirely different issue meaning that we can never rely on the Windows recovery mechanism? [And is it even really happening or am I / are we just getting confused!]

[August_Fields]

I can't help with the list of things to try as my system has only been running for 24 hours since my last reload and sometimes it takes days before it does it again. I've tried many different things. Right now I have all the recent updates from HP and Windows installed, but most of windows defender is not running because mcaffee, which was bundled in my original config  and reloaded when this started is currently running. There is a periodic application error from source SecurityCenter in my system log that says: Security Center failed to validate caller with error DC040780. I don't know if that originates with mcaffee or windows defender because the, well I don't know enough about the details that show in the system log to be able to tell. Or even if that's significant, but it does say error and not warning anyways.

I will say that this doesn't appear to be a hardware issue because I've run all the diagnostics available through HP and windows and the hardware passes all the tests. When it started I also unseated and reseated my ram and after the second bout I also reseated my graphics card. Also, if it was a hardware issue, wouldn't the system get an error BEFORE it gets to the sign on screen? On my system, it would get all the way to the sign on screen and then immediately blue screen again.

[alexgogan]

That Error DC040780 is Windows Defender clashing with your AV  and its been around for a very long time. 

[Ferrumic]

@August_Fields

I ran all the Memtest and Windows Memory tests when this first occurred on my system, and before this thread got going big-time, to rule out hardware problems. I think it''s reasonable to assume that the numerous people who've got this problem haven't all suffered hardware failures at about the same time, and on different spec machines. I'd rule out hardware failure as a cause.

[DHCCLLC]

Only thing to do is to disable Windows 10 updates completely. goto www.greatis.com & download Stopudpates10 utility. It will COMPLETELY disable Windows 10 updates. You can also PAUSE updates indefinitely as well.

[GlassCurtain]

I work at a computer shop and we've seen 3 HP's at 2 different business have this issue. We've tried everything (chkdsk, offboot sfc, system restores, etc..). I eventually installed a new hard drive and reinstalled windows to see if I could recreate the issue. I installed all updates including 1909 and the updates after. It had no issues. The customer used it for about a week and this morning it starts blue screening. This registry work around was the only thing that would work. I also installed another AV just in case a windows update decides to enable windows defender again, at least it will see the other AV is default and will give control over to it.

That being said, I looked at the update history to see what updated today to cause this. The only thing that updated today was "HP SoftwareComponent - 4.1.4.3079". A quick search doesn't really give me any specifics as to what this is related to.

Again, Thanks for the work around SaltyLager and RJWard!

[Zandian]

After a reset I tried installing all the windows drivers and kept defender enabled. I didn’t install the two Realtek Bluetooth drivers under the HP Assistant and things seem stable so far. I was getting BSOD loops before that. 

I put off the Realtek driver installs for a month.

Time will tell.

Z

[cbrsmurf]

Just wanted to say same issue for me. 

initally thought it was a gfx issue but after disabling that it did not work. Reinstalled windows a few days ago which seemed to fix the issue but bsod started occurring again yesterday. 

[tim614]

It's absolutely wild that HP hasn't said anything officially on this. Imagine the non-tech savvy user that has automatic updates enabled, as is recommended, and gets one that effectively bricks their machine with a BSOD boot loop.

[Spaniard80]

I have been having the same issue with my Omen desktop lately. The computer was running fine without issues up until early May when I happened to be checking to see when my warranty expired in HP's Support Assistant and whether it was possible to extend it. While I was there, I noticed there were a few HP-specific updates and drivers that were ready for installation, so I installed them. One of those updates was a BIOS update. Installing them seems to have been a huge mistake.

Ever since then, I've been getting increasingly frequent BSODs always with the KMODE exception pointing to the Windows NT Kernel.exe (or something to that effect). At first it was just once or twice a day at some random event (like watching a video online), but yesterday it happened back-to-back prompting me to try to trouble-fix it a little bit. And that is where I started to get very frustrated because without fail I'd get another BSOD before I could implement any of the suggested solutions (e.g. turning off fast start-up, starting in safe mode with networking to install missing drivers). At some point I tried a system restore (I remember when the HP updates started they specifically indicated on screen that it was creating a restore point), but then I received a message that there were no restore points available.

While it was still somewhat stable I tried the HP Virtual Assistant which suggested I try to run some internal hardware tests. I let those run for about 6 hours and it came back clean. As soon as the tests finished and it tried to start Windows, it crashed again with the same BSOD. Next time it started, the PC couldn't even get off the Windows starting screen without another BSOD. I have every reason to believe that if I hadn't hard powered down the PC that it would have continued crashing, but it was too late to try anything else.

I hope that there's a solution to this issue that doesn't involve resetting my PC and losing all my data, but it seems like I don't have many alternatives at this point.