KMODE EXCEPTION NOT HANDLED

[bibsout]

I use a Microsoft account, didn't have any issues. Also, to anyone experiencing the "File in use" error when trying to do the Registry edit via command prompt, that means you are trying to load the file (when loading hive) from the wrong drive. Make sure you browse and choose the drive that your Windows OS is installed to. If you just stay in the default folder, it tries to load files from the currently running recovery platform.

And is there ANYONE experiencing BSOD's after disabling Windows Defender?

[Jim32161]

I'd reported this issue to MS via their Microsoft Community a few days ago. Got a reply today:

---------------------------------

Apologies James for the delay. I just learned there is a known issue being reported by a number people on HP forums as well.

Please check for driver updates and if it doesn't help, wait for a fix. I appreciate your patience.

---------------------------------

Sigh......

[SlurmMcKenzie]

i am using local accounts

[FireBall90]

I have the same issue, KMODE Exception with OMEN Obelisk Desktop 875-0034. Windows 10 Pro.. Local user account, not cloud. System restored and leaving off and using my dell until HP/Microsoft finds a permanent solution.

[ParalleloSam]

In regard to the question asked about different drives. I have had the BSOD happen on the stock intel M.2 drive and also a brand new Silicon Power M.2 drive with way better specs than the intel. I don’t think it’s the drives. Could be board drivers HP or Intel loads, or it could just be HP software that Windows Defender is choking on, which I feel is the likely culprit at this point. It’s my opinion but it may have to do with HP software that relates to over clocking since we all seem to be having these issues on “gaming” PCs. You can find articles about that online and based on all the information it makes sense. It wouldn’t be the first time that legit software got caught up in a malware scanning app. I personally feel the issue lies within HP, not Microsoft based on the evidence and HP is basically waiting for Microsoft to roll back what could be a legitimate protection feature. 

[Ferrumic]

@Jim32161

As usual, not a lot of help. Without somebody at MS/HP determining the precise and exact cause of this, plus the solution, just poking around the system and trying to download odd drivers of whatever type or description, in the hope that the end-users might empirically stumble upon a solution, is a stupid idea.

First, given the total fiasco that this episode is, there is no guarantee that it might screw the system further. Indeed, I'd say the odds are in favour that it might. Secondly, whatever users may find, a proper solution has to be tested and promulgated by HP/MS, and this isn't likely to happen through a user finding one by chance. Thirdly, it may be that the solution varies according to machine model; although, given the consistency of the error and dire user experiences, I'd think this least possible.

[IcaroChacalPR]

One of my customers has HP ENVY Desktop - 795-0137cb and called like a week ago with the now insidious KMODE_EXCEPTION_NOT_HANDLED blue screen error. I went and did a clean setup of windows 10 v.1909. Updated the PC through Windows Update and installed the user programs and applications. All appeared to be stable but then boom…out of the blue sky the KMODE_EXCEPTION_NOT_HANDLED strikes again!! I searched the net and found that “it might” be a Network Adapter Driver Problem. So, went to the Device Manager and did a Driver Update of the Network Adapter. So far so good, the system is holding stable, but I must wait and see if it maintains. It is worth noting that I have few other customers that are having the same error and with the same model of HP PC. So, this is getting very frustrating!! HP, please HELP !!

[IcaroChacalPR]

I have the same problem and did the BIOS update. It did hold stable for about 3 days and then it started with the KMODE error again!! I searched the net and found that “it might” be a Network Adapter Driver Problem. So, went to the Device Manager and did a Driver Update of the Network Adapter. So far so good, the system is holding stable, but I must wait and see if it maintains. It is worth noting that I have few other customers that are having the same error and with the same model of HP PC. So, this is getting very frustrating!! HP, please HELP !!

[PC775]

---

@fcorral wrote:

...Curious if others are logging in with MS accounts or just using a local account. 

---

A large majority of the computers I setup and are affected are local account, no password. However one still waiting for a fix is using a MS account, but the computer doesn't make it to login screen. It only boots to Recovery screen even after doing System Restore back to May 3- a point which worked to get computer working before. I haven't had a chance to go over and disable Defender via the registry edit yet. 

All affected computers that have been reported to me (about a dozen so far) are HP Pavilion or ENVY with Intel processors.

I will be working with an affected system today that has no system restore points available, and report back what happened.

[zata]

Hello, I had been in this forum when there were only a few answers. I followed Philip42h_2's advice 
"OK, the advice I got from HP Support was to download Windows 10 from Microsoft, create USB installation
 media and perform a clean install from there. And that has worked, so far, in as much as I can now boot
 and even post from my desktop. So this is a clean install with no HP specific software updates. " 
Pause all updates until May 19. So I installed everything that windows update had, and paused again.
 On June 3 I will update again. I hope then everything is fixed. Do not install anything from HP
 that was not installed by windows update. My latest installations are: 
KB4552931, KB4537759, KB4556799. Realtek Net 2024.0.10.209, INTEL 30.100.1915.1, 
REALTEK USB 10.017763.31247, REALTEK Extension 4001.0.1.101, 
MICROSOFT DEFENDER KB2267602 (ver.1.315.997.0) MICROSOFT DEFENDER KB2267602 (ver.1.315.978.0), 
MICROSOFT ANTIMALW30. 
All this installed on the may 19, and the machine has not failed.
My PC is Intel i5-8400. Windows 10 Pro 1909 (ver. 18363.836). 
I write it in case it helps anyone. TRANSLATED WITH GOOGLE TRANSLATOR.