Dell Vostro 3525 - BSOD DRIVER_POWER_STATE_FAILURE (9f) - Ryzen 5 5625U

Question

Hi,

Today i have updated my pc and was running some updates and suddenly it became unresponsive when in opened AMD Adrenaline Edition and had to sign out and when it bsoded.

This is the 2nd time i am having this issue and really frustrating. Can you please check the Dump analysis and let me know the cause /issue and if any additional details required.

Loading Dump File [C:\Windows\Minidump\040623-10609-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Machine Name:
Kernel base = 0xfffff804`3c000000 PsLoadedModuleList = 0xfffff804`3cc133c0
Debug session time: Thu Apr  6 10:09:10.217 2023 (UTC + 5:30)
System Uptime: 4 days 22:11:24.934
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
..............................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`3c4292a0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffbe8b`ff45f790=000000000000009f
2: kd> dx KiBugCheckDriver
Type information missing error for KiBugCheckDriver
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: KiBugCheckDriver                              ***
***                                                                   ***
*************************************************************************
Error: Unable to bind name 'KiBugCheckDriver'
2: 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: ffff98884eae1d50, Physical Device Object of the stack
Arg3: ffffbe8bff45f7d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff988854b9a010, The blocked IRP

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2765

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 6376

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x9f

    Key  : Bugcheck.Code.Register
    Value: 0x9f

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Timestamp
    Value: 2022-05-06T12:50:00Z

    Key  : WER.OS.Version
    Value: 10.0.22621.1


FILE_IN_CAB:  040623-10609-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffff98884eae1d50

BUGCHECK_P3: ffffbe8bff45f7d8

BUGCHECK_P4: ffff988854b9a010

DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: ffff98884eddade0

IMAGE_NAME:  ACPI.sys

MODULE_NAME: ACPI

FAULTING_MODULE: fffff8043f090000 ACPI

BLACKBOXACPI: 1 (!blackboxacpi)


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffbe8b`ff45f788 fffff804`3c5714d6     : 00000000`0000009f 00000000`00000003 ffff9888`4eae1d50 ffffbe8b`ff45f7d8 : nt!KeBugCheckEx
ffffbe8b`ff45f790 fffff804`3c5713ac     : 00000000`00000004 ffffc180`7ab91180 ffffc180`7ab91180 00000000`00000000 : nt!PopIrpWatchdogBugcheck+0x122
ffffbe8b`ff45f810 fffff804`3c2312fb     : ffff9888`55927690 ffff9888`4ecfa000 ffffbe8b`ff45fab8 00000000`00000002 : nt!PopIrpWatchdog+0xc
ffffbe8b`ff45f840 fffff804`3c232a76     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00f7aa32 : nt!KiProcessExpiredTimerList+0x1eb
ffffbe8b`ff45f970 fffff804`3c42e09e     : 00000000`00000000 ffffc180`7ab91180 ffff9888`4eab9040 ffff9888`788f7080 : nt!KiRetireDpcList+0xed6
ffffbe8b`ff45fc00 00000000`00000000     : ffffbe8b`ff460000 ffffbe8b`ff459000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


IMAGE_VERSION:  10.0.22621.1537

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  0x9F_3_amdi2c_DEV_AMDI0010_IMAGE_ACPI.sys

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {4a47bf2d-33a2-c37b-edc8-078440157129}

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

2: kd> dx KiBugCheckDriver
Unimplemented error for KiBugCheckDriver
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: KiBugCheckDriver                              ***
***                                                                   ***
*************************************************************************
Error: Unable to bind name 'KiBugCheckDriver'
2: kd> dt nt!_TRIAGE_9F_POWER ffff988854b9a010
   +0x000 Signature        : 6
   +0x002 Revision         : 0x3a0
   +0x008 IrpList          : (null) 
   +0x010 ThreadList       : (null) 
   +0x018 DelayedWorkQueue : (null) 
   +0x020 DelayedIoWorkQueue : 0xffff9888`54b9a030 _TRIAGE_EX_WORK_QUEUE
2: kd> !irp ffff988854b9a010
Irp is active with 6 stacks 3 is current (= 0xffff988854b9a170)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     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
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0  1 ffff98884eae1d50 00000000 00000000-00000000    pending
	       \Driver\ACPI
			Args: 00000000 00000001 00000004 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff9888545c8c20 00000000 fffff8045d5351c0-6777aba70738 Success Error Cancel pending
	      Unable to load image \SystemRoot\System32\drivers\amdi2c.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amdi2c.sys
 \Driver\amdi2c	SpbCx!CScxController::_OnDxIrpComplete
			Args: 00000000 00000001 00000004 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffff9888545c8c20 00000000 fffff8043c3a6ac0-ffff988855927658 Success Error Cancel pending
	       \Driver\amdi2c	nt!PopRequestCompletion
			Args: 00000000 00000001 00000004 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffff988855927658    

			Args: 00000000 00000000 00000000 00000000
2: kd> !devstack ffff98884eae1d50
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffff9888545c8c20  \Driver\amdi2c     ffff98885458fbb0  InfoMask field not found for _OBJECT_HEADER at ffff9888545c8bf0

> ffff98884eae1d50  \Driver\ACPI       ffff98884eb1e010  Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode ffff98884ede6bb0 :
  DeviceInst is "ACPI\AMDI0010\3"
  ServiceName is "amdi2c"

Thanks,

Aditya

SanoShaker · Answer

try chipset driver from amd website

kjyothiraditya · Answer

today another BSOD occurred. attaching minidump file location from OneDrive for analysis.  Minidump

Mary G · Answer

You are installing the wrong drivers. Dell customizes all laptop drivers and updates from all manufacturers-AMD, Intel, etc. so they work on the Dell motherboard. Get all drivers from your Dell driver downloads page.

kjyothiraditya · Answer

i am under warranty. I update using the Dell Driver updates application and Win 11 updates. Using both are a mess and one overwrites the other. Also, the AMD support page is not helpful and don't provide adequate information.

kjyothiraditya · Answer

yes, i install using 'Dell Update' and all are up to date with OS also.

kjyothiraditya · Answer

Really dont know if its OS issue or Driver issue or something else.

Here are the links which talk about similar issues:

Blue Screen with Error Code 0x0000009F | Dell India

Your Computer Stops with a 0x9F Blue Screen Because of a Windows 11 Race Condition | Dell India

Vostro

Dell Vostro 3525 - BSOD DRIVER_POWER_STATE_FAILURE (9f) - Ryzen 5 5625U

Was this post helpful?