Question DRIVER_POWER_STATE_FAILURE (9f) - need help pinpointing the issue.

[Arthur-The Shaolin Gamer-]

Can someone help me troubleshoot my hardware. I found many threads with this issue but I realized is very specific to every user.
My symptoms are random freezes while gaming, browsing, or idle, can happen 5 minutes after boot or 4 hours. I get this hard freeze daily between 1 to 3 times a day. Seconds before the hang, I get a system-wide peripherals disconnect (Blutooth, PCI-E Wifi card, wired Keyboard and mouse and then everything stop having to hold the power button to shut off the PC. Sometimes it takes too long to shut the PC after clicking the Shut-off option. Sometimes the RGB in the fans and USBs port randomly disconnect but return almost inmediately and is almost certain a freeze will ocurr soon. I have never actually seen a bluescreen, but the DUMP file marks as there is one. I have tried updating drivers (with DDU as well), updating windows, fresh install on windows, testing ram, switching my RAM stick to other dimm slots (only have one 16gb ram stick, I know) and also disabled DOCP. I have reseated my GPU (RTX 2060), I bought a new PSU and still having the same issue.
I have the MEMDUMP file. Also I include my whole setup.

Please help, I thought I could solve this and let time pass, now after 4 months the store won't take it back since is a pre-built PC and added some stuff to it.

Motherboard: ASUS PRIME a520m-A II (Bios 2806) - Which I also updated on January.
DRAM: 1x16gb XPG Adata 3200 mhz (DOCP speed)
GPU: ASUS RTX 2060
Proccesor: AMD Ryzen 7 5700X
PSU: EVGA 750w BQ series.

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffffb9820e24f060, Physical Device Object of the stack
Arg3: ffffb880cf02f810, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffb98214f968e0, The blocked IRP

Debugging Details:
------------------

Implicit thread is now ffffb981`fd8e4040

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4093

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 4141

Key : Analysis.Init.CPU.mSec
Value: 1984

Key : Analysis.Init.Elapsed.mSec
Value: 17461

Key : Analysis.Memory.CommitPeak.Mb
Value: 159

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffb9820e24f060

BUGCHECK_P3: ffffb880cf02f810

BUGCHECK_P4: ffffb98214f968e0

DRVPOWERSTATE_SUBCODE: 3

FAULTING_THREAD: ffffb981fd8e4040

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffb880`cf0170e0 fffff801`19c1c9c0 : ffff8381`d4b00180 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x76
ffffb880`cf017220 fffff801`19c1beef : ffffb982`00000009 fffff801`00000008 ffffb880`cf0173e0 fffff801`00000000 : nt!KiSwapThread+0x500
ffffb880`cf0172d0 fffff801`19c1b793 : ffffb981`00000000 fffff801`00000000 ffff8381`d4b00100 ffffb981`fd8e4180 : nt!KiCommitThreadWait+0x14f
ffffb880`cf017370 fffff801`39024ebe : ffffb982`16a36418 00000000`00000000 00000000`00000000 ffffb880`cf017500 : nt!KeWaitForSingleObject+0x233
ffffb880`cf017460 fffff801`390241c7 : ffffb982`1b4f5290 00000000`00000002 ffffb982`14f96ec0 ffffb982`14f968e0 : HIDCLASS!CancelAllPingPongIrps+0x1fe
ffffb880`cf0174c0 fffff801`390226c6 : ffffb982`1b4f5270 00000000`00000000 00000000`00000016 ffffb982`1b4f5150 : HIDCLASS!HidpFdoPower+0x247
ffffb880`cf017540 fffff801`19d981ff : ffffb880`cf017800 ffffb982`14f968e0 ffffb982`14f968e0 ffffb982`14e3db68 : HIDCLASS!HidpMajorHandler+0x206
ffffb880`cf0175d0 fffff801`19c1139d : ffffb982`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopPoHandleIrp+0x3b
ffffb880`cf017600 fffff801`19d9a489 : 00000000`00000000 ffffb982`14e3db68 00000000`00000000 fffff801`1d7c0000 : nt!IofCallDriver+0x6d
ffffb880`cf017640 fffff801`1d7c04a9 : 00000000`00000000 00000000`00000001 00000000`00000005 ffffb880`cf017800 : nt!IoCallDriver+0x9
ffffb880`cf017670 fffff801`1d7c041b : 00000000`00000000 00000000`00000005 00000000`00000005 ffffb982`14e3d8b0 : Wdf01000!FxPkgFdo::_PowerPassDown+0x79 [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 85]
ffffb880`cf0176a0 fffff801`1d7cc229 : ffffb982`14f968e0 00000000`00000000 00000000`00000005 ffffb982`14e3d8b0 : Wdf01000!FxPkgFdo:owerReleasePendingDeviceIrp+0x4b [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 496]
ffffb880`cf0176d0 fffff801`1d7c139b : 00000000`00000000 ffffb880`cf017870 00000000`00000380 00000000`00000000 : Wdf01000!FxPkgPnp:owerGotoDxIoStoppedCommon+0x1cd [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 3138]
ffffb880`cf017740 fffff801`1d7c25f5 : 00000000`0000031c 00000000`00000b20 ffffb982`14e3d8b0 00000000`00000359 : Wdf01000!FxPkgPnpowerGotoDNotZeroIoStopped+0xb [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 2842]
ffffb880`cf017770 fffff801`1d7c23aa : 00000000`00000340 ffffb982`14e3d8b0 ffffb982`14e3d8b0 fffff801`1eb1a8d2 : Wdf01000!FxPkgPnpowerEnterNewState+0x155 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1699]
ffffb880`cf0178d0 fffff801`1d7c1911 : ffffb982`14e3d8b0 00000000`00000000 00000000`00000002 ffffb982`005fc800 : Wdf01000!FxPkgPnpowerProcessEventInner+0xea [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1615]
ffffb880`cf017950 fffff801`1d7c1135 : 00000000`00000000 ffffb880`cf017ad0 ffffb982`14e3d8b0 ffffb880`cf017bb0 : Wdf01000!FxPkgPnpowerProcessEvent+0x1d1 [minkernel\wdf\framework\shared\irphandlers\pnp\powerstatemachine.cpp @ 1394]
ffffb880`cf0179e0 fffff801`1d7c10b5 : ffffb982`14e3d8b0 ffffb880`cf017aa8 00000000`00000004 00000000`00000000 : Wdf01000!FxPkgFdoispatchDeviceSetPower+0x75 [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 350]
ffffb880`cf017a30 fffff801`1d7bcc5f : ffffb982`14e3d8b0 ffffb982`14e02c40 ffffad4c`140e6876 ffffb982`163a8818 : Wdf01000!FxPkgFdo::_DispatchSetPower+0x25 [minkernel\wdf\framework\shared\irphandlers\pnp\fdopower.cpp @ 120]
ffffb880`cf017a60 fffff801`1d7ba866 : ffffb982`14f968e0 ffffb982`10cdea50 ffffb982`14f968e0 fffff801`1a6232d0 : Wdf01000!FxPkgPnpispatch+0xaf [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 765]
ffffb880`cf017ad0 fffff801`19d9c6a9 : 00000000`00000000 00000000`00000000 ffff8381`d48f3000 ffffb981`fd8e4040 : Wdf01000!FxDeviceispatchWithLock+0x156 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447]
ffffb880`cf017b30 fffff801`19d265f5 : 00000000`00000000 fffff801`19d9c4d0 00000000`00000000 00000000`000000aa : nt!PopIrpWorker+0x1d9
ffffb880`cf017bd0 fffff801`19e048d8 : ffff8381`d48e5180 ffffb981`fd8e4040 fffff801`19d265a0 ca590593`c6190597 : nt!PspSystemThreadStartup+0x55
ffffb880`cf017c20 00000000`00000000 : ffffb880`cf018000 ffffb880`cf011000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: HIDCLASS!CancelAllPingPongIrps+1fe

MODULE_NAME: HIDCLASS

IMAGE_NAME: HIDCLASS.SYS

IMAGE_VERSION: 10.0.19041.2486

STACK_COMMAND: .process /r /p 0xffffb981fd88a0c0; .thread 0xffffb981fd8e4040 ; kb

BUCKET_ID_FUNC_OFFSET: 1fe

FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_HIDCLASS!CancelAllPingPongIrps

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5dd6deb1-98c3-820d-f697-a08332e4e820}

Followup: MachineOwner

Any help will be appreciated.

 

[Colif]

HIDCLASS is used by windows to communicate with Keyboards, Mice & other USB items such as WIFI Dongles.
the other things mentioned in the dump text are also parts of windows.
Its difficult to say what driver is to blame from that report.

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 . . .

Have you updated chipset drivers - https://www.amd.com/en/support/chipsets/amd-socket-am4/a520

USB built into windows so if its showing HID, what Keyboards/mice do you have?

 

[Arthur-The Shaolin Gamer-]

HIDCLASS is used by windows to communicate with Keyboards, Mice & other USB items such as WIFI Dongles.
the other things mentioned in the dump text are also parts of windows.
Its difficult to say what driver is to blame from that report.

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 . . .

Have you updated chipset drivers - https://www.amd.com/en/support/chipsets/amd-socket-am4/a520

USB built into windows so if its showing HID, what Keyboards/mice do you have?

- This is the link to my last 3 .dmp files.

MiniDump File

Folder

1drv.ms

- I have updated chipset drivers as well

- I used to have a used Logitch wireless mouse and switched to this Cobra Chrome Redragon Mouse. As for the keyboard, I got a cheap Logitech Keyboard which I had from another old computer. The keyboard, my previous mouse and this new Redragon were tested in different USB ports as well (except the front panel USBs)

 

[ubuysa]

All three dumps are identical, they all show that the power transition failure (and the resulting blocked IRP) was caused by HidHide.sys...

>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0  0 ffff848d903be060 00000000 00000000-00000000
           \Driver\HidUsb
            Args: 00016600 00000001 00000004 00000006
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff848d9038fae0 00000000 fffff80055f7a700-ffff848d8fdf31e8 Success Error Cancel pending
          Unable to load image \SystemRoot\System32\drivers\HidHide.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for HidHide.sys
 \Driver\HidHide    nt!PopRequestCompletion                                               <========== This is the driver blocking the IRP
            Args: 00016600 00000001 00000004 00000006
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffff848d8fdf31e8

            Args: 00000000 00000000 00000000 00000000

The HidHide.sys driver is the HidHide filter driver. The version you have installed is almost a year old...

1: kd> lmDvmHidHide
Browse full module list
start             end                 module name
fffff801`38ea0000 fffff801`38eb1000   HidHide  T (no symbols)     
    Loaded symbol image file: HidHide.sys
    Image path: \SystemRoot\System32\drivers\HidHide.sys
    Image name: HidHide.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Jun 27 20:42:45 2022 (62B9EC15)
    CheckSum:         00012310
    ImageSize:        00011000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I would either look for an update to this driver or uninstall it completely.

 

[Arthur-The Shaolin Gamer-]

I have a third party software I use to connect my Ps4 controller and be diguised as a XBOX controller, for compatibility with games. It has a sub program called hidHide, which only hides the ps4 drivers from the machine and avoid having a double controller detected.

Could that single program cause a full system hang? I recall installing it quite recently.

EDIT: I just had a couple freeze 1 hours ago and though I could still control the mouse pointer and open the Windows Menu, nothing else worked Force shut down and no minidump was generated. Most of the time the PC don't even generate a minidump file.

I am going to uninstall everything related to hidhide and see if that works. I'll keep you posted. Thanks.

 

[ubuysa]

Could that single program cause a full system hang? I recall installing it quite recently.

Yes, certainly!

Kernel mode drivers, which HidHide.sys is, run in kernel-mode. In kernel-mode the recovery options are severely limited (kernel mode code is required by design to behave itself), so whenever something unexpected happens, like a driver blocking (holding) an IRP (an interrupt request packet) for too long, the kernel causes a BSOD. The reason for a BSOD is to protect your data. Because the kernel does not understand what has happened, and because it's a kernel mode problem (which can trample on anything and everything), the system BSODs to stop potential data corruption.

Those three dumps don't lie and they all agree, as you saw; HidHide.sys was the driver holding on to that blocked IRP. Sometimes when analysing dumps we need to use a bit of intuition and/or experience to determine the root cause, but in the case of these DRIVER_POWER_STATE_FAILURE bugchecks, the cause is quite clear; it's HidHide.sys for sure.

 

[Colif]

GitHub - nefarius/HidHide: Gaming Input Peripherals Device Firewall for Windows.

Gaming Input Peripherals Device Firewall for Windows. - nefarius/HidHide

github.com

 

[Arthur-The Shaolin Gamer-]

GitHub - nefarius/HidHide: Gaming Input Peripherals Device Firewall for Windows.

Gaming Input Peripherals Device Firewall for Windows. - nefarius/HidHide

github.com

I remove everything related to hidhide.sys and drivers from the DS4 software. I just got another freeze; USB disconnected, everything froze but the mouse, as always. There is no BSOD, or minidump file generated. Nothing. Event viewer shows nothing but the forced shutdown. There is no evidence anything was wrong.

After rebooting I got an "overcurrent protection screen" and the system shut itself off again. Another reboot and froze during POST. The next reboot everything was fine. This error happened before as well, but havent had it from a while now.

I suppose there must be some hardware issue here. Anyways, thanks for your help, I really appreciate it.

 

[ubuysa]

Oh, that doesn't sound good. A failure during POST isn't a Windows problem. Best of luck.

 

[Arthur-The Shaolin Gamer-]

Oh, that doesn't sound good. A failure during POST isn't a Windows problem. Best of luck.

I have found 2 events tha happens at the same time of the crash.

The infamous microsoft Gameinput reconfiguration as showed in the Reliability history. Although it happens multiple times, it "almost" always coincides with a hang. I took measures to uninstall it to see if that works.

The other event (which I don't know what even is) that matches the exact time of the system hang and it is registered on the Event Viewer:

>Error en la inicialización de la inscripción de certificados de SCEP para WORKGROUP\DESKTOP-VKOCEJS$ a través de https://AMD-KeyId-907d65e9b562315997dd5ad086b2b7598957b92c.microsoftaik.azure.net/templates/Aik/scep:

GetCACaps
GetCACaps: Not Found
{"Message":"The authority \"amd-keyid-907d65e9b562315997dd5ad086b2b7598957b92c.microsoftaik.azure.net\" does not exist."}
HTTP/1.1 404 Not Found
Date: Fri, 05 May 2023 04:43:56 GMT
Content-Length: 121
Content-Type: application/json; charset=utf-8
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=31536000;includeSubDomains
x-ms-request-id: 006a9779-7796-445c-8ae7-46ea7fc741c4

Método: GET(485ms)
Fase: GetCACaps
No encontrado (404). 0x80190194 (-2145844844 HTTP_E_STATUS_NOT_FOUND)

No dumpfile or minidump file is generated, and when the PC hangs very often show both events, and always at least one of them.