Event ID 153 from nvlddmkm - "\Device\Video9 Error on GPUID: 100" Appearing Frequently

[MBM0899]

Hello,

I’ve been dealing with a persistent issue for a long time, and I believe I’ve exhausted almost all troubleshooting steps. I'm hoping HP staff or someone knowledgeable can provide a solution or insight.

In Event Viewer, I regularly see the following warning during gameplay:

The description for Event ID 153 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

The following information was included with the event:

\Device\Video9
Error occurred on GPUID: 100

This error appears while playing any GPU-intensive game (e.g., Witcher 3, GTA V, Skyrim, Mount & Blade II: Bannerlord), and it results in FPS drops, stuttering, or driver recovery behavior.

Here’s the strange part:
--The problem only occurs when the laptop is plugged into AC power.
-- When I run on battery, there is no issue whatsoever — all games run smoothly without any Event ID 153 logs.

What I’ve Tried (Extensively):

• Replaced thermal paste and cleaned internals

• Reseated and swapped RAM modules

• Removed battery and ran on AC only – issue persists

• Ran HP Hardware Diagnostics UEFI (full) – no errors

• Ran Windows built-in and HP diagnostics – no issues found

• Used DDU to completely remove NVIDIA drivers and installed:

  • The latest drivers

  • Older drivers (from 2022 till today, almost all versions tested)

• Windows clean installations:

  • Tried Windows 11 21H2, 22H2, and the latest 24H2

• Disabled the following:

  • Windows Game Bar

  • "Optimizations for windowed games"

  • Hardware-accelerated GPU scheduling

• NVIDIA Control Panel:

  • Set to Maximum Performance

  • G-Sync enabled/disabled tested

• Power settings:

  • Tested Balanced and Maximum Performance

• Frame limiter:

  • Capped FPS to 50 – still occurs

• Undervolted GPU via MSI Afterburner:

  • Down to -100 MHz – no improvement

  • Fixed core clock to 735 MHz – seems to reduce/eliminate the issue during 1–2 hour play sessions (still under test)

• Tried different wall sockets

• Measured PSU output – steady 19.5V

• Ran OCCT stress tests (VRAM, GPU) for up to 1 hour – no instability or artifacts

Important Clue:

I vaguely recall that this issue started after a BIOS update last year. Unfortunately, HP seems to block BIOS rollbacks, as the system won’t recognize the older version on USB during recovery.

My suspicion is that either:

• There’s a bug in the current BIOS that mismanages GPU behavior when on AC, or

• There might be a VBIOS (GPU firmware) issue affecting stability under high power states
  
  

System Info:

• Model: OMEN by HP Laptop 16-b1797nr

• CPU: Intel® Core™ i7-12700H

• GPU: NVIDIA® GeForce RTX™ 3070 Ti Laptop GPU (8 GB GDDR6, 150W Max TGP)

• RAM: 16 GB DDR5‑4800 MHz (Dual Channel – likely 2×8 GB SO-DIMM)

• Storage: 1 TB PCIe® Gen4 NVMe™ TLC SSD

• Display: 16.1″ QHD (2560×1440) IPS, 165 Hz

• OS: Windows 11 Home (currently running 24H2; previously tested 21H2 and 22H2 clean installs)

• BIOS Version: F.22

• VBIOS VERSION:  94.04.74.00.40

• Power Adapter: 230W HP Smart AC Adapter (output: 19.5V – confirmed stable with multimeter)

Request:

Please escalate this issue to the relevant HP support or engineering team. I believe this is not an isolated hardware failure, but possibly a firmware/BIOS-level conflict affecting GPU power management on AC.

I would be grateful for:

• Any workaround for BIOS rollback

• Official response on whether this is a known issue

• VBIOS reflash possibility (if provided by HP)

Thanks in advance.

[Max3Aj]

@MBM0899, Welcome to HP Support Community. 

Thank you for posting your query, I will be glad to help you. 
You've done an excellent job narrowing down the issue. This appears to be a power-state-related GPU issue, likely triggered by a BIOS or VBIOS bug introduced in a recent update.

Root Cause Analysis

The fact that:

• The issue only occurs on AC power,
• Does not occur on battery, and
• Started after a BIOS update,

strongly suggests a BIOS-level power delivery or GPU power state mismanagement issue. Event ID 153 from nvlddmkm typically indicates a storage or GPU timeout, often due to power instability or driver/firmware conflicts.

Recommended Steps to Resolve

Use HP BIOS Recovery Tool (if rollback is allowed)

Download the older BIOS version:

• Visit the HP Drivers & Downloads page for your model.
• Look under the BIOS section.
• If older versions are listed, download the one you want to roll back to.

Create a BIOS recovery USB:

• Run the downloaded .exe file.
• Choose "Create Recovery USB Flash Drive" when prompted.
• Insert a USB drive (8–16 GB), and let the tool create the recovery media.

Enter BIOS Recovery Mode:

• Turn off the laptop.
• Press and hold Windows + B, then press and hold the Power button for 2–3 seconds.
• Release the Power button but keep holding Windows + B until the BIOS recovery screen appears.

Follow on-screen instructions to install the older BIOS.
 

Force GPU to Lower Power State on AC

Since underclocking the GPU to 735 MHz reduces the issue, try this workaround:

• Use MSI Afterburner to:
  • Set Core Clock Offset to -150 MHz.
  • Set Power Limit to 80–85%.
  • Enable Custom Fan Curve to keep temps low.
• Save this as a profile and auto-load it on startup.

This reduces power draw and may prevent the GPU from entering unstable high-power states.

Test with HP OMEN Gaming Hub Performance Modes

• Open OMEN Gaming Hub.
• Go to Performance Control.
• Set to Balanced or Quiet mode (instead of Performance).
• This may limit GPU boost behavior and avoid triggering the issue.

Try Alternate NVIDIA Driver Branch

Sometimes switching driver branches helps:

• Use NVIDIA Studio Drivers instead of Game Ready Drivers.
• Or try a clean install of a known stable version like 531.79 or 537.42 using DDU.

Optional: Advanced Debugging

If you're comfortable:

• Use GPU-Z to monitor VBIOS version and power draw.
• Use LatencyMon to check for DPC latency spikes during AC usage.
• Log GPU behavior with NVIDIA Nsight or Windows Performance Recorder. 

I hope this helps. 

Take care and have a good day. 

Please click “Accepted Solution” if you feel my post solved your issue, it will help others find the solution. Select "Yes" on the bottom left to say “Thanks” for helping! 

Max3Aj

HP Support 

[MBM0899]

Thank you for the response.

I appreciate the time you took to assist me, but unfortunately, most of the suggestions you’ve provided have already been thoroughly tested, as clearly stated in my initial post.

 

Regarding BIOS Rollback:

You recommended using the HP BIOS Recovery Tool, but as I mentioned: Unfortunately, HP seems to block BIOS rollbacks, as the system won’t recognize the older version on USB during recovery.

Regarding MSI Afterburner:

“Set Power Limit to 80–85%”

My system does not allow adjusting the power limit via MSI Afterburner — it's locked. Only the GPU core clock can be lowered.

OMEN Gaming Hub:

I’ve already tested all modes available (Balanced, Quiet, Performance), and none resolved the issue.

 

Driver Branches:

I’ve tested nearly every driver from 2022 to 2024 — including both Game Ready and Studio versions, such as 531.79 and 537.42 (as you mentioned). No version resolved the issue.

LatencyMon:

I’ve now conducted an advanced DPC latency test using LatencyMon, as you suggested — and the results confirm the issue is indeed related to GPU and power management routines under AC power. Here is the output:

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing
as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long.
One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:09:50 (h:mm:ss) on all processors.

_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-7AONHV2
OS version: Windows 11, 10.0, version 2009, build: 26100 (x64)
Hardware: OMEN by HP Laptop 16-b1xxx, HP
BIOS: F.22
CPU: GenuineIntel 12th Gen Intel(R) Core(TM) i7-12700H
Logical processors: 20
Processor groups: 1
Processor group size: 20
RAM: 16051 MB total

_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 230 MHz
Reported CPU speed (registry): 2688 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step
and AMD Cool N Quiet in the BIOS setup for more accurate results.

_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the
moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an
event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 5233.80
Average measured interrupt to process latency (µs): 23.164366

Highest measured interrupt to DPC latency (µs): 1145.20
Average measured interrupt to DPC latency (µs): 4.436710

_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 775.828125
Driver with highest ISR routine execution time: ACPI.sys - ACPI Driver for NT, Microsoft Corporation

Highest reported total ISR routine time (%): 0.005376
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0.005821

ISR count (execution time <250 µs): 51155
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 87
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0

_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is
interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 6763.032738
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 576.88 , NVIDIA Corporation

Highest reported total DPC routine time (%): 0.018302
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in DPCs (%) 0.103379

DPC count (execution time <250 µs): 1912619
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 568
DPC count (execution time 1000-2000 µs): 42
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 1

_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file
on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked
from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream
resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: omencommandcenterbackground.exe

Total number of hard pagefaults 69303
Hard pagefault count of hardest hit process: 11690
Number of processes hit: 208

_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 10.817437
CPU 0 ISR highest execution time (µs): 775.828125
CPU 0 ISR total execution time (s): 0.397674
CPU 0 ISR count: 23708
CPU 0 DPC highest execution time (µs): 1481.672619
CPU 0 DPC total execution time (s): 1.547955
CPU 0 DPC count: 147151
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 9.606155
CPU 1 ISR highest execution time (µs): 124.430060
CPU 1 ISR total execution time (s): 0.000779
CPU 1 ISR count: 7
CPU 1 DPC highest execution time (µs): 1034.825149
CPU 1 DPC total execution time (s): 1.365164
CPU 1 DPC count: 124694
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 12.285862
CPU 2 ISR highest execution time (µs): 119.397321
CPU 2 ISR total execution time (s): 0.000119
CPU 2 ISR count: 1
CPU 2 DPC highest execution time (µs): 1403.360863
CPU 2 DPC total execution time (s): 1.973193
CPU 2 DPC count: 222009
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 4.538574
CPU 3 ISR highest execution time (µs): 242.674107
CPU 3 ISR total execution time (s): 0.038383
CPU 3 ISR count: 3528
CPU 3 DPC highest execution time (µs): 920.436756
CPU 3 DPC total execution time (s): 0.303486
CPU 3 DPC count: 45610
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 11.179161
CPU 4 ISR highest execution time (µs): 563.617560
CPU 4 ISR total execution time (s): 0.189217
CPU 4 ISR count: 19922
CPU 4 DPC highest execution time (µs): 1188.570685
CPU 4 DPC total execution time (s): 1.530597
CPU 4 DPC count: 316901
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 8.383850
CPU 5 ISR highest execution time (µs): 0.0
CPU 5 ISR total execution time (s): 0.0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 6763.032738
CPU 5 DPC total execution time (s): 0.818311
CPU 5 DPC count: 106260
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 11.949912
CPU 6 ISR highest execution time (µs): 76.614583
CPU 6 ISR total execution time (s): 0.000077
CPU 6 ISR count: 1
CPU 6 DPC highest execution time (µs): 737.718006
CPU 6 DPC total execution time (s): 1.254267
CPU 6 DPC count: 293592
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 6.030514
CPU 7 ISR highest execution time (µs): 322.281994
CPU 7 ISR total execution time (s): 0.017237
CPU 7 ISR count: 940
CPU 7 DPC highest execution time (µs): 1281.260417
CPU 7 DPC total execution time (s): 0.328588
CPU 7 DPC count: 118204
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 5.838781
CPU 8 ISR highest execution time (µs): 223.896577
CPU 8 ISR total execution time (s): 0.031684
CPU 8 ISR count: 2698
CPU 8 DPC highest execution time (µs): 842.558036
CPU 8 DPC total execution time (s): 0.393943
CPU 8 DPC count: 85843
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 3.645632
CPU 9 ISR highest execution time (µs): 0.0
CPU 9 ISR total execution time (s): 0.0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 382.505952
CPU 9 DPC total execution time (s): 0.162413
CPU 9 DPC count: 23748
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 7.405811
CPU 10 ISR highest execution time (µs): 0.0
CPU 10 ISR total execution time (s): 0.0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 1035.523810
CPU 10 DPC total execution time (s): 0.652937
CPU 10 DPC count: 132858
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 4.067212
CPU 11 ISR highest execution time (µs): 86.518601
CPU 11 ISR total execution time (s): 0.007866
CPU 11 ISR count: 317
CPU 11 DPC highest execution time (µs): 379.031994
CPU 11 DPC total execution time (s): 0.124126
CPU 11 DPC count: 31638
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 4.990627
CPU 12 ISR highest execution time (µs): 79.254464
CPU 12 ISR total execution time (s): 0.004174
CPU 12 ISR count: 117
CPU 12 DPC highest execution time (µs): 722.837798
CPU 12 DPC total execution time (s): 0.361552
CPU 12 DPC count: 51304
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 4.360279
CPU 13 ISR highest execution time (µs): 0.0
CPU 13 ISR total execution time (s): 0.0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 226.258929
CPU 13 DPC total execution time (s): 0.229717
CPU 13 DPC count: 36670
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 4.199921
CPU 14 ISR highest execution time (µs): 0.0
CPU 14 ISR total execution time (s): 0.0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 372.757440
CPU 14 DPC total execution time (s): 0.210170
CPU 14 DPC count: 37955
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 4.081124
CPU 15 ISR highest execution time (µs): 70.247024
CPU 15 ISR total execution time (s): 0.000206
CPU 15 ISR count: 3
CPU 15 DPC highest execution time (µs): 362.203869
CPU 15 DPC total execution time (s): 0.175744
CPU 15 DPC count: 26677
_________________________________________________________________________________________________________
CPU 16 Interrupt cycle time (s): 4.503050
CPU 16 ISR highest execution time (µs): 0.0
CPU 16 ISR total execution time (s): 0.0
CPU 16 ISR count: 0
CPU 16 DPC highest execution time (µs): 712.167411
CPU 16 DPC total execution time (s): 0.264032
CPU 16 DPC count: 38075
_________________________________________________________________________________________________________
CPU 17 Interrupt cycle time (s): 3.761212
CPU 17 ISR highest execution time (µs): 0.0
CPU 17 ISR total execution time (s): 0.0
CPU 17 ISR count: 0
CPU 17 DPC highest execution time (µs): 720.630952
CPU 17 DPC total execution time (s): 0.188859
CPU 17 DPC count: 28081
_________________________________________________________________________________________________________
CPU 18 Interrupt cycle time (s): 3.665206
CPU 18 ISR highest execution time (µs): 0.0
CPU 18 ISR total execution time (s): 0.0
CPU 18 ISR count: 0
CPU 18 DPC highest execution time (µs): 719.970238
CPU 18 DPC total execution time (s): 0.183308
CPU 18 DPC count: 26823
_________________________________________________________________________________________________________
CPU 19 Interrupt cycle time (s): 3.378057
CPU 19 ISR highest execution time (µs): 0.0
CPU 19 ISR total execution time (s): 0.0
CPU 19 ISR count: 0
CPU 19 DPC highest execution time (µs): 362.731399
CPU 19 DPC total execution time (s): 0.140421
CPU 19 DPC count: 19137
_________________________________________________________________________________________________________

This supports my suspicion that this is not a driver-only issue, but potentially a conflict or bug in BIOS firmware or ACPI power state handling, especially under AC power. All of this strongly points to a firmware or BIOS-related mismanagement of GPU power states.

Request:

Please escalate this issue to the BIOS or firmware engineering team. This is not a basic driver issue, and users cannot resolve it without a BIOS update or an official rollback method. The inability to roll back to a known working BIOS is making this issue persistent.

I would be grateful for:

• Any workaround for BIOS rollback

• Official response on whether this is a known issue

• VBIOS reflash possibility (if provided by HP)

Thanks again.

[MBM0899]

Thank you for the response.

I appreciate the time you took to assist me, but unfortunately, most of the suggestions you’ve provided have already been thoroughly tested, as clearly stated in my initial post.

 

Regarding BIOS Rollback:

You recommended using the HP BIOS Recovery Tool, but as I mentioned: Unfortunately, HP seems to block BIOS rollbacks, as the system won’t recognize the older version on USB during recovery.

Regarding MSI Afterburner:

“Set Power Limit to 80–85%”

My system does not allow adjusting the power limit via MSI Afterburner — it's locked. Only the GPU core clock can be lowered.

OMEN Gaming Hub:

I’ve already tested all modes available (Balanced, Quiet, Performance), and none resolved the issue.

 

Driver Branches:

I’ve tested nearly every driver from 2022 to until today — including both Game Ready and Studio versions, such as 531.79 and 537.42 (as you mentioned). No version resolved the issue.

LatencyMon:

I’ve now conducted an advanced DPC latency test using LatencyMon, as you suggested — and the results confirm the issue is indeed related to GPU and power management routines under AC power.

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:09:50 (h:mm:ss) on all processors.

_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-7AONHV2
OS version: Windows 11, 10.0, version 2009, build: 26100 (x64)
Hardware: OMEN by HP Laptop 16-b1xxx, HP
BIOS: F.22
CPU: GenuineIntel 12th Gen Intel(R) Core(TM) i7-12700H
Logical processors: 20
Processor groups: 1
Processor group size: 20
RAM: 16051 MB total

_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 230 MHz
Reported CPU speed (registry): 2688 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 5233.80
Average measured interrupt to process latency (µs): 23.164366

Highest measured interrupt to DPC latency (µs): 1145.20
Average measured interrupt to DPC latency (µs): 4.436710

_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 775.828125
Driver with highest ISR routine execution time: ACPI.sys - ACPI Driver for NT, Microsoft Corporation

Highest reported total ISR routine time (%): 0.005376
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0.005821

ISR count (execution time <250 µs): 51155
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 87
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0

_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 6763.032738
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 576.88 , NVIDIA Corporation

Highest reported total DPC routine time (%): 0.018302
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in DPCs (%) 0.103379

DPC count (execution time <250 µs): 1912619
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 568
DPC count (execution time 1000-2000 µs): 42
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 1

_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: omencommandcenterbackground.exe

Total number of hard pagefaults 69303
Hard pagefault count of hardest hit process: 11690
Number of processes hit: 208

This supports my suspicion that this is not a driver-only issue, but potentially a conflict or bug in BIOS firmware or ACPI power state handling, especially under AC power.

Request:

Please escalate this issue to the BIOS or firmware engineering team. This is not a basic driver issue, and users cannot resolve it without a BIOS update or an official rollback method. The inability to roll back to a known working BIOS is making this issue persistent.

I would be grateful for:

• Any workaround for BIOS rollback

• Official response on whether this is a known issue

• VBIOS reflash possibility (if provided by HP)

Thanks again!

[Max3Aj]

@MBM0899, Thank you for your response,  

I'm sending a private message to assist you with the next action. 

  

Please check your Private message icon on the upper right corner of your HP Community profile Next, to your profile Name, you should see a little blue envelope, please click on it or simply click on this link. 

  

I hope this helps! Keep me posted. 

  

Max3Aj

HP Support 

[Darkix]

Could you help me as well if possible? I'm having the same exact issue.