KMODE EXCEPTION NOT HANDLED

[wolfdd]

FYI, there is a new intelligence update to Window Defender. Trying it now on the machine that is still BSODing. My other machine is still working fine with all updates installed.

[Keiichi]

---

@malssid wrote:

I'm getting the same when using Blue screen view. All of the BSODs say caused by driver: ntoskrnl.exe

---

Yes, for sure it's the kernal that's causing the BSOD, but more curious about the address.  Do you have the same addresses after me or are they different?  

[malssid]

---

@Keiichi wrote:

---

@malssid wrote:

I'm getting the same when using Blue screen view. All of the BSODs say caused by driver: ntoskrnl.exe

---

Yes, for sure it's the kernal that's causing the BSOD, but more curious about the address.  Do you have the same addresses after me or are they different?  

---

For me

Address in stack: ntoskrnl.exe+25ad71

Caused by address: ntoskrnl.exe+1c2390

So same exact as yours!

[August_Fields]

> I get the feeling people who were using a different antivirus in April and early May didn't run into this error and so they aren't here now heh.

I don't think that's it. I had been using malwarebytes for about a year when this started for me last week. I never checked before to see if defender was turned off by it because I never had any problem. But when I ran the dumpanalyzer after my first blue screen all it said that I could understand was the faulting program was msmpeng.exe. Now, wether this was caused by defender itself, or some kind of cross talk between the defender structure in place and my AV , or just some element of windows defender I can't say. But judging from all I've read in this forum, defender or some  underlying or associated software structure (perhaps HP's software, maybe some driver?) seems to be trying to overwrite or access a protected memory location used by windows itself. But now with my system reverting to mcaffee after a factory reinstall, I've checked and only windows defender firewall services are actually running in services. Windows Defender itself is not running. Of course, without any acknowledgement from HP or Microsoft it's all just conjecture. Plus my system has only been up with virtually no added apps for a day or so, so given this problem's habit of reappearing days or weeks after we apply these fixes there's just no way to know when we will have a resolution without some kind of statement from some software folks. 

[PSchniz]

Update on the possible fix/workaround. The computer has begun blue screening again. So, the issue does extend beyond an active Windows Defender. The computer is allowing me to log on for a short time before the error occurs. In the past, it would just loop until it brought up the recovery menu. Time to take a few more stabs at a solution...

[malssid]

---

@PSchniz wrote:

Update on the possible fix/workaround. The computer has begun blue screening again. So, the issue does extend beyond an active Windows Defender. The computer is allowing me to log on for a short time before the error occurs. In the past, it would just loop until it brought up the recovery menu. Time to take a few more stabs at a solution...

---

Apparently there's was a security intelligence update today. I wonder if that fixes the issue?

[wolfdd]

Another update on the new Windows Defender update, after installing the problem computer still has NOT BSOD for about 15 minutes. Still waiting to see if it does it but this is the longest it has gone.

[GlassCurtain]

I'm curious if this is only an issue effecting HP's Intel chipsets. As a computer technician we've installed A LOT of HP desktops when swapping business over to Windows 10 and no one has had issues but the computers we installed all had Ryzen's in them. The computers that have this blue screen issue that have come into the shop all had Intel processors.

[malssid]

---

@wolfdd wrote:

Another update on the new Windows Defender update, after installing the problem computer still has NOT BSOD for about 15 minutes. Still waiting to see if it does it but this is the longest it has gone.

---

That's a good sign. 

https://www.microsoft.com/en-us/wdsi/definitions/antimalware-definition-release-notes

I think these are the release notes for that update. Maybe report back in 45 min and let us know if you get a BSOD? 

[wolfdd]

Sure thing. I know how frustrated everyone is with this and would love for this to be the problem solver. 20 minutes and still going strong!