KMODE EXCEPTION NOT HANDLED

[philip42h_2]

---

@Markic wrote:

How to check if my Pavilion 17 installed "Hp software component 4.1.4.3079".  Last week I get on WU some HP Drivers, but after installing and restarting to apply update, I get "Failed to install" error in WU. I try again, but update not showing. Check for Updates every day, but not getting hp software component 4.1.4.3079.

When I go to Device Manager I didn't see Software Components section or HP Device Health Service.

---

In simple terms, if you haven'r already got it, you probably don't want it! 🙂

Check Start > Settings > Update & Security > View Update History > Driver Updates

I have 4.1.4.3079 on my Envy - which had all sorts of problems

I don't have 4.1.4.3079 on my laptop which has never missed a beat

It all depends of which version of the HP Support Framework stuff you have running on your machine ...

[Markic]

Nothing in Update History. I have Pavilion 17 f001sm and experience BSOD with KMOD EXCEPTION NOT HANDLED error. 

[Ferrumic]

@Philip42h_2

I turned Windows Update (and the driver/other software setting) back on via gpedit, and promptly received KB4497165 and 4556799. The latter I had previously received 14/5 and then uninstalled, and the former is an Intel microcode update. That is the lot. There aren't any other HP type updates, either old or new, listed anywhere, either.

I still have Defender and its services and components OFF / Disabled, which may explain why the last Definition update was 18th May. Perhaps it doesn't deliver them if it is indeed OFF. This may also explain some problems with getting updates from Microsoft Store, which I don't like doing anyway.

It's by no means clear whether re-enabling all the Defender constituents could/might/will put me back where we started in this BSOD hell. It is anyway turned off by virtue of having Avast (and Malwarebytes) both running, and unless it interferes with other things because it's not running, I don't see any good reason to have WD going as well. I have Feature updates i.e. 2004 deferred for 365 days, and I expect that installing that in due course will reset and restart WD.

[Radio28]

Just wanted to jump into this thread again to say that my PC has worked well for half a month, after doing all the steps from this thread:
- Turning of Defender through regedit

- Paused any updates from Windows Update

- Paused any updates from HP
- Installed Avast (didn't install the McAfee which is included)
- Turned off the possibility for the PC to go to sleep. However, I just turned this on again, and no problems as of yet. 

I'm not ready to turning on defender and updates yet, as I feel I would like a official message from HP/Microsoft. Why don't HP bother to at least answer this thread with "We are looking at it"? It is the biggest thread in here at the moment. It's odd. 

[philip42h_2]

---

@Ferrumic wrote:

@Philip42h_2

I turned Windows Update (and the driver/other software setting) back on via gpedit, and promptly received KB4497165 and 4556799. The latter I had previously received 14/5 and then uninstalled, and the former is an Intel microcode update. That is the lot. There aren't any other HP type updates, either old or new, listed anywhere, either.

I still have Defender and its services and components OFF / Disabled, which may explain why the last Definition update was 18th May. Perhaps it doesn't deliver them if it is indeed OFF. This may also explain some problems with getting updates from Microsoft Store, which I don't like doing anyway.

It's by no means clear whether re-enabling all the Defender constituents could/might/will put me back where we started in this BSOD hell. It is anyway turned off by virtue of having Avast (and Malwarebytes) both running, and unless it interferes with other things because it's not running, I don't see any good reason to have WD going as well. I have Feature updates i.e. 2004 deferred for 365 days, and I expect that installing that in due course will reset and restart WD.

---

I'm now on day 15 with Windows Updates enabled, running Windows Defender, all HP Support tools and everything is as it should be. I've even got the PC built back up to the state it was (more or less) when this fiasco started at the beginning of May. So I'm increasing confident that the root cause of this issue was Windows Defender and this was resolved via updates applied to Defender during May. Cue BSOD any second ... 😉

If you have Defender disabled and an alternative AV installed I'm pretty confident that you won't see this particular error again - because you no longer have the original cause running. Equally you could safely switch back to Windows Defender if you wanted to. You absolutely do not want to try running two forms of real-time AV protection at the same time - that would be asking for trouble. (I believe that Defender pulls down its own updates if it is running - if you have it disabled it can't do that.)

Installing a Windows cumulative or feature update shouldn't cause a problem. I trust that Microsoft will respect your choice of an alternative AV solution and leave that as you have it - my trust could be misplaced! But reintroducing Defender at this stage shouldn't cause an issue.

The Microsoft Store does seem a little dodgy but I doubt that this is in any way related to our favourite BSOD issue. 🙂

[Ferrumic]

@Philip42h_2

Glad it's still going OK.

I seem to get plenty of protection from the AV/Firewall/etc. things I'm running, and sometimes a little too much; weblinks in Office documents, spreadsheets and databases were blocked on outgoing, and other things.

I'm still in two minds about WD, and it looks a bit of a "chicken and egg" quandary. If it's not running, and I'm not getting the updates, including the fixes for this, then I have to enable it to get them. If so, will it then BSOD before it "comes right" post-updates, or will it behave? It seems that it's OK for yourself and Melinda00, but can I be bothered (aka am I that daring)? Probably not.

On the Store thing, there is, as usual, a multitude of speculative reasons for update failures, lots of possible cures, but very little from the MS horse's mouth. I mentioned WD, as one posited cause is not having that running. Again, I'm not desperate for it.

This is a 16gb machine, and it could do with the same again. I spent a lot of time removing HP bloatware and MS stuff to get a bit more speed, but I suspect that, as happened with the Feature update last year, a lot of customisation of the giant MS ecosystem will disappear, and have to be redone.

The HP tools don't do very much on this machine (October 2018 purchase) and although HPSA tells me it has a V9 for me, every time I install it I get V8. Frankly, the whole HP setup is really not too brilliant. Whenever I go direct to the Drivers and Downloads HP website for this machine model and spec, there are a number of inconsistencies in what is being offered; some of which has nothing to do with this box. The downloading and installation via HPSA is very hit-and-miss, and often just hangs. Whether that has something to do with WD or other AVs is yet another question.

Anyway, so long as this keeps going! Thanks for the updates, and please let us know if anything else (preferably NOT exciting) happens.

[HowardF422]

Philip- you're my favorite author for the month of June 2020.  With 44 pages under this thread, I went through the replies and look for your (and a few others') response to this BSOD debacle.  Mine is a HP Pavilion Gaming PC purchased in February this year.  I know I didn't brick the thing playing games because I bought it for the higher end graphics card for CAD work not gaming.  Sent it back last week, and now it is sitting next to me still in the box.  I am afraid to use now, after the hell it put me through- all because of software bug?!

I have been using Windows 10 only for one whole month, 1 month.  I am typing this on my old Windows 7 desktop, my workhorse since 2013, which I was replacing with the new Pavilion due to fan issues.  Ironic how the Replaced returns to save my butt from angry clients due to a software bug.

-Howard

[philip42h_2]

@HowardF422

Howard, be bold - turn it back on, let it update and enjoy ... 🙂

In the absence of input from either Microsoft or HP I am as sure as I can be that the root cause was a Windows Defender issue and that was resolved through updates issued by Microsoft last month - so this particular problem is done and dusted.

My Envy survived patch Tuesday this week and is now on the latest cumulative updates including the latest Windows Defender. It continues to work just fine.

It's still "not quite ready"  for Windows 10 version 2004 according to Microsoft - I'd love to know why but that isn't really an issue. Meanwhile, my laptop having received the latest cumulative updates was then offered  and is now on version 2004. And, just for the record, my old 2013 Pavilion (A6 based) that was 'pensioned off' last year for 'fan issues' (and occasionally going walkies) was upgraded to Windows 10 version 2004 the week that it was first offered. 😉

[HowardF422]

Philip- glad to hear it is working, glad to hear.  This Defender vs. HP BSOD bug was giving me high BP for days at a time.  Yesterday I got an update from HP telling me the repaired is finished and it is on its way back to LA the next day.  The description on what's being repaired was so minimal- Reinstalled Windows.  And like everyone else here, the follow-up question is: well, what if it happens again if it's not a hardware issue.

And today, like the sword of Inigo Montoya, Google searched led me to this exact thread which I never came across previously, and I had a serious jawdrop moment after reading from the top.  I'm still shaking my head because how the F does HP crapware conflicts with Windows Defender or vice versa...  Then again, I didn't major in CS so... just glad I'm not alone on this, and HP resolved it with an update .

[Ferrumic]

@Philip42h_2

Glad it's working OK. I'm receiving updates, but I don't have Defender turned on, and I probably won't do so until the 2004 update (eventually). I have 2 other AV/Ransomware/Firewalls running, which, if they resist attack as well as they stop me from doing things until I fix or allow them, should do the job.

I have the same message about 2004 as you. The reasons for it being delayed, as I understand them, are twofold. Firstly, MS want to throttle or stagger the release to prevent server overloads, so they're dishing it out in dribs and drabs.

Secondly, there are indeed some serious problems with 2004, which could indeed affect particular configurations. The 2004 dashboard is here: 2004 Problems .

It doesn't make for happy reading, although I've looked through it to see whether any items refer to this system, and they appear not. MS still have some work to do to ensure that these problems are sorted and future ones detected and also dealt with, which seems a good reason for delaying.

Personally, I have tended to defer Feature updates for as long as possible (365 days on Pro), and only shorten the wait time when the consensus is that they have been running long enough on other people's machines to enable debugging. Past experience suggests that is usually around 60-90 days after general release.

I'm still trying to make sense of the HPSA thing, which appears to be almost useless for its intended purpose. For example, the HP Downloads and Drivers web page shows a new BIOS A41 for this machine, but not a whisper of it when checking using HPSA.

Onward and upwards, anyway.