My Omen's got #HPCovid-19 KMODE EXCEPTION NOT HANDLED

[Dave308]

Just finished resetting my brand new Omen Desktop (875-0060) for the 3rd time in 3 weeks after BSOD: KMODE EXCEPTION NOT HANDLED. When will HP sort this out? When the world finds a vaccine for Covid-19? I bought this PoS off the shelf because I needed a machine in a hurry to work from home and now I regret not building it myself. Something in the HP Bloatware is causing this issue, Microsoft is blaming McAfee, HP don't even acknowledge there is a problem, yet 25k people have viewed this thread: https://h30434.www3.hp.com/t5/Desktop-Operating-Systems-and-Recovery/KMODE-EXCEPTION-NOT-HANDLED/td-... and the posters there are putting their brilliant minds together to find the cause and hopefully a solution if the HP software permits. This is your job Hewlett Packard, get your act together!

Maybe we can get their attention #HPCovid-19 

[praveen196]

@Dave308 Welcome to HP Community!

As I Understand you want a fix for the error - kmode exception not handled in Windows,

Peace be unto you, I have a few steps that should help resolve this concern:

Causes of this Error:

• Cause 1: Faulty RAM module
•  Cause 2: Corrupt or outdated device drivers

Fixing “ Stop Code: kmode exception not handled” on Windows:

•   Fix #1: Test your RAM
•   Fix #2: Update or disable drivers
•   Fix #3: Disable antivirus
•   Fix #4: Check for new software

Description and Symptoms

The error messages, alerts, warnings, and symptoms below are tied to this error.

The error indicates that the system error handler couldn’t catch an exception generated by a kernel mode program. It’s mostly displayed as a Blue Screen Error (BSOD) or a STOP code. When this happens, the computer shuts down abruptly.

The error can be caused by one of the following situations:

• Hardware problems
• Incompatibility with device drivers
• Corrupt system services
• Recently installed software applications that might be incompatible with your Windows versions

Cause 1: Faulty RAM module

The most common cause of this error is a faulty RAM module that periodically gives read/write errors. If that’s the case, then it is advisable to scan the system memory and replace the faulty RAM module.
 

Cause 2: Corrupt or outdated device drivers

Sometimes the device drivers may become misconfigured, corrupt or outdated. That may also happen after a Windows update or a Windows downgrade from a newer system to an older one.

Here's a related HP Forums post that seems to have helped others: Click here

Keep us posted,

If you would like to thank us for our efforts to help you, 

Give us a virtual high-five by clicking the 'Thumbs Up' icon below, followed by clicking on the "Accept as solution" on this post, 

Have a great day!

[Dave308]

LOL, 10 days later a response, what a joke.

It was cause 2: **bleep** HP drivers.

Since installing "HP Software Component 4.1.4.3079" on 25th of May, it's fixed. 

I'm not accepting your solution, when in fact I'm telling you what the solution is. You should have known about this for at least 6 days before you even replied. Maybe you should talk to your driver team about solutions, not your consumers.

Never buying a HP again!