Question BSOD help!

[slither.io]

I've had the computer for a little over a month and randomly (about ever 3-5 days). I will get the BSOD and my computer will restart. Sometimes it boots backup just fine the other times I have to go in and remove the battery connector and then reboot it, and it will work for the 3-5 days. This isn't a new computer but just recently started happening. I ran a Diagnostic tool on all the hardware and it all passed. I looked into a couple other people who were having similar issues and they all have been talking about the Graphics card on the computer and that the new driver for this is causing the issue. I pulled the DMP file, but not entirely sure on how to tell what the root issue is. Any information would be very helpful.

Thank you in advance.





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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5936

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 8169

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x9f

Key : Bugcheck.Code.KiBugCheckData
Value: 0x9f

Key : Bugcheck.Code.Register
Value: 0x9f

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

BUGCHECK_P3: fffff80119c6f750

BUGCHECK_P4: ffffa608f2e17a30

DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: ffffa608f20d3de0

IMAGE_NAME: USBXHCI.SYS

MODULE_NAME: USBXHCI

FAULTING_MODULE: fffff80126060000 USBXHCI

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
fffff80119c6f718 fffff80114360447 : 000000000000009f 0000000000000003 ffffa608f20a5d10 fffff80119c6f750 : nt!KeBugCheckEx
fffff80119c6f720 fffff80114360361 : ffffa608f2e631e8 ffffa60919948080 0000000000000000 0000000001e14f41 : nt!PopIrpWatchdogBugcheck+0xdf
fffff80119c6f790 fffff8011403ffa2 : ffffa608f2e63220 fffff80111897180 fffff80119c6fa18 0000000000000000 : nt!PopIrpWatchdog+0x31
fffff80119c6f7e0 fffff801140a0eed : 0000000000000000 0000000000000000 0000000000140001 0000000001e14f41 : nt!KiProcessExpiredTimerList+0x172
fffff80119c6f8d0 fffff801141fb93e : 0000000000000000 fffff80111897180 fffff80114b27a00 ffffa6091e220080 : nt!KiRetireDpcList+0x5dd
fffff80119c6fb60 0000000000000000 : fffff80119c70000 fffff80119c69000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e


IMAGE_VERSION: 10.0.19041.1741

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_IMAGE_USBXHCI.SYS

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {eba525c1-ef53-2fc7-9af9-fdd9d996252b}

Followup: MachineOwner
---------

 

[Colif]

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

So it could be a USB device given the USB extensible host controller is showing as part of blame.
what usb devices do you have?
what are specs of PC?

 

[slither.io]

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

So it could be a USB device given the USB extensible host controller is showing as part of blame.
what usb devices do you have?
what are specs of PC?

The laptop is a Lenovo Thinkpad Type 20LB
I7 gen 8 vpro quad core
512 NVME
16GB DDR4 ram (I added an extra 8 GB DDR4 ram) 24GB total
Nvidia graphics card (not positive on the exact one)

Here is the link to the entire file
https://drive.google.com/file/d/1n6oVdXzR5XH9iLh6YLjV1qLs_ZpF6V29/view?usp=sharing

When I get the BSOD I sometimes have 2 monitors plugged into it and a wireless keyboard and mouse, but sometimes I have nothing plugged in.

Let me know if you need any other details.

 

[Colif]

i will ask a friend to check the file, he is likely asleep right now, but there is a chance someone else will answer while you wait.

 

[gardenman]

It appears you uploaded a larger file. Can you upload the minidumps instead?