none
Errore durante Sospensione/Ibernazione WIN8_DRIVER_FAULT RRS feed

  • Domanda

  • Buongiorno,

    è da diversi giorni che non riesco ad effettuare l'ibernazione del mio notebook HP-450 con Windows 8.1, analizzando il minidump non riesco a capire cosa possa andare in conflitto? mi aiutate

    Grazie.

    Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


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


    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*c:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
    Machine Name:
    Kernel base = 0xfffff803`0160e000 PsLoadedModuleList = 0xfffff803`018e7250
    Debug session time: Wed Feb 11 23:22:19.421 2015 (UTC + 1:00)
    System Uptime: 0 days 2:07:20.112
    Loading Kernel Symbols
    .

    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.

    ..............................................................
    ................................................................
    ................................................................

    Loading User Symbols
    Loading unloaded module list
    ...............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9F, {3, ffffe0010097a470, ffffd0017c9c6960, ffffe0010a337010}

    Probably caused by : ntkrnlmp

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

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

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


    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump

    DRVPOWERSTATE_SUBCODE:  3

    IMAGE_NAME:  ntkrnlmp

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAULTING_MODULE: fffff801ccfac000 rassstp

    IRP_ADDRESS: ffffe0010a337010

    DEVICE_OBJECT: ffffe00104a87050

    DRIVER_OBJECT: ffffe0010496d8d0

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    BUGCHECK_STR:  0x9F

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre

    DPC_STACK_BASE:  FFFFD0017C9CDFB0

    STACK_TEXT:  
    ffffd001`7c9c6928 fffff803`01816e3e : 00000000`0000009f 00000000`00000003 ffffe001`0097a470 ffffd001`7c9c6960 : nt!KeBugCheckEx
    ffffd001`7c9c6930 fffff803`01816d5e : ffffe001`0803fa80 00000000`00000008 ffffd001`7c9c6a58 fffff803`016c1515 : nt!PopIrpWatchdogBugcheck+0xde
    ffffd001`7c9c6990 fffff803`016c2428 : 00000000`00000000 ffffd001`7c9c6ae0 00000000`00000001 00000000`00000001 : nt!PopIrpWatchdog+0x32
    ffffd001`7c9c69e0 fffff803`017624ea : ffffd001`7c998180 ffffd001`7c998180 ffffd001`7c9a42c0 ffffe001`09508880 : nt!KiRetireDpcList+0x4f8
    ffffd001`7c9c6c60 00000000`00000000 : ffffd001`7c9c7000 ffffd001`7c9c1000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: ntkrnlmp

    IMAGE_VERSION:  

    FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

    BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_image_ntkrnlmp

    FAILURE_ID_HASH:  {678b3384-34e9-dafc-d401-53951e725571}

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

    giovedì 12 febbraio 2015 08:56

Tutte le risposte