driver_power_state_failure BOD but...

[zignblowfly]

Hey everyone!

 

So I recently build an AMD system. Everything is new but the graphics card. I was planning on updating to a 30 series Invidia but we all know how that shitshow went. So the motherboard, Gigabyte Aorus Master x570, CPU, Ryzen 7 3800x, and western digital black m.2 WDS100T3Xoc-00SJGO are all new. I also installed an m.2 from my old system which is an ADATA SX6000LNP. I have 32GB of Crucial Ballistix UDIMM 32GB( 8GB x 4) running at 3200mhz even though its rated at 3600mhz. So the main issue is when I start my system up it boots fine and runs for a couple of minutes then the BOD for driver_power_state_failure pops up. I restart my system then everything runs fine for the duration that the machine is running. So while this isn't critical it is damn frustrating to have a brand new system that has to be restarted shortly after initial boot. I have tried to troubleshoot what exactly is causing the driver_power_state_failure but have had no luck. If anyone has any ideas they could throw my way to stop the irritation of having to restart every time I boot would be AWESOME and MUCH appreciated!!! Also while I'm throwing that out there I might as well throw this as well but this is not a big deal. So I have Crucial Ballistix UDIMM 3600 4 x 8GB I can only run it at 3200. I tried using the XMP and it worked great with 16GB but once I installed the other 16GB it started to cause my system to stutter during game play. I made sure I bought the exact same type of DIMMs as the original 16GB and it ran smooth at first but then started to stutter. I tried testing the DIMMs individually and they all run fine just as long as I don't run them with XMP. Any ideas would be much appreciated but its not that big of a deal. Even the driver_power_state_failure is not that big of a deal because once I restart the  system it runs like a champ its just damn frustrating to have issues with a system that should be running like new. Thank you all for any help you can throw my way. Thanks Ladies and Gentleman for any help you give me... Z

[Radium_Angel]

14 minutes ago, zignblowfly said:

Thanks Ladies and Gentleman for any help you give me... Z

If you are getting a Blue Screen of Death, there should be minidumps (aka crash dumps) on your system, if you post them here (or PM them to me) I can deconstruct and pinpoint the error for you. 

[bmx6454]

check event viewer to see if it provides more details on the bsods. as far as the ram, buying an identical part # set doesn't guarantee they are identical to a T. have you tried running them at stock speeds?

[zignblowfly]

2 minutes ago, bmx6454 said:

check event viewer to see if it provides more details on the bsods. as far as the ram, buying an identical part # set doesn't guarantee they are identical to a T. have you tried running them at stock speeds?

yes sir at 3200 they run great but they are "listed" as 3600. at 3600 they stutter. In event viewer where do I find the BSOD details? Thanks for the response!

[zignblowfly]

5 minutes ago, Radium_Angel said:

If you are getting a Blue Screen of Death, there should be minidumps (aka crash dumps) on your system, if you post them here (or PM them to me) I can deconstruct and pinpoint the error for you. 

That would be great and I can send it to you but how do I go about finding the minidumps? thanks for the response!!

[Radium_Angel]

8 minutes ago, zignblowfly said:

That would be great and I can send it to you but how do I go about finding the minidumps? thanks for the response!!

Looking for the minidumps specifically

https://kb.datto.com/hc/en-us/articles/115004753183-SIRIS-ALTO-and-NAS-Datto-Windows-Agent-How-to-retrieve-memory-dump-files#:~:text=The memory dump file is,folder is %SystemRoot%\Minidump.

 

[zignblowfly]

30 minutes ago, Radium_Angel said:

Looking for the minidumps specifically

https://kb.datto.com/hc/en-us/articles/115004753183-SIRIS-ALTO-and-NAS-Datto-Windows-Agent-How-to-retrieve-memory-dump-files#:~:text=The memory dump file is,folder is %SystemRoot%\Minidump.

 

I figured out how to save the dumpfile now I have to shutdown the desktop and wait a little bit to restart to see if it will give me a BSOD to record the file then ill send it to you.

[zignblowfly]

57 minutes ago, Radium_Angel said:

Looking for the minidumps specifically

https://kb.datto.com/hc/en-us/articles/115004753183-SIRIS-ALTO-and-NAS-Datto-Windows-Agent-How-to-retrieve-memory-dump-files#:~:text=The memory dump file is,folder is %SystemRoot%\Minidump.

 

Alright so i was able to capture the small dump and had to download WinDbg Preview to be able to open the file. i tried to save what the file reads so i could send it to you but either I am doing it wrong or it wont let me share or save it. so here is what the file reads in WinDbg Preview...

 

Bug Check 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: ffffbd079b577d80, Physical Device Object of the stack

Arg3: fffffb0e900a7850, nt! TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack

Arg4: ffffbd07a9887540, The Blocked IRP

 

Debugging Details

KEY_VALUES_STRING:  1

 

Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on Beast

 

Key: Analysis. DebugData

Value: CreateObject

 

Key:Analysis. DebugModel

Value: CreateObject

 

Key: Analysis.Elapsed.mSec

Value: 3477

 

Key: Analysis. Memory.CommitPeak.Mb

Value: 111

 

Key : Analysis.System

Value: CreateObject

 

ADDITIONAL_XML: 1

 

OS_BUILD_LAYERS: 1

 

DUMP_FILE_ATTRIBUTES: 0X8

    Kernal Generated Triage Dump

 

BUGCHECK_CODE: 9f

 

BUGCHECK_P1: 3

 

BUGCHECK_P2: ffffbd079b577d80

 

BUGCHECK_P3: fffffb0e900a7850

 

BUGCHECK_P4: ffffbd07a9887540

 

DRVPOWERSTATE_SUBCODE: 3

 

IMAGE_NAME: UsbHub3.sys

 

MODULE_NAME: UsbHub3.sys

 

FAULTING_MODULE: fffff8038e0100000 UsbHub3

 

BLACKBOXSD: 1 (!blackboxbsd)

 

BLACKBOXNTFS: 1 (blackboxntfs)

 

BLACKBOXPNP: 1 (!blackboxpnp)

 

BLACKBOXWINLOGON: 1

 

CUSTOMER_CRASH_COUNT: 1

 

PROCESS_NAME: System

 

STACK_TEXT:

fffffb0e'900a7818 fffff803'7af5f4b7   : 00000000'0000009f 00000000'00000003 ffffbd07' 9b577d80 fffffb0e'900a7850 : nt!KeBugCheckEx

fffffb0e'900a7820 fffff803'7af5f3d1  :ffffbd07'aa49dd20 00000000'00000000 ffffbd07'a3ccdb00 00000000'00000000 :nt!PopIrpWatchdogBugcheck+0xdf

fffffb0e'900a7890 fffff803'7acc3ee2  : ffffbd07'aa49dd58 ffffe481'd2940180 ffffbd07'00000002 : nt!PopIrpWatchdog+0x31

fffffb0e'900a78e0 fffff803'7ace910d : 00000000'00000000 00000000'00000000 00000000'00140001 00000000'003e1a6 : nt!KiProcessExpiredTimerList+0x172

fffffb0e'900a79d0 fffff803'7adf7a0e : ffffffff'00000000 ffffe481'd2940180 ffffe481'd2940180 ffffe481'd294b440 ffffbd07'a27df080 : nt!KiRetireDpcList+0x5dd

fffffb0e'900a7c60 00000000'00000000 : fffffb0e'900a8000 fffffb0e'900a2000 00000000'00000000 00000000'00000000 : nt!KiIdleLoop+0x9e

 

IMAGE_VERSION: 10.0.19041.264

STACK_COMMAND: .thread  ; .cxr ; kb

FAILURE_BUCKET_ID: 0x9f_3_Focusriteusb_IMAGE_UsbHub3.sys

OSPLATFORM_TYPE: X64

OSNAME: Windows 10

FAILURE_ID_HASH: {4b2e2f7c-1fb8-94ff-a902-832a00ea8b47}

Followup: MachineOwner

 

 

so thats everything the file said. I am sure you probrably didnt need all of that but I wanted to be thourough since your helping me. From what I read I am thinking it may be my Focusrite Scarlett USB audio interface? Did I read that right? either way thanks again for your help and I hope the message above helps.... Z

[Radium_Angel]

9 hours ago, zignblowfly said:

able to open the file.

Thank you for the dump, but what I need is the actual file itself, you can upload it to a message here as an attachment and I can download it and work on it.

9 hours ago, zignblowfly said:

FAILURE_BUCKET_ID: 0x9f_3_Focusriteusb_IMAGE_UsbHub3.sys

That is the module that failed, but that might not be the actual cause, just the end result.

9 hours ago, zignblowfly said:

TRIAGE_9F_POWER

Look into this, that seems to be the key, if I had my guess, I'd say something attached to the USB ports is drawing too much power (or not enough)

[zignblowfly]

4 hours ago, Radium_Angel said:

Thank you for the dump, but what I need is the actual file itself, you can upload it to a message here as an attachment and I can download it and work on it.

That is the module that failed, but that might not be the actual cause, just the end result.

Look into this, that seems to be the key, if I had my guess, I'd say something attached to the USB ports is drawing too much power (or not enough)

I'll try to download the file to this site so you can look at it. I tried to send the file through my email because the issue is on my desktop and I'm talking to you with my laptop. I'll log into the forum on my desktop and see if I can't post the file. I did unplug the Focusrite USB audio interface before my current boot and so far no BSOD. Either way if you could look at the file and let me know what else, if anything i need to do that would be awesome. I'm going to try to post it now. Thanks again for the help!

[zignblowfly]

11 minutes ago, zignblowfly said:

I'll try to download the file to this site so you can look at it. I tried to send the file through my email because the issue is on my desktop and I'm talking to you with my laptop. I'll log into the forum on my desktop and see if I can't post the file. I did unplug the Focusrite USB audio interface before my current boot and so far no BSOD. Either way if you could look at the file and let me know what else, if anything i need to do that would be awesome. I'm going to try to post it now. Thanks again for the help!

Hope this helps. Thanks!

102320-7546-01.dmp

[Radium_Angel]

50 minutes ago, zignblowfly said:

I'll try to download the file to this site so you can look at it. I tried to send the file through my email because the issue is on my desktop and I'm talking to you with my laptop. I'll log into the forum on my desktop and see if I can't post the file. I did unplug the Focusrite USB audio interface before my current boot and so far no BSOD. Either way if you could look at the file and let me know what else, if anything i need to do that would be awesome. I'm going to try to post it now. Thanks again for the help!

I see the file, give me some to dig through it.

Cheers mate!

[Radium_Angel]

57 minutes ago, zignblowfly said:

Hope this helps. Thanks!

102320-7546-01.dmp 2.4 MB · 0 downloads

Ok, it's the usb driver stack, that went stupid because the Focus Rite device wouldn't let go of the IRP power state for other devices

Basically, that Focus Rite thing probably needs to be plugged into a powered USB hub, it seems to be drawing more power than it should.

[zignblowfly]

5 hours ago, Radium_Angel said:

Ok, it's the usb driver stack, that went stupid because the Focus Rite device wouldn't let go of the IRP power state for other devices

Basically, that Focus Rite thing probably needs to be plugged into a powered USB hub, it seems to be drawing more power than it should.

Ok that makes sense. Ever since I unplugged the device I have had no blue screens...YAY! I'll try to plug into a powered slot. Hey thanks for the help! I REALLY do appreciate it.  I feel like I have a good understanding of computers but I am no wizard and am still learning every day. Thanks again for your help and if there is ever anything I can help you with PLEASE let me know! Z

[Radium_Angel]

13 hours ago, zignblowfly said:

Ok that makes sense. Ever since I unplugged the device I have had no blue screens...YAY! I'll try to plug into a powered slot. Hey thanks for the help! I REALLY do appreciate it.  I feel like I have a good understanding of computers but I am no wizard and am still learning every day. Thanks again for your help and if there is ever anything I can help you with PLEASE let me know! Z

Glad we got it figured out. Cheers Mate!