Question HP Omen “Driver Power State Failure” & BSOD GPU ?

Oct 26, 2022
7
0
10

Like I said before (link above) - BSOD when I'm trying to use GPU 3070 with charger.

Charger working 100% (I have two chargers (same omen chargers) )

Help, please.
 

Colif

Win 11 Master
Moderator
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
 
Oct 26, 2022
7
0
10
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .


Thanks for the answer!

https://dropmefiles.com/DxG5u

Minidumps (it's before total windows reinstalling) (anyway, it was useless)
 

Colif

Win 11 Master
Moderator
report - click run as fiddle to read


File: 102622-13218-01.dmp (Oct 26 2022 - 15:27:32)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: pci.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 06 Min(s), and 34 Sec(s)

File: 102622-12625-01.dmp (Oct 27 2022 - 00:21:10)
BugCheck: [VIDEO_DXGKRNL_FATAL_ERROR (113)]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by: dxgkrnl.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 22 Sec(s)

File: 102622-12500-01.dmp (Oct 26 2022 - 23:53:00)
BugCheck: [VIDEO_DXGKRNL_FATAL_ERROR (113)]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by: dxgkrnl.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 11 Min(s), and 53 Sec(s)

File: 102622-12296-01.dmp (Oct 26 2022 - 17:30:15)
BugCheck: [PFN_LIST_CORRUPT (4E)]
*** WARNING: Unable to verify timestamp for GPU-Z-v2.sys
Probably caused by: memory_corruption (Process: GPU-Z.2.46.0.e)
Uptime: 0 Day(s), 0 Hour(s), 34 Min(s), and 39 Sec(s)

File: 102622-12234-01.dmp (Oct 26 2022 - 15:07:30)
BugCheck: [VIDEO_DXGKRNL_FATAL_ERROR (113)]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by: dxgkrnl.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 07 Min(s), and 23 Sec(s)

Comment: The overclocking driver "IOCBios2.sys" was found on your system. (Intel Extreme Tuning Utility)

The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

3 out of 5 blame Nvidia drivers, one blames
Apr 11 2022GPU-Z-v2.sysTechPowerUp CPUID GPU-Z driver https://www.techpowerup.com/

Have you run this? use it to check drivers
https://support.hp.com/au-en/help/hp-support-assistant
this seems old but might be okay
Oct 26 2017hpomencustomcapdriver.sysHP Omen Custom Capabilities driver
 
Last edited:
Oct 26, 2022
7
0
10
I've tried uninstalling the driver and trying to install a new one, didn't help. On a completely clean Windows, the same thing, but I'll check on a different version.

Yes, I used GPU-Z, I'll try not to use it next time.

I'll post the results a little later.


I also tried DDU before. Didn't help me.

Overclocking file, I guess, from Omen app undervolting feature for CPU. It's off now, anyway.
 
Last edited:

Colif

Win 11 Master
Moderator
its possible you should try to use the Nvidia driver supplied by HP, the newer Nvidia driver might not be working with the switchable graphics driver from Intel.

I expect report just shows Nvidia again

report - click Run as fiddle to read


File: 102722-12812-01.dmp (Oct 28 2022 - 02:51:59)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: pci.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 07 Min(s), and 44 Sec(s)

File: 102722-12734-01.dmp (Oct 28 2022 - 01:28:03)
BugCheck: [DPC_WATCHDOG_VIOLATION (133)]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by: nvlddmkm.sys (Process: MsMpEng.exe)
Uptime: 0 Day(s), 0 Hour(s), 04 Min(s), and 39 Sec(s)

File: 102622-12109-01.dmp (Oct 27 2022 - 03:14:30)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: pci.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 15 Min(s), and 11 Sec(s)

File: 102622-11968-01.dmp (Oct 27 2022 - 04:33:58)
BugCheck: [VIDEO_DXGKRNL_FATAL_ERROR (113)]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by: dxgkrnl.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 05 Min(s), and 25 Sec(s)


Yeah, for 2 of them.
Driver Power State Failures mentioning pci.sys errors seem to be GPU drivers most of time.

what power plan are you running in? what is it set to run when plugged in?
 
Oct 26, 2022
7
0
10
I seem to have set the one suggested by the HP site (I'm not sure exactly, I tried a lot of things - I might not remember) I'll try to roll back to different versions now.

I have tried different power settings. I tried the standard HP and the maximum performance mode and tried to change it myself as suggested by some sites where there were similar cases. Still useless.

Gonna try some drivers.


By the way. How likely is it that this is not a software problem, but a hardware one?

Literally new laptop. Bad luck, I guess.