Windows 10: BSOD DRIVER_POWER_STATE_FAILURE 2 minutes after the PC wakes from sleep

Discus and support BSOD DRIVER_POWER_STATE_FAILURE 2 minutes after the PC wakes from sleep in Windows 10 Performance & Maintenance to solve the problem; Hello, I consistently get a BSOD DRIVER_POWER_STATE_FAILURE exactly 2 minutes after the PC wakes from sleep. Disabling sleep is not an option.... Discussion in 'Windows 10 Performance & Maintenance' started by RolandFeibert, Mar 10, 2020.

  1. ROLANDFEIBERT
    RolandFeibert Win User

    BSOD DRIVER_POWER_STATE_FAILURE 2 minutes after the PC wakes from sleep


    Hello,

    I consistently get a BSOD DRIVER_POWER_STATE_FAILURE exactly 2 minutes after the PC wakes from sleep.

    Disabling sleep is not an option.


    Using WinDbg on C:\Windows\MEMORY 031020 614pm.DMP:


    Microsoft R Windows Debugger Version 10.0.18362.1 AMD64
    Copyright c Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\MEMORY 031020 614pm.DMP]
    Kernel Bitmap Dump File: Full address space is available

    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 18362 MP 8 procs Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 18362.1.amd64fre.19h1_release.190318-1202
    Machine Name:
    Kernel base = 0xfffff800`7cc00000 PsLoadedModuleList = 0xfffff800`7d048110
    Debug session time: Tue Mar 10 18:06:42.997 2020 UTC - 4:00
    System Uptime: 0 days 1:50:18.917
    Loading Kernel Symbols
    ......................................Page 2003ea15a too large to be in the dump file.
    Page 2003ed759 too large to be in the dump file.
    .........................
    ................................................................
    ......................................
    Loading User Symbols

    Loading unloaded module list
    ........................
    For analysis of this file, run !analyze -v
    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: ffff8001fa217d80, Physical Device Object of the stack
    Arg3: fffff8007feb3c00, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffff800202e829a0, The blocked IRP

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


    KEY_VALUES_STRING: 1


    PROCESSES_ANALYSIS: 1

    SERVICE_ANALYSIS: 1

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 402

    BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

    SYSTEM_MANUFACTURER: ADDC

    SYSTEM_PRODUCT_NAME: ADDC KBL DDR4

    SYSTEM_SKU: ADDC-11C-16-128

    SYSTEM_VERSION: 3.0

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: 5.12

    BIOS_DATE: 10/19/2018

    BASEBOARD_MANUFACTURER: ADDC

    BASEBOARD_PRODUCT: ADDC KBL DDR4

    BASEBOARD_VERSION: 3.0

    DUMP_TYPE: 0

    BUGCHECK_P1: 3

    BUGCHECK_P2: ffff8001fa217d80

    BUGCHECK_P3: fffff8007feb3c00

    BUGCHECK_P4: ffff800202e829a0

    DRVPOWERSTATE_SUBCODE: 3

    IMAGE_NAME: ACPI.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MODULE_NAME: ACPI

    FAULTING_MODULE: fffff8007e8d0000 ACPI

    CPU_COUNT: 8

    CPU_MHZ: 840

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 8e

    CPU_STEPPING: a

    CPU_MICROCODE: 6,8e,a,0 F,M,S,R SIG: 96'00000000 cache 96'00000000 init

    BLACKBOXBSD: 1 !blackboxbsd


    BLACKBOXNTFS: 1 !blackboxntfs


    BLACKBOXPNP: 1 !blackboxpnp


    BLACKBOXWINLOGON: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x9F

    PROCESS_NAME: System

    CURRENT_IRQL: 2

    ANALYSIS_SESSION_HOST: DESKTOP-077IHRH

    ANALYSIS_SESSION_TIME: 03-10-2020 18:20:29.0955

    ANALYSIS_VERSION: 10.0.18362.1 amd64fre

    DPC_STACK_BASE: FFFFF8007FEB3FB0

    STACK_TEXT:
    fffff800`7feb3bc8 fffff800`7ceee7f7 : 00000000`0000009f 00000000`00000003 ffff8001`fa217d80 fffff800`7feb3c00 : nt!KeBugCheckEx
    fffff800`7feb3bd0 fffff800`7ceee701 : ffff8002`025ef690 ffff8001`f84ea000 fffff800`78593100 fffff800`78593180 : nt!PopIrpWatchdogBugcheck+0xef
    fffff800`7feb3c40 fffff800`7ccc1d59 : ffff8002`025ef6c8 fffff800`918c4ff0 f87c900f`00000003 0000000f`68ee39c7 : nt!PopIrpWatchdog+0x31
    fffff800`7feb3c90 fffff800`7ccc0ab9 : 00000000`00000012 00000000`00989680 00000000`0003da4b 00000000`00000063 : nt!KiProcessExpiredTimerList+0x169
    fffff800`7feb3d80 fffff800`7cdc93c5 : 00000000`00000000 fffff800`78593180 fffff800`7cbcc0e0 00000000`00000064 : nt!KiRetireDpcList+0x4e9
    fffff800`7feb3fb0 fffff800`7cdc91b0 : 00000000`00000001 fffff800`7cb602cb 00000000`01000010 fffff800`7cb602cb : nt!KxRetireDpcList+0x5
    fffffb8d`bfd126f0 fffff800`7cdc8a65 : 00000000`00000064 fffff800`7cdc4401 00000000`000003e8 fffffb8d`bfd127b0 : nt!KiDispatchInterruptContinue
    fffffb8d`bfd12720 fffff800`7cdc4401 : 00000000`000003e8 fffffb8d`bfd127b0 fffff800`7cbcc0e0 fffffb8d`bfd127c0 : nt!KiDpcInterruptBypass+0x25
    fffffb8d`bfd12730 fffff800`93971264 : fffff800`93974a1d 00000000`000003e7 00000000`00000060 fffffb8d`bfd12930 : nt!KiInterruptDispatchNoLockNoEtw+0xb1
    fffffb8d`bfd128c8 fffff800`93974a1d : 00000000`000003e7 00000000`00000060 fffffb8d`bfd12930 fffff800`00000002 : i8042prt!I8xReadPortUchar+0x4
    fffffb8d`bfd128d0 fffff800`93983d9c : 00000000`00020000 00000000`00000000 ffffffff`ffffd8f0 fffff800`9397e8e0 : i8042prt!I8xDrainOutputBuffer+0xd1
    fffffb8d`bfd12920 fffff800`9398453b : 00000000`c0000001 00000000`00020000 00000000`c0000001 00000000`00000064 : i8042prt!I8xInitializeHardware+0x90
    fffffb8d`bfd12990 fffff800`7cd02b0f : ffff8002`035fb220 00000000`c0000001 00000000`c0000001 00000000`00000000 : i8042prt!I8xReinitializeHardware+0x14b
    fffffb8d`bfd12a00 fffff800`7ccf43c5 : ffff8001`f82b1a20 ffff8002`04bef040 fffff800`7cd02a10 00000000`0000000c : nt!IopProcessWorkItem+0xff
    fffffb8d`bfd12a70 fffff800`7cc6bce5 : ffff8002`04bef040 00000000`00000080 ffff8001`f82b0340 00000000`00000080 : nt!ExpWorkerThread+0x105
    fffffb8d`bfd12b10 fffff800`7cdc99ca : ffff9b81`ec480180 ffff8002`04bef040 fffff800`7cc6bc90 000001d1`83f4fe48 : nt!PspSystemThreadStartup+0x55
    fffffb8d`bfd12b60 00000000`00000000 : fffffb8d`bfd13000 fffffb8d`bfd0c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


    THREAD_SHA1_HASH_MOD_FUNC: a1fd116e0c584322e4b33776c9854c25b9f8f6d9

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 80f7f3483dd4917828a93bb8c27303edd9d02a65

    THREAD_SHA1_HASH_MOD: 03da033d24ecdcf2459079eb0d6820818763ff3d

    FOLLOWUP_NAME: MachineOwner

    STACK_COMMAND: .thread ; .cxr ; kb

    FAILURE_BUCKET_ID: 0x9F_3_i8042prt_IMAGE_ACPI.sys

    BUCKET_ID: 0x9F_3_i8042prt_IMAGE_ACPI.sys

    PRIMARY_PROBLEM_CLASS: 0x9F_3_i8042prt_IMAGE_ACPI.sys

    TARGET_TIME: 2020-03-10T22:06:42.000Z

    OSBUILD: 18362

    OSSERVICEPACK: 0

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: unknown_date

    BUILDDATESTAMP_STR: 190318-1202

    BUILDLAB_STR: 19h1_release

    BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

    ANALYSIS_SESSION_ELAPSED_TIME: 2409

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x9f_3_i8042prt_image_acpi.sys

    FAILURE_ID_HASH: {a42f147e-922c-d9e0-658e-1c9f7b2cb9ff}

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

    0: kd> !devobj ffff8001fa217d80
    Device object ffff8001fa217d80 is for:
    0000002d \Driver\ACPI DriverObject ffff8001f862e960
    Current Irp 00000000 RefCount 1 Type 00000032 Flags 00001040
    SecurityDescriptor ffffc48a6f2cce20 DevExt ffff8001fa1527d0 DevObjExt ffff8001fa217ed0 DevNode ffff8001fa1b6670
    ExtensionFlags 0x00000800 DOE_DEFAULT_SD_PRESENT
    Characteristics 0x00000080 FILE_AUTOGENERATED_DEVICE_NAME
    AttachedDevice Upper ffff8001fdfdc980 \Driver\i8042prt
    Device queue is not busy.
    0: kd> !devnode ffff8001fa1b6670
    DevNode 0xffff8001fa1b6670 for PDO 0xffff8001fa217d80
    Parent 0xffff8001fa2138e0 Sibling 0xffff8001fa1b69a0 Child 0000000000
    InstancePath is "ACPI\PNP0F03\0"
    ServiceName is "i8042prt"
    TargetDeviceNotify List - f 0xffffc48a72d40380 b 0xffffc48a72d40380
    State = DeviceNodeStarted 0x308
    Previous State = DeviceNodeEnumerateCompletion 0x30d
    StateHistory[19] = DeviceNodeEnumerateCompletion 0x30d
    StateHistory[18] = DeviceNodeEnumeratePending 0x30c
    StateHistory[17] = DeviceNodeStarted 0x308
    StateHistory[16] = DeviceNodeEnumerateCompletion 0x30d
    StateHistory[15] = DeviceNodeEnumeratePending 0x30c
    StateHistory[14] = DeviceNodeStarted 0x308
    StateHistory[13] = DeviceNodeEnumerateCompletion 0x30d
    StateHistory[12] = DeviceNodeEnumeratePending 0x30c
    StateHistory[11] = DeviceNodeStarted 0x308
    StateHistory[10] = DeviceNodeEnumerateCompletion 0x30d
    StateHistory[09] = DeviceNodeEnumeratePending 0x30c
    StateHistory[08] = DeviceNodeStarted 0x308
    StateHistory[07] = DeviceNodeEnumerateCompletion 0x30d
    StateHistory[06] = DeviceNodeEnumeratePending 0x30c
    StateHistory[05] = DeviceNodeStarted 0x308
    StateHistory[04] = DeviceNodeEnumerateCompletion 0x30d
    StateHistory[03] = DeviceNodeEnumeratePending 0x30c
    StateHistory[02] = DeviceNodeStarted 0x308
    StateHistory[01] = DeviceNodeEnumerateCompletion 0x30d
    StateHistory[00] = DeviceNodeEnumeratePending 0x30c
    Flags 0x2c0000f0 DNF_ENUMERATED, DNF_IDS_QUERIED,
    DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED,
    DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_LOWER_CLASS_FILTERS,
    DNF_NO_UPPER_DEVICE_FILTERS
    UserFlags 0x00000008 DNUF_NOT_DISABLEABLE
    CapabilityFlags 0x000000c0 UniqueID, SilentInstall
    DisableableDepends = 1 including self
    0: kd> dt fffff8007feb3c00
    Symbol not found at address fffff8007feb3c00.
    0: kd> !dt fffff8007feb3c00
    No export dt found
    0: kd> !irp ffff800202e829a0
    Irp is active with 6 stacks 4 is current = 0xffff800202e82b48
    No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned
    cmd flg cl Device File Completion-Context
    [N/A0, N/A0]
    0 0 00000000 00000000 00000000-00000000

    Args: 00000000 00000000 00000000 00000000
    [N/A0, N/A0]
    0 0 00000000 00000000 00000000-00000000

    Args: 00000000 00000000 00000000 00000000
    [IRP_MJ_POWER16, IRP_MN_WAIT_WAKE0]
    0 0 ffff8001fa217d80 00000000 fffff8009397baa0-00000000
    \Driver\ACPI i8042prt!I8xPowerUpToD0Complete
    Args: 00000000 00000000 00000000 00000002
    >[IRP_MJ_POWER16, IRP_MN_SET_POWER2]
    0 e1 ffff8001fdfdc980 00000000 fffff800939a19c0-00000000 Success Error Cancel pending
    \Driver\i8042prt mouclass!MouseClassPowerComplete
    Args: 00041100 00000001 00000001 00000002
    [IRP_MJ_POWER16, IRP_MN_SET_POWER2]
    0 e1 ffff8001fdd1b0b0 00000000 fffff8007cd71110-ffff8002025ef690 Success Error Cancel pending
    \Driver\mouclass nt!PopRequestCompletion
    Args: 00041100 00000001 00000001 00000002
    [N/A0, N/A0]
    0 0 00000000 00000000 00000000-ffff8002025ef690

    Args: 00000000 00000000 00000000 00000000
    0: kd> !devstack ffff8001fa217d80
    !DevObj !DrvObj !DevExt ObjectName
    ffff8001fdd1b0b0 \Driver\mouclass ffff8001fdd1b200 PointerClass0
    ffff8001fdfdc980 \Driver\i8042prt ffff8001fdfdcad0
    > ffff8001fa217d80 \Driver\ACPI ffff8001fa1527d0 0000002d
    !DevNode ffff8001fa1b6670 :
    DeviceInst is "ACPI\PNP0F03\0"
    ServiceName is "i8042prt"
    0: kd> !poaction
    PopAction: fffff8007d044fc0
    State..........: 0 - Idle
    Updates........: 0
    Action.........: None
    Lightest State.: Unspecified
    Flags..........: 10000003 QueryAppsUIAllowed
    Irp minor......: ??
    System State...: Unspecified
    Hiber Context..: 0000000000000000

    Allocated power irps PopIrpList - fffff8007d0456f0
    IRP: ffff800202e829a0 set/D0,, PDO: ffff8001fa217d80, CURRENT: ffff8001fdfdc980
    IRP: ffff80020215c9a0 wait-wake/S4, PDO: ffff8001fe20b060
    IRP: ffff8001ff30c010 wait-wake/S4, PDO: ffff8001fe261060

    Irp worker threads PopIrpThreadList - fffff8007d03ad00
    THREAD: ffff8001f82db040 static
    THREAD: ffff8001f82ba040 static

    Broadcast in progress: FALSE
    Is Directed DRIPS Transition: FALSE

    No Device State present


    Do I have an issue with "i8042prt" above? Is this my keyboard?



    Using WinDbg on C:\Windows\minidump\031020-9609-01.DMP:


    Microsoft R Windows Debugger Version 10.0.18362.1 AMD64
    Copyright c Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\minidump\031020-9609-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 18362 MP 8 procs Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 18362.1.amd64fre.19h1_release.190318-1202
    Machine Name:
    Kernel base = 0xfffff800`7cc00000 PsLoadedModuleList = 0xfffff800`7d048110
    Debug session time: Tue Mar 10 18:06:42.997 2020 UTC - 4:00
    System Uptime: 0 days 1:50:18.917
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................................
    Loading User Symbols
    Loading unloaded module list
    ........................
    For analysis of this file, run !analyze -v
    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: ffff8001fa217d80, Physical Device Object of the stack
    Arg3: fffff8007feb3c00, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffff800202e829a0, The blocked IRP

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

    *** WARNING: Unable to verify timestamp for win32k.sys

    KEY_VALUES_STRING: 1


    PROCESSES_ANALYSIS: 1

    SERVICE_ANALYSIS: 1

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

    SYSTEM_MANUFACTURER: ADDC

    SYSTEM_PRODUCT_NAME: ADDC KBL DDR4

    SYSTEM_SKU: ADDC-11C-16-128

    SYSTEM_VERSION: 3.0

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: 5.12

    BIOS_DATE: 10/19/2018

    BASEBOARD_MANUFACTURER: ADDC

    BASEBOARD_PRODUCT: ADDC KBL DDR4

    BASEBOARD_VERSION: 3.0

    DUMP_TYPE: 2

    BUGCHECK_P1: 3

    BUGCHECK_P2: ffff8001fa217d80

    BUGCHECK_P3: fffff8007feb3c00

    BUGCHECK_P4: ffff800202e829a0

    DRVPOWERSTATE_SUBCODE: 3

    IMAGE_NAME: ACPI.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MODULE_NAME: ACPI

    FAULTING_MODULE: fffff8007e8d0000 ACPI

    CPU_COUNT: 8

    CPU_MHZ: 840

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 8e

    CPU_STEPPING: a

    CPU_MICROCODE: 6,8e,a,0 F,M,S,R SIG: 96'00000000 cache 96'00000000 init

    BLACKBOXBSD: 1 !blackboxbsd


    BLACKBOXNTFS: 1 !blackboxntfs


    BLACKBOXPNP: 1 !blackboxpnp


    BLACKBOXWINLOGON: 1

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x9F

    PROCESS_NAME: System

    CURRENT_IRQL: 2

    ANALYSIS_SESSION_HOST: DESKTOP-077IHRH

    ANALYSIS_SESSION_TIME: 03-10-2020 19:11:38.0120

    ANALYSIS_VERSION: 10.0.18362.1 amd64fre

    DPC_STACK_BASE: FFFFF8007FEB3FB0

    STACK_TEXT:
    fffff800`7feb3bc8 fffff800`7ceee7f7 : 00000000`0000009f 00000000`00000003 ffff8001`fa217d80 fffff800`7feb3c00 : nt!KeBugCheckEx
    fffff800`7feb3bd0 fffff800`7ceee701 : ffff8002`025ef690 ffff8001`f84ea000 fffff800`78593100 fffff800`78593180 : nt!PopIrpWatchdogBugcheck+0xef
    fffff800`7feb3c40 fffff800`7ccc1d59 : ffff8002`025ef6c8 fffff800`918c4ff0 f87c900f`00000003 0000000f`68ee39c7 : nt!PopIrpWatchdog+0x31
    fffff800`7feb3c90 fffff800`7ccc0ab9 : 00000000`00000012 00000000`00989680 00000000`0003da4b 00000000`00000063 : nt!KiProcessExpiredTimerList+0x169
    fffff800`7feb3d80 fffff800`7cdc93c5 : 00000000`00000000 fffff800`78593180 fffff800`7cbcc0e0 00000000`00000064 : nt!KiRetireDpcList+0x4e9
    fffff800`7feb3fb0 fffff800`7cdc91b0 : 00000000`00000001 fffff800`7cb602cb 00000000`01000010 fffff800`7cb602cb : nt!KxRetireDpcList+0x5
    fffffb8d`bfd126f0 fffff800`7cdc8a65 : 00000000`00000064 fffff800`7cdc4401 00000000`000003e8 fffffb8d`bfd127b0 : nt!KiDispatchInterruptContinue
    fffffb8d`bfd12720 fffff800`7cdc4401 : 00000000`000003e8 fffffb8d`bfd127b0 fffff800`7cbcc0e0 fffffb8d`bfd127c0 : nt!KiDpcInterruptBypass+0x25
    fffffb8d`bfd12730 fffff800`93971264 : fffff800`93974a1d 00000000`000003e7 00000000`00000060 fffffb8d`bfd12930 : nt!KiInterruptDispatchNoLockNoEtw+0xb1
    fffffb8d`bfd128c8 fffff800`93974a1d : 00000000`000003e7 00000000`00000060 fffffb8d`bfd12930 fffff800`00000002 : i8042prt!I8xReadPortUchar+0x4
    fffffb8d`bfd128d0 fffff800`93983d9c : 00000000`00020000 00000000`00000000 ffffffff`ffffd8f0 fffff800`9397e8e0 : i8042prt!I8xDrainOutputBuffer+0xd1
    fffffb8d`bfd12920 fffff800`9398453b : 00000000`c0000001 00000000`00020000 00000000`c0000001 00000000`00000064 : i8042prt!I8xInitializeHardware+0x90
    fffffb8d`bfd12990 fffff800`7cd02b0f : ffff8002`035fb220 00000000`c0000001 00000000`c0000001 00000000`00000000 : i8042prt!I8xReinitializeHardware+0x14b
    fffffb8d`bfd12a00 fffff800`7ccf43c5 : ffff8001`f82b1a20 ffff8002`04bef040 fffff800`7cd02a10 00000000`0000000c : nt!IopProcessWorkItem+0xff
    fffffb8d`bfd12a70 fffff800`7cc6bce5 : ffff8002`04bef040 00000000`00000080 ffff8001`f82b0340 00000000`00000080 : nt!ExpWorkerThread+0x105
    fffffb8d`bfd12b10 fffff800`7cdc99ca : ffff9b81`ec480180 ffff8002`04bef040 fffff800`7cc6bc90 000001d1`83f4fe48 : nt!PspSystemThreadStartup+0x55
    fffffb8d`bfd12b60 00000000`00000000 : fffffb8d`bfd13000 fffffb8d`bfd0c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


    THREAD_SHA1_HASH_MOD_FUNC: a1fd116e0c584322e4b33776c9854c25b9f8f6d9

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 80f7f3483dd4917828a93bb8c27303edd9d02a65

    THREAD_SHA1_HASH_MOD: 03da033d24ecdcf2459079eb0d6820818763ff3d

    FOLLOWUP_NAME: MachineOwner

    IMAGE_VERSION: 10.0.18362.329

    STACK_COMMAND: .thread ; .cxr ; kb

    FAILURE_BUCKET_ID: 0x9F_3_i8042prt_IMAGE_ACPI.sys

    BUCKET_ID: 0x9F_3_i8042prt_IMAGE_ACPI.sys

    PRIMARY_PROBLEM_CLASS: 0x9F_3_i8042prt_IMAGE_ACPI.sys

    TARGET_TIME: 2020-03-10T22:06:42.000Z

    OSBUILD: 18362

    OSSERVICEPACK: 693

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: unknown_date

    BUILDDATESTAMP_STR: 190318-1202

    BUILDLAB_STR: 19h1_release

    BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

    ANALYSIS_SESSION_ELAPSED_TIME: 19499

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x9f_3_i8042prt_image_acpi.sys

    FAILURE_ID_HASH: {a42f147e-922c-d9e0-658e-1c9f7b2cb9ff}

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


    Can you assist?

    Thank You, Roland

    :)
     
    RolandFeibert, Mar 10, 2020
    #1
  2. CHRISBARBER2
    ChrisBarber2 Win User

    BSOD due to netadaptercx.sys after waking the PC from Sleep

    Hi Prakhar,

    The steps you suggested did not solve the problem. I am still experiencing the BSOD when waking the computer from sleep. If you have an other suggestions they'd be greatly appreciated.

    Regards,

    Chris
     
    ChrisBarber2, Mar 10, 2020
    #2
  3. PASTORMIKE
    PastorMike Win User
    BSOD with Driver_Power_State_Failure after waking from sleep


    Ever since updating to Windows 10 I have periodically had a problem with my computer when I wake it from sleep. The symptoms of this are as follows:
    • The machine will wake from sleep fine and I'm able to put in my password etc. After 30s to a minute, the machine will give me a BSOD citing Driver_Power_State_Failure (occasionally it has been something else but this is the main culprit.) It then collects data cycling up to 100% but does not reboot automatically. I need to do this manually. When I do so, the machine will reboot normally.
    • On a couple of occasions in the last month, the machine will simply not wake from sleep at all and neither does it respond when I press the power or reset buttons. The only way I can get it to start again is by manually turning off the power supply and then turning it on again. I am not sure if this is related to the BSOD issue or whether it is a separate issue.
    • I have previously had an issue where the machine would appear to wake from sleep but the screen would remain dead and the keyboard was unresponsive (though the num lock light was showing.) I can't recall having this issue recently and am unsure whether this is a separate issue.
    • It normally seems to occur after the machine has been asleep (hybrid sleep) for some time.
    • Of late I've noticed that it often seems to coincide with me opening a new program or file immediately after waking the machine from sleep.

    I have tried several things to fix the issue as follows:
    • I've tried to run Driver Verifier but have never managed to get the machine to start up successfully even with only one driver selected. (In fact I have to manually import the original registry settings to turn off Driver Verifier again in order to get my machine going again.)
    • I have uninstalled and unplugged a USB video capture device but that has made no difference.
    • I have completely uninstalled the drivers for my graphics card and then reinstalled using Microsoft's default drivers. No difference.
    • I've made sure that I am running the latest drivers, have checked Windows update etc.

    It's tricky to pin things down to a particular driver without using Driver Verifier and I'm not sure how to decipher the dump files and error logs generated each time this happens. That's why I've come here for help!

    Here's a zip with all of the relevant data. Attachment 61143

    Any help you can give would be very much appreciated!
     
    PastorMike, Mar 10, 2020
    #3
  4. CHRISTOPHER GUINNUP
    Christopher Guinnup Win User

    BSOD DRIVER_POWER_STATE_FAILURE 2 minutes after the PC wakes from sleep

    DRIVER_POWER_STATE_FAILURE BSOD on wake from sleep

    I've tried all the solutions I can find online, including turning all advanced power settings to max performance, and running the driver verifier. Unfortunately, my laptop still encounters a DRIVER_POWER_STATE_FAILURE error when waking from sleep.

    Here are my DMP and Msinfo32 files:

    Dropbox - Link not found

    Dell Inspiron 15 5570 laptop

    I appreciate any help.
     
    Christopher Guinnup, Mar 10, 2020
    #4
Thema:

BSOD DRIVER_POWER_STATE_FAILURE 2 minutes after the PC wakes from sleep

Loading...

  1. BSOD DRIVER_POWER_STATE_FAILURE 2 minutes after the PC wakes from sleep - Similar Threads - BSOD DRIVER_POWER_STATE_FAILURE minutes

  2. BSOD Driver_Power_State_Failure after waking from sleep Windows 11

    in Windows 10 Gaming
    BSOD Driver_Power_State_Failure after waking from sleep Windows 11: Was running into some BSOD recently. NTOSKRNL.EXE and QCWLAN64.sys. The QCWLAN64.sys has been resolved since updated the LAN Driver but NTOSKRNL.EX still happens. It happened when I woke PC from sleep. I tried copying a file to LucidLink 23 GB file and a little while BSOD....

  3. BSOD Driver_Power_State_Failure after waking from sleep Windows 11

    in Windows 10 Software and Apps
    BSOD Driver_Power_State_Failure after waking from sleep Windows 11: Was running into some BSOD recently. NTOSKRNL.EXE and QCWLAN64.sys. The QCWLAN64.sys has been resolved since updated the LAN Driver but NTOSKRNL.EX still happens. It happened when I woke PC from sleep. I tried copying a file to LucidLink 23 GB file and a little while BSOD....

  4. Windows 10 BSOD after wake from Sleep/Hibernate [DRIVER_POWER_STATE_FAILURE]

    in Windows 10 Performance & Maintenance
    Windows 10 BSOD after wake from Sleep/Hibernate [DRIVER_POWER_STATE_FAILURE]: I have recently bought a new device Lenovo Legion 5 AMD Ryzen 7 Sr. No PF2332PR [Product Support Link] and since the beginning, I am facing a BSOD Issue, Whenever I put my device to sleep/hibernate and turn it back on then it shows a black screen for a few seconds and then...

  5. Windows 10 BSOD after wake from Sleep/Hibernate [DRIVER_POWER_STATE_FAILURE]

    in Windows 10 Gaming
    Windows 10 BSOD after wake from Sleep/Hibernate [DRIVER_POWER_STATE_FAILURE]: I have recently bought a new device Lenovo Legion 5 AMD Ryzen 7 Sr. No PF2332PR [Product Support Link] and since the beginning, I am facing a BSOD Issue, Whenever I put my device to sleep/hibernate and turn it back on then it shows a black screen for a few seconds and then...

  6. Windows 10 BSOD after wake from Sleep/Hibernate [DRIVER_POWER_STATE_FAILURE]

    in Windows 10 Software and Apps
    Windows 10 BSOD after wake from Sleep/Hibernate [DRIVER_POWER_STATE_FAILURE]: I have recently bought a new device Lenovo Legion 5 AMD Ryzen 7 Sr. No PF2332PR [Product Support Link] and since the beginning, I am facing a BSOD Issue, Whenever I put my device to sleep/hibernate and turn it back on then it shows a black screen for a few seconds and then...

  7. DRIVER_POWER_STATE_FAILURE after wake from sleep, have tried everything

    in Windows 10 Drivers and Hardware
    DRIVER_POWER_STATE_FAILURE after wake from sleep, have tried everything: I've been dealing with this recurrent problem of a BSoD after my PC wakes from sleep for a couple months now, but nothing seems to work. I have tried re-installing drivers and updating windows. I did a clean install of windows, and then replaced the SSD and tried to do...

  8. After waking from Sleep, Monitor Shuts off after 2 minutes of inactivity

    in Windows 10 Performance & Maintenance
    After waking from Sleep, Monitor Shuts off after 2 minutes of inactivity: My power options are set to NEVER NEVER NEVER... but when I wake my computer from sleep the Monitor will shut off after 2 or 3 minutes and I have to log in from screen lock to continue reading or working. Its very annoying... I eventually just reboot the system and then...

  9. BSOD "DRIVER_POWER_STATE_FAILURE" after resuming from sleep

    in Windows 10 BSOD Crashes and Debugging
    BSOD "DRIVER_POWER_STATE_FAILURE" after resuming from sleep: Hi, My computer BSODs every time I resume from sleep, usually after a minute or two, with the "DRIVER_POWER_STATE_FAILURE" error. I've tried to update all my drivers and done some troubleshooting on my own, but I can't seem to find the cause of the crashes. I would love if...

  10. BSOD with Driver_Power_State_Failure after waking from sleep

    in Windows 10 BSOD Crashes and Debugging
    BSOD with Driver_Power_State_Failure after waking from sleep: Ever since updating to Windows 10 I have periodically had a problem with my computer when I wake it from sleep. The symptoms of this are as follows: The machine will wake from sleep fine and I'm able to put in my password etc. After 30s to a minute, the machine will give me...
  1. ADARSH ANSHUMAN
    Thread

    Windows 10 graphics card not showing in device manager after driver_power_state_failure.

    Ok so let's be honnest I turned on my pc around 12pm today, worked fine for 5 mins after that this happened,[ATTACH] And unfortunately I didn't...
    Thread by: Adarsh Anshuman, Feb 18, 2021, 3 replies, in forum: Windows 10 Drivers and Hardware
  2. ADARSHANSHUMAN
    Thread

    Windows 10 driver_power_state_failure without any reason

    Ok so let's be honest around 12 PM when I turned my pc on it worked fine for around 5 mins after that this happened [ATTACH] And unfortunately I...
    Thread by: AdarshAnshuman, Feb 18, 2021, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  3. PAWEL82
    Thread

    Blue Screen UsbHub3.sys DRIVER_POWER_STATE_FAILURE 9f on brand new laptop

    Hi, A few days ago i bought brand new Acer Nitro 5 AN515-54 NH. I installed the latest Windows 10 Pro, then all the drivers from Acer website,...
    Thread by: Pawel82, Feb 15, 2021, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
  4. /U/THEFARTICLEPARTICLE
    Thread

    Having BSOD issue: "DRIVER_POWER_STATE_FAILURE"

    Hi, shortly after I turn on my computer, I suddenly get this screen: https://ibb.co/HVdqV6W After this screen completes, I get taken back to the...
    Thread by: /u/TheFarticleParticle, Feb 13, 2021, 3 replies, in forum: Windows 10 Ask Insider
  5. AMED-
    Thread

    DRIVER_POWER_STATE_FAILURE

    So I just got COD and as I was playing, suddenly my keyboard stopped working. The mouse was working fine, and my character kept walking forward. I...
    Thread by: AMED-, Feb 12, 2021, 3 replies, in forum: Windows 10 BSOD Crashes and Debugging
Tags: