KMODE EXCEPTION NOT HANDLED

[SpedP]

Just a quick question for anyone who has/had this issue, does the newest Windows 10 update/patch resolve this issue and prevent it from occurring again? I recieve my PC from repair tomorrow and I was wondering if I should halt incoming updates or just go for the newest one when I get it back to prevent any further issues or if there's anything I can do to prevent it.

[melinda00]

Because I am not technically proficient with computers, I do not know if I correctly reactivated Windows Defender in the registry. But it appears to be running normally and I have had no system crashes in the past half hour since I made the following registry changes. Please let me know if I need to try anything else to replicate BSOD.  This is what I did to reactivate WD:

I went back into registry following the same instructions to disable Windows Defender.

I noticed my system drive is now E, instead of C which it was previously, in my recovery environment. This difference in drive letter may be because I reinstalled two hard drives back into my desktop which I had removed when the system first crashed and I was trying to eliminate possible culprits.

I set the following dwords to 0:

DisableAntiSpyware

DisableBehaviorMonitoring

DisableOnAccessProtection

DisableScanOnRealtimeEnable

The start dword under system was set to 3 even though I had previously changed it to 4.

I left the start dword with a value of 3 and rebooted.

No BSOD.

I opened Windows Defender Firewall with Advanced Security and it appears everything is on. However, the last virus scan shows a date of 5/17/20, so I do not know how often a scan should happen automatically, and it seems to me that if it were actually on, a scan should have run by now. I went ahead and ran a quick scan without issue.

I have no other antivirus software running.

If any of you see anything else I should try to replicate the original BSOD, let me know.

 

 

 

[melinda00]

I had the issue of BSOD boot loop and was unable to get into safe mode.  I made registry changes recommended in this thread to disable Windows Defender, successfully rebooted my computer, and ran all available Windows updates yesterday 5/28/20. Thankfully, I never had to reinstall Windows and all my files and software are intact!

I just restarted Windows Defender today and have not had any crashes in past hour. This does not mean that updates are "safe" yet. I am keeping my updates on, at this point, and will report back if I have any system crashes. If no crashes occur within the next week or so, I will also report back.

Hope that helps!

[philip42h_2]

I’ve being running for four days now with all updates applied and no errors so that is looking good but, equally, I should note that last time round I had BSOD on the eight day – make of that what you will.

I’m pretty sure that we don’t know what caused the issue and consequently can’t know whether or not it is resolved …

The evidence that we have points to a Windows Defender update released around end of April / beginning of May as a key contributor to the issue- this was evident from the mini dumps and/or the SaltyLager ‘escape’ from the BSOD boot loop. Microsoft has released new engine and security intelligence updates since then and those of us running with the latest updates appear to be stable.

On the other hand, that doesn’t explain why the issue appears to have been prevalent on HP machines. I suspect that it was some piece of HP software that didn’t play well with Defender – and a weakness in Defender that caused the crash. Personally, I suspect some versions of the TouchPoint Analytics software included with the HP Support Assistant. This software runs periodically – i.e. to it’s own schedule – and thus is a candidate for causing a crash independently of whatever the user is doing.

This used to be deployed as a standard program – visible and un-installable via Control Panel > Programs and Features. Older machines we have here have such versions and have not been affected in any way by the recent Windows updates

On my Envy, the HP Support Assistant is implemented as a Windows App and the TouchPoint Analytics software is presented as a driver. The version I currently have is described as HP Inc. - Software Component - 4.1.4.3079. There are various reports on the Web that “version 4.1.4.3079 was release by HP to resolve this issue” – I don’t believe this to be true for two reasons:

• The build date of this version is 29th April – i.e. before we started having these problems so before HP could have been aware of the issue.
• I received version 4.1.4.3079 via Windows Update (on 24/05/2020 when I re-enabled updates) and I’m pretty sure that I saw version in the Microsoft Update Catalog. I can no longer find it in the Catalog and rather suspect that Microsoft has pulled it.

HP Inc. - Software Component - 4.1.4.3079 may well be a part of the problem rather than a  part of the solution.

In short, I’m confused as to exactly what state we are in …

I’m looking forward (if that the correct term) to the June cumulative update in the hope that everything gets sorted then. Oh, and just to add to the potential confusion Windows 10 version 2004 is released today!  😉

[SpedP]

**bleep** it, my PC is put On Hold for service and now it's getting delayed. I've read stories of people who have been delayed for months or haven't recieved their products back at all. Does anybody have experience with sending a PC to a Service Center?

[taimea]

what make me mad about this the most is that replys from hp are still acting like they don't know about the problem going on. hp japan twitter seems to at lest admit there a problem but they say they are still looking in to it from a replay i saw from them to some guy. so who knows if there is a patch out that fixed this or we just get lucky if it dose. since im not a theck wiz i had given my pc to my friend since he pretty good with pc we had re-stalled windows and updated stuff and he got me out of the BS lock down. but since we didn't know about what going on all he did was update and reinstall windows so i guess ill be see if this update fixed anything for me.

[Ferrumic]

@Melinda00

Thanks for the update, which is very useful. It would be handy if you could let us know how you are faring with this in the course of the next few days, as it may provide some insight into whether it's fixed or not.

I'm still running without Defender (disabled in gpedit and regedit), but with other AV software, and I have Updates turned off until mid-June, so anything I can gather to work out whether to leap back in or not before then will be most welcome.

By the way, I'm very impressed with your approach to this, and with the details and methods you've described here . 

[PhilItaly]

Hello,i had the same issue with my HP Desktop Pavilion.Random Blue Screen started in May as most of people here.I noticed  AppCrash with software HP,specially the driver:Sysinfocap.exe,this is due to the softer HP assistant.

Now i deleted every HP software from my PC,and i have updated the new Win 10 version 2004 and at moment everything works!Finger crossing.I will reinstall HP assistant if they will find a fix and a solution for this issue very annoying.

Greetings

[PC775]

UPDATE: After fixing this issue on nearly a dozen modern HP computers between May 6 and May 26, I still stand by my post on Page 33 of this thread that a Windows Defender Antivirus update mid-last week ultimately fixed the problem.

[philip42h_2]

---

@PC775 wrote:

UPDATE: After fixing this issue on nearly a dozen modern HP computers between May 6 and May 26, I still stand by my post on Page 33 of this thread that a Windows Defender Antivirus update mid-last week ultimately fixed the problem.

---

I suspect (and hope) that you are correct ... 🤞

Reviewing you earlier post I also note that you also demonstrated that "HP SoftwareComponent 4.1.4.3079" does NOT resolve the issue by enjoying a BSOD shortly after installing it. 👍