Trying to solve Kernel Power Error 41

Question

Here is a copy of a memory dump my computer created.

4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

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: ffffbe0703098060, Physical Device Object of the stack Arg3: ffffa80f04e5f750, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffbe0709d44520, The blocked IRP

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 5733

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 5725

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

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

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

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: ffffbe0703098060

BUGCHECK_P3: ffffa80f04e5f750

BUGCHECK_P4: ffffbe0709d44520

DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: ffffbe06fbaafe30

IMAGE_NAME: xusb22.sys

MODULE_NAME: xusb22

FAULTING_MODULE: fffff80539980000 xusb22

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffa80f04e5f718 fffff8052a760157 : 000000000000009f 0000000000000003 ffffbe0703098060 ffffa80f04e5f750 : nt!KeBugCheckEx ffffa80f04e5f720 fffff8052a760071 : ffffbe06f9a518b8 0000000000000000 ffffbe07038c81f0 0000000000000000 : nt!PopIrpWatchdogBugcheck+0xdf ffffa80f04e5f790 fffff8052a481702 : ffffbe06f9a518f0 ffffab803b4dc180 ffffab803b4dc180 0000000000000002 : nt!PopIrpWatchdog+0x31 ffffa80f04e5f7e0 fffff8052a499add : 0000000000000000 0000000000000000 0000000000140001 0000000002f37973 : nt!KiProcessExpiredTimerList+0x172 ffffa80f04e5f8d0 fffff8052a5fb18e : 0000000000000000 ffffab803b4dc180 ffffab803b4e7240 ffffbe0703bab080 : nt!KiRetireDpcList+0x5dd ffffa80f04e5fb60 0000000000000000 : ffffa80f04e60000 ffffa80f04e59000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_IMAGE_xusb22.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b809f1f3-d516-d278-4cf4-f0faeccdd54d}

Followup: MachineOwner

4: kd> !drvobj ffffbe06fbaafe30 f Driver object (ffffbe06fbaafe30) is for: \Driver\xusb22

Driver Extension List: (id , addr) (fffff8052cdf4d50 ffffbe070a813e90)
Device Object list: ffffbe0703098060 ffffbe06fbc62510

DriverEntry: fffff80539992560 xusb22!FxDriverEntry DriverStartIo: 00000000 DriverUnload: fffff80539992510 xusb22!FxStubDriverUnload AddDevice: fffff8052cdf4b00 Wdf01000!FxDriver::AddDevice

Dispatch routines: [00] IRP_MJ_CREATE fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [01] IRP_MJ_CREATE_NAMED_PIPE fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [02] IRP_MJ_CLOSE fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [03] IRP_MJ_READ fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [04] IRP_MJ_WRITE fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [05] IRP_MJ_QUERY_INFORMATION fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [06] IRP_MJ_SET_INFORMATION fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [07] IRP_MJ_QUERY_EA fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [08] IRP_MJ_SET_EA fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [09] IRP_MJ_FLUSH_BUFFERS fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [0a] IRP_MJ_QUERY_VOLUME_INFORMATION fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [0b] IRP_MJ_SET_VOLUME_INFORMATION fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [0c] IRP_MJ_DIRECTORY_CONTROL fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [0d] IRP_MJ_FILE_SYSTEM_CONTROL fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [0e] IRP_MJ_DEVICE_CONTROL fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [0f] IRP_MJ_INTERNAL_DEVICE_CONTROL fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [10] IRP_MJ_SHUTDOWN fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [11] IRP_MJ_LOCK_CONTROL fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [12] IRP_MJ_CLEANUP fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [13] IRP_MJ_CREATE_MAILSLOT fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [14] IRP_MJ_QUERY_SECURITY fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [15] IRP_MJ_SET_SECURITY fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [16] IRP_MJ_POWER fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [17] IRP_MJ_SYSTEM_CONTROL fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [18] IRP_MJ_DEVICE_CHANGE fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [19] IRP_MJ_QUERY_QUOTA fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [1a] IRP_MJ_SET_QUOTA fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock [1b] IRP_MJ_PNP fffff8052cdaa710 Wdf01000!FxDevice::DispatchWithLock

Device Object stacks:

!devstack ffffbe0703098060 : !DevObj !DrvObj !DevExt ObjectName ffffbe0701b42060 \Driver\HidUsb ffffbe0701b421b0 _HID00000043 > ffffbe0703098060 \Driver\xusb22 ffffbe06fde82fc0 00000218 !DevNode ffffbe070e105cc0 : DeviceInst is "USB\VID_0955&PID_B400&IG_00\2&6e20533&1&00" ServiceName is "HidUsb"

!devstack ffffbe06fbc62510 : !DevObj !DrvObj !DevExt ObjectName > ffffbe06fbc62510 \Driver\xusb22 ffffbe06fb5417e0
ffffbe07073bdcd0 Unable to load image \SystemRoot\System32\drivers\nvvhci.sys, Win32 error 0n2 \Driver\nvvhci ffffbe07073bde20 00000217 !DevNode ffffbe070dcaecc0 : DeviceInst is "USB\Vid_0955&Pid_b400\1&1651c353&0&01" ServiceName is "xusb22"

Processed 2 device objects.

I have tried so many things to fix this, including updating all drivers, changing sleep settings, power settings, updating the BIOs and nothing. I think it could be a hardware problem but even there I have no clue what it would be as running CPU, GPU, and RAM benchmarks individually caused no crashes. Although when playing any sort of intensive videogame my system crashes. The only other thing I could think of would be my powersupply but after monitoring my voltages I don't exactly think that's the issue either.

Answer 1

OK.

Can you provide the memory dump via OneDrive or similar site.

Answer 2

Auggy,

I have unplugged my NVIDIA Controller and still getting the same issue, I am going to try and trigger a new memory dump as that file was generated on 4/7

Answer 3

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html https://www.elevenforum.com/t/bsod-posting-instructions.103/

Answer 4

Hi auggy!

Thank you so much for your reply! Do you think this could cause issues while the system is already booted and on? I play one game where I use the controller and it causes no issues but other games where I do not cause it to crash. I Will definitely try updating/removing the driver tonight,

Thank you!

Answer 5

Hi,

There appears to be similarities to the error reported in the following topic (your error also references the xusb22.sys and nvvhci.sys) :

https://answers.microsoft.com/en-us/windows/for...

Try updating the NVIDIA Shield Controller driver or remove the device.