BSOD driver power state failure, only on cold boot

Hey there,

I've been having problems with this for a few months and gradually trying to figure out what it going wrong, but im at a loss now.

Any time I leave my PC off for an extended period (usually overnight) around 2 minutes after first boot I get a BSOD and forced restart with the error reading driver power state failure. Once the system resumes, it seems to run perfectly. For now i have disabled all overclocks, but even when they are on the system is rock stable after the initial first crash.

Things i have tried that resulted in the same problem:
- Remove OC from CPU and GPU
- Remove Creative soundcard and drivers
- Disable Intel Wifi / Bluetooth m.2 card in BIOS (haven't physically remove because it requires removing I/O shield.
- Complete fresh Win 10 install
- Multiple fresh Nvidia driver installs (uninstall, boot to safe, run DDU, reinstall latest version).

I have tried analyzing the minidump myself and using whocrashed ect but it doesnt give me anything i understand. Hopefully someone here will be able to shed more light :)

Thanks in advance for your time!

PS: I uploaded a separate zip with the raw minidump file, the tool didnt seem to find it in the default directory.

Please note the forum rules that state that help will not be given if we suspect that you are avoiding activation of software products installed on your system.

All the crashes point to a blocked IRP (I/O Request Packet) caused by the Xbox360 wireless receiver driver. See if you can find an update for it.

Code:

0: kd> !irp ffffc20637606cf0
Irp is active with 3 stacks 2 is current (= 0xffffc20637606e08)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
            0  0 ffffc2063cb9e390 00000000 00000000-00000000    
	      *** WARNING: Unable to verify timestamp for nvvhci.sys
*** ERROR: Module load completed but symbols could not be loaded for nvvhci.sys
 \Driver\nvvhci
			Args: 00000000 00000000 00000000 00000002
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffc2063b2ac1c0 00000000 fffff801eab33180-ffffc20635a91010 Success Error Cancel pending
	       \Driver\xusb22	nt!PopRequestCompletion
			Args: 00051100 00000001 00000001 00000002
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffc20635a91010    

			Args: 00000000 00000000 00000000 00000000

philc43 said:

All the crashes point to a blocked IRP (I/O Request Packet) caused by the Xbox360 wireless receiver driver. See if you can find an update for it.

Code:

0: kd> !irp ffffc20637606cf0
Irp is active with 3 stacks 2 is current (= 0xffffc20637606e08)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
            0  0 ffffc2063cb9e390 00000000 00000000-00000000    
	      *** WARNING: Unable to verify timestamp for nvvhci.sys
*** ERROR: Module load completed but symbols could not be loaded for nvvhci.sys
 \Driver\nvvhci
			Args: 00000000 00000000 00000000 00000002
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffc2063b2ac1c0 00000000 fffff801eab33180-ffffc20635a91010 Success Error Cancel pending
	       \Driver\xusb22	nt!PopRequestCompletion
			Args: 00051100 00000001 00000001 00000002
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffc20635a91010    

			Args: 00000000 00000000 00000000 00000000

Gosh that seems like a seriously odd thing to cause a BSOD, thanks for your help i'll look into it.