ProBook 450 with high CPU usage

[fhgut]

The thing is that the problem does not appear after the restart. Updating Intel drivers should solve problems with BSODs and not with high CPU usage.

[TDkozlyk]

I tried this the other day - then I read the CAUTION note saying that some drivers from Intel ARE MODIFIED by HP, meaning downloading directly from Intel (which seems good to me) may still be fraught with problems.

I wish vendors like HP would not xxxk around with Intel drivers - let the experts(Intel) who knows their chips, modify their drivers & just use them - instead of HP'ing it

Just when you think you are getting somewhere . . .

[muscken]

Bad news for me!

I toguht it was ok but today the process is still at 30% ad i need to rescan hardware components.

So intel driver is not the final solution 😞

[oxapentane]

Probook 450 G5 owner here, with the same problem after every resume from sleep or hibernation. Only way to workaround that I found helpful is device rescan method. Update to latest firmware, Windows april update and latest drivers from windows update didn't solve it.

No news from @HP on this matter as far as I can tell, which a little bit weird since it is a showstopper - unless you are comfortable with switching your device off instead of putting it to sleep every time while you on the go.

[Tamkien]

So does the problem only occur when using the hibernate/sleeping mode or it happens everytime? I can consider it acceptable without hibernation.

[ArtemSnezhny]

---

@Tamkienwrote:
So does the problem only occur when using the hibernate/sleeping mode or it happens everytime? I can consider it acceptable without hibernation.

---

For me the problem sometimes occur after shutdown (not hibernate or sleep) too. Probably it is need to disable the FastBoot option in the BIOS, but I did not do it.

[ju1c3]

I had it fixed with driver version 9.0.180.10 from 1/3/2018 off the HP website. The key is to use the driver you download without running the full installer. You just point device manager to that folder and let it install. I tried the driver from 4/2 off Microsoft Update and it broke it again. 

[ArtemSnezhny]

---

@ju1c3wrote:

I had it fixed with driver version 9.0.180.10 from 1/3/2018 off the HP website. The key is to use the driver you download without running the full installer. You just point device manager to that folder and let it install. I tried the driver from 4/2 off Microsoft Update and it broke it again. 

---

On the HP website the Conexant HD Audio Driver has 12.71.2.45 Rev.Q version from Jan 14 2018 for my laptop (470 G5). I tried install it from device manager, but it says, that I already have right version. BTW, in the 'About Audio Controls' it shows 9.0.180.10 audio driver version and 4.0.52.0 software version.

[ju1c3]

Right click the device in device manager under sound, video and game controllers and uninstall the conexant ISST audio device. Check the delete driver box. Keep doing that until it has no more drivers. Then point it to that folder where the driver was located. I know that worked. I am guessing that since you ran the full install in the past its causing the issue because it did for me. I needed to clean out the drivers first before pointing it at the folder since I had tried the installer. Another laptop that had a older driver to start worked when just pointing the device at the driver folder.  

[oxapentane]

---

@ju1c3wrote:

I had it fixed with driver version 9.0.180.10 from 1/3/2018 off the HP website. The key is to use the driver you download without running the full installer. You just point device manager to that folder and let it install. I tried the driver from 4/2 off Microsoft Update and it broke it again. 

---

Didn't work for me. Same ACPI.sys hogging one logical core at semi-random times both with hp driver and one from windows update.  

As far as HP support goes - absolutely nothing helpful. They proposed to send device to service for god knows how long for what is clearly a software issue (e.g. under linux there's no troubles with this at all).

@current workaround - bought a dell xps. Judging by how long it is haunting users @hp won't do a thing to fix it. It is not even acknowledged at support page for this laptop.