Question Having BSOD once everytime i turn on PC

ammarzool

Reputable
Dec 2, 2014
39
0
4,530
0
Hello ,
need help with my BSOD its starting to get annoying ....
i get a BSOD just once everytime i turn on my PC ... then it restart and everything goes normally i don't get it until i turn it on the next day
the error is Driver Power State Failure



My specs:

Graphics Card: Rx 580 8GB

Processor: Ryzen 5 2600

Memory: 16GB RAM

Operating System: Windows 10 PRO

Motherboard: B450 Tomahawk





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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-MTLO2KL

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 25

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

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffd80d67385df0

BUGCHECK_P3: ffffd70d7e48b8d0

BUGCHECK_P4: ffffd80d6d0c8450

DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: ffffd80d678bf060

IMAGE_NAME: UsbHub3.sys

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff8066ea90000 UsbHub3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


PROCESS_NAME: System

STACK_TEXT:
ffffd70d7e48b898 fffff80663d8ae36 : 000000000000009f 0000000000000003 ffffd80d67385df0 ffffd70d7e48b8d0 : nt!KeBugCheckEx
ffffd70d7e48b8a0 fffff80663d8ad42 : ffffd80d6c3046e0 ffffd70d7e48ba10 000000000000007b ffffaf81cead7180 : nt!PopIrpWatchdogBugcheck+0xea
ffffd70d7e48b910 fffff80663b31119 : ffffaf81ceae7300 00000000000000ff ffffd70d7e48bb18 0000000000000008 : nt!PopIrpWatchdog+0x22
ffffd70d7e48b960 fffff80663b32067 : 0000000000000008 0000000000989680 ffffaf81ceae7300 000000000000001a : nt!KiProcessExpiredTimerList+0x159
ffffd70d7e48ba50 fffff80663c70a7a : ffffffff00000000 ffffaf81cead7180 0000000000000000 ffffaf81ceae7300 : nt!KiRetireDpcList+0x4a7
ffffd70d7e48bc60 0000000000000000 : ffffd70d7e48c000 ffffd70d7e486000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x5a


IMAGE_VERSION: 10.0.17763.1

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_IMAGE_UsbHub3.sys

OS_VERSION: 10.0.17763.1

BUILDLAB_STR: rs5_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {58bbe6fe-0b43-accc-1beb-340d4227ae9c}

Followup: MachineOwner
 
Last edited:

axe0axe0

Respectable
Jun 5, 2017
842
20
2,165
95
Hi ammarzool,

Seeing you opened one of the dumps, could you run the command '!irp ffffd80d6d0c8450 1' and post the output. That allows us to look into the blocked IRP hopefully showing us what driver is causing the problem.
Usually we can already see the driver in the blocked IRP in the verbose analysis, but the driver it shows, usbhub3.sys, merely gives an indication that it's a USB related issue.
 

ammarzool

Reputable
Dec 2, 2014
39
0
4,530
0
ok got it



Irp is active with 15 stacks 12 is current (= 0xffffd80d6d0c8838)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
Flags = 00000000
ThreadListEntry.Flink = ffffd80d6d0c8470
ThreadListEntry.Blink = ffffd80d6d0c8470
IoStatus.Status = 00000000
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = ffffd80d6d0c84c8
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = ffffd80d677a2a08
Tail.Overlay.ListEntry.Blink = fffff80663ed1800
Tail.Overlay.CurrentStackLocation = ffffd80d6d0c8838
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
cmd flg cl Device File Completion-Context
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffffd80d67385df0 00000000 fffff8066eaa82c0-ffffd80d674ae0d0 Success Error Cancel pending
\Driver\USBHUB3 UsbHub3!HUBPDO_WdmPnpPowerIrpCompletionRoutineForAsynchronousCompletion
Args: 00051100 00000001 00000001 00000002
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffffd80d67385df0 00000000 00000000-00000000 pending
\Driver\USBHUB3
Args: 00051100 00000001 00000001 00000002
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffffd80d6731e630 00000000 fffff80663c23df0-ffffd80d6c3046e0 Success Error Cancel pending
\Driver\usbccgp nt!PopRequestCompletion
Args: 00051100 00000001 00000001 00000002
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-ffffd80d6c3046e0

Args: 00000000 00000000 00000000 00000000
 

axe0axe0

Respectable
Jun 5, 2017
842
20
2,165
95
Looks like a Razer device may be causing issues based on the VID.
Code:
8: kd> !irp ffffd80d`6d0c8450 1
Irp is active with 15 stacks 12 is current (= 0xffffd80d6d0c8838)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
Flags = 00000000
ThreadListEntry.Flink = ffffd80d6d0c8470
ThreadListEntry.Blink = ffffd80d6d0c8470
IoStatus.Status = 00000000
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000   
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = ffffd80d6d0c84c8
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = ffffd80d677a2a08
Tail.Overlay.ListEntry.Blink = fffff80663ed1800
Tail.Overlay.CurrentStackLocation = ffffd80d6d0c8838
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     cmd  flg cl Device   File     Completion-Context

.......

            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffd80d67385df0 00000000 fffff8066eaa82c0-ffffd80d674ae0d0 Success Error Cancel pending
           \Driver\USBHUB3    UsbHub3!HUBPDO_WdmPnpPowerIrpCompletionRoutineForAsynchronousCompletion
            Args: 00051100 00000001 00000001 00000002
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffd80d67385df0 00000000 00000000-00000000    pending
           \Driver\USBHUB3
            Args: 00051100 00000001 00000001 00000002
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffd80d6731e630 00000000 fffff80663c23df0-ffffd80d6c3046e0 Success Error Cancel pending
           \Driver\usbccgp    nt!PopRequestCompletion
            Args: 00051100 00000001 00000001 00000002
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffd80d6c3046e0    

            Args: 00000000 00000000 00000000 00000000
8: kd> !devobj ffffd80d67385df0
Device object (ffffd80d67385df0) is for:
 Cannot read info offset from nt!ObpInfoMaskToOffset
 \Driver\USBHUB3 DriverObject ffffd80d678bf060
Current Irp 00000000 RefCount 0 Type 00000022 Flags 00003044
SecurityDescriptor ffffc48cc9128aa0 DevExt ffffd80d62bd6d80 DevObjExt ffffd80d67385f68 DevNode ffffd80d67503010 
ExtensionFlags (0000000000)  
Characteristics (0x00000100)  FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffd80d6745ee10 \Driver\ACPI
Device queue is not busy.
8: kd> !devstack ffffd80d67385df0
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffffd80d6731e630  \Driver\usbccgp    ffffd80d6731e780  InfoMask field not found for _OBJECT_HEADER at ffffd80d6731e600

  ffffd80d6745ee10  \Driver\ACPI       ffffd80d62b947e0  InfoMask field not found for _OBJECT_HEADER at ffffd80d6745ede0

> ffffd80d67385df0  \Driver\USBHUB3    ffffd80d62bd6d80  Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode ffffd80d67503010 :
  DeviceInst is "USB\VID_1532&PID_0227\6&35466de&0&6"
  ServiceName is "usbccgp"
 

Ketchup79

Notable
Aug 7, 2019
1,287
118
1,090
57
Same as the last dumpm DRIVER_POWER_STATE_FAILURE. The driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time. The failure is pointing to usbhub3.sys. If you have the latest drivers for those devices I recommend you go to the MSI website and install all the latest drivers for your motherboard.
 

ammarzool

Reputable
Dec 2, 2014
39
0
4,530
0
someone suggested i do this .... i did it , don't know if it will help tho as the BSOD only comes when i turn on my PC can't just test it right away

Open the Device Manager and uncheck the "Allow the computer to turn off this device to save power" on all of the USB Hub / USB Root Hubs. When finished, disable also the USB suspend settings in the power options.
 

Ketchup79

Notable
Aug 7, 2019
1,287
118
1,090
57
I found this which may be applicable:

i did some research on Razer insider and found that the Huntsman Elite requires that you plug it into a 2.0 usb and not a 3.1. I did this and Razer Synapse worked immediately better. Didnt slow or lag at all. I didnt know what usb was 2.0 so i just plugged it into the front of my computer and its working perfect.
Your motherboard has:
6 x USB 2.0 (High-speed USB) ports (2 Type-A ports on the back panel, 4 ports available through the internal USB 2.0 connectors)
 

ammarzool

Reputable
Dec 2, 2014
39
0
4,530
0
I found this which may be applicable:


i did some research on Razer insider and found that the Huntsman Elite requires that you plug it into a 2.0 usb and not a 3.1. I did this and Razer Synapse worked immediately better. Didnt slow or lag at all. I didnt know what usb was 2.0 so i just plugged it into the front of my computer and its working perfect.
Your motherboard has:

6 x USB 2.0 (High-speed USB) ports (2 Type-A ports on the back panel, 4 ports available through the internal USB 2.0 connectors)

i will try that , thx .... altho i have my keyboard since 6-7 months and its in the same USB port since then
 
Last edited:

ammarzool

Reputable
Dec 2, 2014
39
0
4,530
0
altho today i got a different BSOD when i turned my PC
Power State Failure
before it used to say Driver Power State Failure .... dunno if something changed but i'll upload it so u can take a look at it ^^



**edit: nvm its damaged ... the minidumb has 0kb on size and error when i try to open it so no use i guess
 
Thread starter Similar threads Forum Replies Date
mrshrir Windows 10 1

ASK THE COMMUNITY

TRENDING THREADS