Como descobrir o que causa falhas no Windows 10 durante a suspensão ou a hibernação (DRIVER_POWER_STATE_FAILURE, ntoskrnl.exe + 14d220)?

Question

Quando volto do modo de suspensão / hibernação no Windows 10, ele inicia normalmente (como foi desativado). No log de eventos, encontrei o seguinte erro:

O computador foi reinicializado a partir de uma verificação de bug. A verificação de bug foi: 0x0000009f (0x0000000000000003, 0xffffe000b0233060, 0xffffd00035bba990, 0xffffe000abc76010). Um dump foi salvo em: C: \ WINDOWS \ MEMORY.DMP. ID do relatório: 081015-39234-01.

Como descobrir o que está causando o problema, por exemplo, qual motorista? (Windows 10 foi atualizado do Windows 8.1, onde estava funcionando, ok.)

ATUALIZAÇÃO: Mensagem BSOD é esta:

Bug Check String: DRIVER_POWER_STATE_FAILURE
Bug Check Code: 0x0000009f
Parameter 1: 00000000'00000003
Parameter 2: ffffe001'2795a060
Parameter 3: ffffd001'024ab990
Parameter 4: ffffe001'33776980
Caused By Driver: ntoskrnl.exe
Caused By Address: ntoskrnl.exe+14d220
File Description: NT Kernel & System
Product Name: Microsoft® Windows® Operating System
Company: Microsoft Corporation
File Version: 10.0.10240.16412 (th1.150729-1800)
Processor: x64
Crash Address: ntoskrnl.exe+14d220

    

Answer 1

o acidente parece ser causado pelo driver btfilter.sys (driver Atheros Bluetooth):

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

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


    SYSTEM_SKU:  PSKK6E

    SYSTEM_VERSION:  PSKK6E-02H05KCZ

    BIOS_DATE:  09/19/2014

    BASEBOARD_PRODUCT:  VG10S

    BASEBOARD_VERSION:  To be filled by O.E.M.

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    BUGCHECK_STR:  0x9F

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    ANALYSIS_VERSION: 10.0.10240.9 amd64fre

    STACK_TEXT:  
    00 nt!KeBugCheckEx
    01 nt!PopIrpWatchdogBugcheck
    02 nt!PopIrpWatchdog
    03 nt!KiRetireDpcList
    04 nt!KiIdleLoop


    IMAGE_VERSION:  10.0.10240.16401

    FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_btfilter_IMAGE_usbhub.sys

    5: kd> !irp ffffe00133776980
    Irp is active with 15 stacks 14 is current (= 0xffffe00133776df8)
     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
    >[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
                0 e1 ffffe0012792b030 00000000 fffff800907ecd40-ffffe0012ec4f7d0 Success Error Cancel pending
              Unable to load image \SystemRoot\system32\DRIVERS\btfilter.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for btfilter.sys
    *** ERROR: Module load completed but symbols could not be loaded for btfilter.sys
     \Driver\BtFilter   nt!PopSystemIrpCompletion
                Args: 00014400 00000000 00000004 00000002
     [N/A(0), N/A(0)]
                0  0 00000000 00000000 00000000-ffffe0012ec4f7d0    

                Args: 00000000 00000000 00000000 00000000

        Loaded symbol image file: btfilter.sys
        Image path: \SystemRoot\system32\DRIVERS\btfilter.sys
        Image name: btfilter.sys
        Browse all global symbols  functions  data
        Timestamp:        Fri Aug 09 11:41:27 2013 

o motorista tem 2 anos de idade. Procure uma atualização de driver ou remova-a e verifique se o driver genérico do Windows funciona.