-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Desktops
- Desktop Operating Systems and Recovery
- Re: KMODE EXCEPTION NOT HANDLED
Create an account on the HP Community to personalize your profile and ask a question
05-20-2020 04:01 PM - edited 05-20-2020 04:02 PM
We need HP/Microsoft to address this issue. It isn't fair that we all have to troubleshoot it ourselves when people can't WORK because their computer keeps restarting with a blue screen. I understand that things like this can take a while to fix but it has easily been 2 weeks since it started for me.
I have already disabled windows defender in the settings (not registry) and uninstalled HP's support assistant software. Right now I am waiting for an actual solution instead of messing anything up more or pointlessly resetting my entire computer.
05-20-2020 04:04 PM
@malssid wrote:We need HP/Microsoft to address this issue. It isn't fair that we all have to troubleshoot it ourselves when people can't WORK because their computer keeps restarting with a blue screen. I understand that things like this can take a while to fix but it has easily been 2 weeks since it started for me.
Besides continuing to post updates here, best thing is to post on social media with a link to this thread.
I've tried contacting them via Twitter and Facebook, but have yet to hear anything back. I'm almost at the point where I want to start responding to every single post they make, until they directly acknowledge that they have received the message and that they are working on it.....
05-20-2020 04:04 PM - edited 05-20-2020 04:07 PM
Finally getting around to messing with fixing my computer. Going to try postponing updates.
I wouldn't put too much hope in KB4497165. I'm not the most well versed with hardware but for my HP OMEN the processor isn't listed (i7-9700. The i7-9700K is listed)
Seems like more of a coincidence. I hope I'm wrong though
05-20-2020 04:05 PM
I’m a full time computer technician and lots of my clients having been contacting me about this issue. However I don’t have easy access to one of my client’s computers to test the following. For anyone that has disabled Windows Defender, can you re-enable it and run it in sandbox mode to see if that is a possible workaround? https://www.howtogeek.com/fyi/windows-defender-now-offers-ultra-secure-sandbox-mode-heres-how-to-tur...
05-20-2020 04:10 PM
Just a suggestion: I would try to backup to the earliest restore point and just "pause updates for 7 days".
That's at least what I'm doing until it states that the next update will fix this blue screen. I worry that updating to KB4497165 might bring back the loop that I had yesterday. Right now it's not as bad.
05-20-2020 04:21 PM
Sounds like the update probably isn't the solution, unless individual machines are reacting differently I guess.
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.
And yeah, I'd recommend however can do it, have Defender disabled...with other antivirus etc.
I guess when I did my reset the McAfee asserted itself eventually.
05-20-2020 04:25 PM
@malssid wrote:I'm with you on this. I am going to keep bugging them on social media about it until it's fixed. Blue screening is a SERIOUS issue especially when most people now are working from home on their computers.
I am in complete agreement. I tried starting a support case this morning through the chat function in the HP Support app and gave them my phone number "in case of disconnection." The chat was disconnected and now I see that they have closed the case that was started as a result of that chat! So I then messaged them on Facebook (using the link from the website) and received an automated message that stated the following: " Thank you for messaging HP. We are here to help you. To help us answer your question, please provide details such as product info and issue. We typically respond in less than 2 hours. Our business hours are 8 a.m. – 6 p.m. EST."
That was at 10:25am EST and I did not receive so much as an acknowledgement. It is now 6:24pm EST.
Anyone have a good idea for a hashtag? #HPBlueScreens ??
05-20-2020 04:31 PM
For those of you who are more technically inclined, have you used Blue Screen View to look at your dump files?
https://www.nirsoft.net/utils/blue_screen_view.html
I noticed with my looping BSOD and the Windows Defender GUI BSOD, I get the same consistent:
"Address in Stack" : ntoskrnl.exe+25ad71
"Caused By Address": ntoskrnl.exe+1c2390