Share via

Driver Power State Failure

Anonymous
2024-07-09T20:09:14+00:00

Hello there,

I am trying to figure out why one of our laptop went bluescreen. The error code was Driver Power State Failure. I tried research on the topic and seems like the information is documented in the dump file. I will attach the dump file here. Can you help me read it and provide me with more information regarding the cause?

Thanks!

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

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

Implicit thread is now ffffba05`d4195040

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2390

    Key  : Analysis.Elapsed.mSec
    Value: 7857

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x9f

    Key  : Bugcheck.Code.TargetModel
    Value: 0x9f

    Key  : Failure.Bucket
    Value: 0x9F_3_ks!CKsDevice::AcquireDevice

    Key  : Failure.Hash
    Value: {f0041349-03f4-2d36-ccf0-e8d26fb30fb6}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : WER.OS.Branch
    Value: ni_release_svc_prod3

    Key  : WER.OS.Version
    Value: 10.0.22621.2506

BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffba05c65a25f0

BUGCHECK_P3: fffff80548c0e0f8

BUGCHECK_P4: ffffba05c83cf6e0

FILE_IN_CAB:  070324-29281-01.dmp

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

DRVPOWERSTATE_SUBCODE:  3

FAULTING_THREAD:  ffffba05d4195040

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffcc08`f62feb30 fffff805`4365a265     : 00000000`00000000 00000000`00000000 ffffe586`29793dd0 00000000`00000000 : nt!KiSwapContext+0x76
ffffcc08`f62fec70 fffff805`4365c447     : 00000000`00000000 ffffe586`24944200 00000000`00000000 00000000`00000000 : nt!KiSwapThread+0xaa5
ffffcc08`f62fedc0 fffff805`4365e356     : ffffe586`00000000 fffff805`00000001 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x137
ffffcc08`f62fee70 fffff805`41a89b8b     : 00000000`00000004 ffffba05`caebe9a0 00000000`00000003 00000000`00000020 : nt!KeWaitForSingleObject+0x256
ffffcc08`f62ff210 fffff805`41a8fd08     : ffffba05`caebe9a0 00000000`00000004 ffffba05`c83cfbe8 ffffba05`c83cf6e0 : ks!CKsDevice::AcquireDevice+0x4b
ffffcc08`f62ff250 fffff805`41a8f982     : 00000000`00000000 ffffba05`c83cfbe8 ffffba05`caebe9a0 fffff805`41a4c0a0 : ks!CKsDevice::DispatchDeviceSetPowerIrp+0x1e8
ffffcc08`f62ff2b0 fffff805`4371a1b7     : ffffba05`00000001 ffffba05`c83cf6e0 ffffcc08`f62ff400 ffffba05`c83cfc30 : ks!CKsDevice::DispatchPower+0x332
ffffcc08`f62ff310 fffff805`43649b1d     : ffffba05`d3f5c001 ffffcc08`00000000 fffff805`4202c008 ffffba05`d3f5c4a8 : nt!IopPoHandleIrp+0x3b
ffffcc08`f62ff340 fffff805`4376dea9     : ffffba05`d3f5c030 fffff805`42027230 fffff805`00000020 ffffba05`b623c3c0 : nt!IofCallDriver+0x6d
ffffcc08`f62ff380 fffff805`420a157e     : ffffba05`00000002 fffff805`00000001 00000000`00000000 ffffba05`b623c610 : nt!PoCallDriver+0x9
ffffcc08`f62ff3b0 fffff805`420a1133     : ffffba05`d4195040 00000000`00000000 ffffba05`00000000 ffffba05`c657fe00 : ksthunk!CKernelFilterDevice::DispatchIrp+0x25e
ffffcc08`f62ff410 fffff805`43719ffa     : ffffba05`d4195040 fffff805`4403a080 ffffba05`d4195040 fffff805`4403a080 : ksthunk!CKernelFilterDevice::DispatchIrpBridge+0x13
ffffcc08`f62ff440 fffff805`4360e957     : ffffba05`d4195040 ffffffff`fa0a1f00 fffff805`43719da0 00000000`00000000 : nt!PopIrpWorker+0x25a
ffffcc08`f62ff4f0 fffff805`4381f3b4     : fffff805`402c9180 ffffba05`d4195040 fffff805`4360e900 00000000`00000246 : nt!PspSystemThreadStartup+0x57
ffffcc08`f62ff540 00000000`00000000     : ffffcc08`f6300000 ffffcc08`f62f9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME:  ks!CKsDevice::AcquireDevice+4b

MODULE_NAME: ks

IMAGE_NAME:  ks.sys

IMAGE_VERSION:  10.0.22621.3858

STACK_COMMAND:  .process /r /p 0xffffba0594ed4040; .thread 0xffffba05d4195040 ; kb

BUCKET_ID_FUNC_OFFSET:  4b

FAILURE_BUCKET_ID:  0x9F_3_ks!CKsDevice::AcquireDevice

OS_VERSION:  10.0.22621.2506

BUILDLAB_STR:  ni_release_svc_prod3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f0041349-03f4-2d36-ccf0-e8d26fb30fb6}

Followup:     MachineOwner
---------
Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. DaveM121 891.6K Reputation points Independent Advisor
    2024-07-11T06:25:06+00:00

    Glad to help!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-07-10T19:33:58+00:00

    Thanks for the information, Dave.

    I will note that and upload new minidump if it crashed again.

    Was this answer helpful?

    0 comments
  3. DaveM121 891.6K Reputation points Independent Advisor
    2024-07-10T06:04:41+00:00

    Your new minidump file just indicates generic memory (RAM) corruption no specific driver is listed

    If the PC only crashed once, then most likely Windows was updating drivers in the background, that caused a temporary incompatibility and there is nothing further you need to do.

    If the PC does crash again, please upload any new minidump files you may get for analysis.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-07-09T21:20:24+00:00

    Hello Dave,

    Thanks for taking care of this request.

    1. Only once so far, but we are concerned that if this turns into on-going issue for the user. We want to confirm the cause of it before returning the laptop to its user.
    2. Here is the link:

    Dumpfile_DrivePowerState.zip

    Was this answer helpful?

    0 comments
  5. DaveM121 891.6K Reputation points Independent Advisor
    2024-07-09T20:41:36+00:00

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

    1

    Did the PC only crash once or is this an on-going problem?

    2

    Please upload any minidump files you have for analysis, 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.

    Was this answer helpful?

    0 comments