DRIVER_POWER_STATE_FAILURE

Question

Got DRIVER_POWER_STATE_FAILURE BSOD. What cause it? I did use Windbg to analyse minidump and got:
************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true

-- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25921.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\krasa\Desktop\082823-175687-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Kernel base = 0xfffff8065f200000 PsLoadedModuleList = 0xfffff8065fe2a3d0 Debug session time: Mon Aug 28 15:59:03.486 2023 (UTC + 5:00) System Uptime: 0 days 8:03:48.195 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ... Loading User Symbols Unable to read LDR_DATA_TABLE_ENTRY at 000002d3`3a5c29f0 - Win32 error 0n30

Loading unloaded module list .......... WARNING: .reload failed, module list may be incomplete For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff8065f5fcc40 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff8066587bb70=000000000000009f 0: 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: ffffbd8d26e56050, Physical Device Object of the stack Arg3: fffff8066587bba0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffbd8d2901b410, The blocked IRP

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 2562

Key  : Analysis.Elapsed.mSec
Value: 29556

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

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

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

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

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

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

Key  : Bugcheck.Code.LegacyAPI
Value: 0x9f

Key  : Failure.Bucket
Value: 0x9F\_3\_disk\_IMAGE\_storahci.sys

Key  : Failure.Hash
Value: {c3191f76-a0c6-cba7-b63d-40337d053563}

Key  : WER.OS.Branch
Value: vb\_release

Key  : WER.OS.Version
Value: 10.0.19041.1

BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffbd8d26e56050

BUGCHECK_P3: fffff8066587bba0

BUGCHECK_P4: ffffbd8d2901b410

FILE_IN_CAB: 082823-175687-01.dmp

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: storahci.sys

MODULE_NAME: storahci

FAULTING_MODULE: fffff80664a30000 storahci

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Telegram.exe

DPC_STACK_BASE: FFFFF8066587BFB0

STACK_TEXT:
fffff8066587bb68 fffff8065f764a27 : 000000000000009f 0000000000000003 ffffbd8d26e56050 fffff8066587bba0 : nt!KeBugCheckEx fffff8066587bb70 fffff8065f764941 : ffffbd8d2901f698 fffff8066587bcc8 0000000000000000 000000000010c269 : nt!PopIrpWatchdogBugcheck+0xdf fffff8066587bbe0 fffff8065f44db52 : ffffbd8d2901f6d0 fffff8065d7b1180 fffff8066587be68 0000000000000001 : nt!PopIrpWatchdog+0x31 fffff8066587bc30 fffff8065f44cbcd : fffff8065d7b1180 0000000000000000 0000000000000000 000000000010c269 : nt!KiProcessExpiredTimerList+0x172 fffff8066587bd20 fffff8065f605135 : 0000000000000000 fffff8065d7b1180 fffff8065fef3ac0 ffffa28b514fb3b0 : nt!KiRetireDpcList+0x5dd fffff8066587bfb0 fffff8065f604f20 : fffff8065f5f8cf0 fffff8065f52a8aa 0000000000000000 ffffa28b514fb278 : nt!KxRetireDpcList+0x5 ffffa28b514fb020 fffff8065f6046a5 : ffffa28b514fb3b0 fffff8065f5ff421 000000000002624e fffff8065f440062 : nt!KiDispatchInterruptContinue ffffa28b514fb050 fffff8065f5ff421 : 000000000002624e fffff8065f440062 0000000000000000 ffffce0a1ae51d60 : nt!KiDpcInterruptBypass+0x25 ffffa28b514fb060 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1

IMAGE_VERSION: 10.0.19041.3516

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_disk_IMAGE_storahci.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c3191f76-a0c6-cba7-b63d-40337d053563}

Followup: MachineOwner

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

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 2515

Key  : Analysis.Elapsed.mSec
Value: 2676

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

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

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

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

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

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

Key  : Bugcheck.Code.LegacyAPI
Value: 0x9f

Key  : Failure.Bucket
Value: 0x9F\_3\_disk\_IMAGE\_storahci.sys

Key  : Failure.Hash
Value: {c3191f76-a0c6-cba7-b63d-40337d053563}

Key  : WER.OS.Branch
Value: vb\_release

Key  : WER.OS.Version
Value: 10.0.19041.1

BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffbd8d26e56050

BUGCHECK_P3: fffff8066587bba0

BUGCHECK_P4: ffffbd8d2901b410

FILE_IN_CAB: 082823-175687-01.dmp

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: storahci.sys

MODULE_NAME: storahci

FAULTING_MODULE: fffff80664a30000 storahci

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Telegram.exe

DPC_STACK_BASE: FFFFF8066587BFB0

STACK_TEXT:
fffff8066587bb68 fffff8065f764a27 : 000000000000009f 0000000000000003 ffffbd8d26e56050 fffff8066587bba0 : nt!KeBugCheckEx fffff8066587bb70 fffff8065f764941 : ffffbd8d2901f698 fffff8066587bcc8 0000000000000000 000000000010c269 : nt!PopIrpWatchdogBugcheck+0xdf fffff8066587bbe0 fffff8065f44db52 : ffffbd8d2901f6d0 fffff8065d7b1180 fffff8066587be68 0000000000000001 : nt!PopIrpWatchdog+0x31 fffff8066587bc30 fffff8065f44cbcd : fffff8065d7b1180 0000000000000000 0000000000000000 000000000010c269 : nt!KiProcessExpiredTimerList+0x172 fffff8066587bd20 fffff8065f605135 : 0000000000000000 fffff8065d7b1180 fffff8065fef3ac0 ffffa28b514fb3b0 : nt!KiRetireDpcList+0x5dd fffff8066587bfb0 fffff8065f604f20 : fffff8065f5f8cf0 fffff8065f52a8aa 0000000000000000 ffffa28b514fb278 : nt!KxRetireDpcList+0x5 ffffa28b514fb020 fffff8065f6046a5 : ffffa28b514fb3b0 fffff8065f5ff421 000000000002624e fffff8065f440062 : nt!KiDispatchInterruptContinue ffffa28b514fb050 fffff8065f5ff421 : 000000000002624e fffff8065f440062 0000000000000000 ffffce0a1ae51d60 : nt!KiDpcInterruptBypass+0x25 ffffa28b514fb060 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1

IMAGE_VERSION: 10.0.19041.3516

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_disk_IMAGE_storahci.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c3191f76-a0c6-cba7-b63d-40337d053563}

Followup: MachineOwner

0: kd> lmvm storahci Browse full module list start end module name fffff80664a30000 fffff80664a62000 storahci # (pdb symbols) C:\ProgramData\Dbg\sym\storahci.pdb\AF47274BC9366B8C8556F63640CA08583\storahci.pdb Loaded symbol image file: storahci.sys Mapped memory image file: C:\ProgramData\Dbg\sym\storahci.sys\6A1B92AB32000\storahci.sys Image path: \SystemRoot\System32\drivers\storahci.sys Image name: storahci.sys Browse all global symbols functions data Image was built with /Brepro flag. Timestamp: 6A1B92AB (This is a reproducible build file hash, not a timestamp) CheckSum: 000386A7 ImageSize: 00032000 File version: 10.0.19041.3516 Product version: 10.0.19041.3516 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.7 Driver File date: 00000000.00000000 Translations: 0409.04b0 Information from resource tables: CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: storahci.sys OriginalFilename: storahci.sys ProductVersion: 10.0.19041.3516 FileVersion: 10.0.19041.3516 (WinBuild.160101.0800) FileDescription: MS AHCI Storport Miniport Driver LegalCopyright: © Microsoft Corporation. All rights reserved.

Answer 1

Glad to help!

Answer 2

I did have latest chipset drivers. I didn't update the BIOS, I was afraid it would get worse. Crashes are rare, I just wanted to understand the cause. If there will be further problems I think I will have to update BIOS. Thanks for the reply!

Answer 3

Your minidump file indicates it is the chipset drivers causing your PC to crash.

Go to the support page for your PC or Motherboard on the manufacturers website, then from there, download and install the version of chipset drivers they recommend and while there, check for any BIOS update that may need to be installed

Answer 4

Thx, there is minidump https://www.dropbox.com/scl/fi/om8x1u2ivxfa7lm30vtrj/082823-175687-01.rar?rlkey=8cvyjjqq1izk3c1grg9esakb5&dl=0

Answer 5

Hi, I am Dave, I will help you with this.

Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive, DropBox... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so we can take a look for you.