KMODE EXCEPTION NOT HANDLED

[das335]

I joined this forum so I could thank everyone who provided information for solving the dreaded BSOD bootloop problem.

Big thanks to Brainz01 and SaltyLager for their original instructions for how to update the registry to avoid the BSOD bootloop.

Also, thanks to Melinda00 for all her work in documenting the process.

I waited until today (5/29/2020) to try this process and it worked for me, with a few missteps on my part.

I followed the instructions and added the new keys and values OK.
I let Windows apply all available updates (2020-01 and 2020-05 Quality updates, and HP Software Component)
Everything was working fine so I attempted to get Windows defender working again.

I originally tried using regedit while in Windows.
I found the Real-Time Protection key and set the 3 dwords to 0.
I found an occurence of DisableAntiSpyware and it was already set to 0 so I thought I was OK.
When I restarted my PC, Windows Defender was still not available.

I went back to using the recovery method and ran regedit from the command prompt.
I did the procedure that involved the Load Hive, create "temp" key, and set the DisableAntiSpyware dword to 0.
I did the unload hive and exited regedit and shutdown my PC.

I started my PC and Windows Defender was now active again.

Thanks to everyone on this forum for all the help and information they provided.

[PhilItaly]

Hello,just a question: Did you already updated to Windows 10 2004?and if yes all works fine to you?

Greetings

[philip42h_2]

---

@PhilItaly wrote:

Hello,just a question: Did you already updated to Windows 10 2004?and if yes all works fine to you?

Greetings

---

You're the only person who has posted as having updated to version 2004 so far ...

For me, Windows Update notes that the "Windows 10 May 2020 Update is on its way. We’re offering this update to compatible devices, but your device isn’t quite ready for it. Once your device is ready, you’ll see the update available on this page." So I'm waiting until it's available ...

[Ferrumic]

@Philip42h_2

I wouldn't be in too much of a hurry to get 2004, as there are quite a few "issues"; though none are specifically HP machine-based. This is the current state of play :

https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-2004

MS are staggering the release of this (as I think they did previously, but not so effectively), so that their servers aren't overwhelmed, and I think that's what's behind the message you're seeing.

I'm still holding on to hear how you and @Melinda00 get on with your systems after the updates and re-Defending before I do anything.

If your news is good, I may do some special "to keep" image backups, re-enable Updates through gpedit, bring forward my pause date of 20th June, and "bite the bullet".  I'm undecided whether to re-enable any part of Defender, either before or after updating, as I'm running Avast paid and Malwarebytes Premium, and Avast asserts itself in place of WD anyway.

I'm also less than impressed that another machine is getting odd, opaque and completely uninformative messages about WD not allowing something in Vivaldi, and I distrust it greatly; especially after this episode.

I look forward to an update from you here at some point.

[das335]

PhilItaly,

I'm running Windows 10 1903.

[PhilItaly]

i Updated Windows 10may 2020 version 2004 the may 28,to avoid eventually issues i saved on USB the previous version 1909,at moment looks like works,i just wanted to know if someone did the same thing already and if works well too.After all the troubles we had,never say never.I hope Microsoft fixed all the problems now,even if i continue to think there are always some incompatibility with HP software.

Greetings

[Dave308]

 Been running for 9 days now with updates and defender turned on. Crashed 3 Thursdays in a row and 3 Windows re-installs later now its Saturday and still going strong. Looks like I got a new driver version of HP Inc. - SoftwareComponent and a new Defender update or maybe it was the new 500Gb NVME SSD I installed or was it getting rid of Windows Home and installing Windows Enterprise. Who knows, HP have had no input, taken no responsibility and had a total disrespect to their Consumers.

HP it's time to explain the underlying cause, then maybe I can actually rely on this desktop to do my work.

What a waste of time and money this has been. Definitely the last time I buy a HP!

[PhilItaly]

I totally agree, it seems that we have to make attempts by ourselves, having no advice from HP

Greetings

[philip42h_2]

---

@Dave308 wrote:

 Been running for 9 days now with updates and defender turned on. Crashed 3 Thursdays in a row and 3 Windows re-installs later now its Saturday and still going strong. ...

---

Dave,

Take a look in Task Scheduler to see what runs on a Thursday ... on my PC, under Task Scheduler Library > Hewlett-Packard > HP Support Assistant, there's a WarrantyChecker_DeviceScan that runs at 11:19 every Thursday of every week ...

It may be pure coincidence but we are looking for some regular / scheduled task that provokes the error. I survived last Thursday and am hopeful that the Defender updates have put an end to this nightmare.

[zdroidapk]

Hello All!

have facing the same issue.

can i know that Is your machine running is OK still?

Thanks.