HP Omen 17 - High system/ntoskrnl.exe/ACPI.sys process usage.

[lewy01]

Hello, I have syrious problem with my HP Omen 17 unit - System process takes 30% of cpu during idle time. Under load it takes effect on games FPS, screen stuttering etc.

Problem occurs at first boot (after about 5-10 min shutdown). After 1-3 Windows restart it disappears.
But it's unacceptable situation, since I need this pc for work (where time of reaction matters, so it cannot be just restarted each boot).

At first it occured as ACPI.sys+0x42f50

After Windows update to 1809 it shows as ACPI.sys+0283d0

Here is what I've tried:

- Run Diagnostic Software from HP (full test etc.)
- Run Diagnostics with Windows Performance Analyzer
- LatencyMon Home Edition shows that ACPI.sys works incorrectly
- Clean boot (Windows)
- Turning off Fast start up(Windows)
- Turning off devices one by one in Device Manager
- Updating all drivers to actual versions
- Restoring Windows with F11
- Re-installing Windows with iso image from Microsoft (format and clean installation)
- Turning off magic packet from network card
- Trying to install Windows on different drives (HDD/different SSD)
- Uninstalling M2 SSD

- and all rest stuff that was suggested on similar topics....

I have additional SATA caddy, but it was uninstalled in a first place in this investigation

Some screenshots:

- task manager:

- from procexp64:

- from Windows Performance Analyzer:

 Please let me know what else can I do, because this issue is really annoying and sits in a back of my head all the time.

[lewy01]

Really, no clue ? I've seen some guys got private messages and mark this problem as solved. I mean, in thist situation I won't be even able to sell this laptop, cause is pretty much obious giant flaw, spotted on the first sight.

[matck06]

The problem is probably hardware, and hp covers the problem because the technical support says that the problem does not prevent the use.

[ltmd]

Hello. I have an omen by hp 15-ce 01 tx unit. It also had the same problem. However, it was solved by replacing HDD with SSD.

[lewy01]

Unfortunately it doesn't help in my case. I've tried every possible hdd/sdd, m2/sata combination with fresh W10 installation each time. Like Matck06 said, it must be some hardware issue.