none
电脑蓝屏,麻烦帮忙分析一下dump文件 RRS feed

  • 问题


  • 0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc000001d, The exception code that was not handled
    Arg2: fffffa8010949070, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 00000000ffffff00, Parameter 1 of the exception

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

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that     ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: ExceptionRecord                               ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that     ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: ContextRecord                                 ***
    ***                                                                   ***
    *************************************************************************

    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING:  7600.16988.amd64fre.win7_gdr.120401-1505

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

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

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

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

    BIOS_VENDOR:  American Megatrends Inc.

    BIOS_VERSION:  4.6.5

    BIOS_DATE:  08/02/2016

    BASEBOARD_MANUFACTURER:  INTEL Corporation

    BASEBOARD_PRODUCT:  MAHOBAY

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

    DUMP_TYPE:  2

    BUGCHECK_P1: ffffffffc000001d

    BUGCHECK_P2: fffffa8010949070

    BUGCHECK_P3: 0

    BUGCHECK_P4: ffffff00

    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - <Unable to get error code text>

    FAULTING_IP: 
    +0
    fffffa80`10949070 16              ???

    BUGCHECK_STR:  0x1E_c000001d

    CPU_COUNT: 4

    CPU_MHZ: cdc

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 3a

    CPU_STEPPING: 9

    CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: A'00000000 (cache) A'00000000 (init)

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT_SERVER

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    ANALYSIS_SESSION_HOST:  ZHANQ-S3

    ANALYSIS_SESSION_TIME:  09-22-2017 09:41:53.0504

    ANALYSIS_VERSION: 10.0.15063.468 amd64fre

    EXCEPTION_RECORD:  fffff88018e62718 -- (.exr 0xfffff88018e62718)
    ExceptionAddress: fffffa8010949070
       ExceptionCode: c000001d (Illegal instruction)
      ExceptionFlags: 00000000
    NumberParameters: 0

    TRAP_FRAME:  fffff88018e627c0 -- (.trap 0xfffff88018e627c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa801094a876 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000176 rsi=0000000000000000 rdi=0000000000000000
    rip=fffffa8010949070 rsp=fffff88018e62958 rbp=fffffa800ccbf000
     r8=fffffa8009927090  r9=fffff8a00b5eb010 r10=00000000fffffffc
    r11=fffff8a00b5eb11c r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    fffffa80`10949070 16              ???
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff80001b03e49 to fffff80001aca040

    FAILED_INSTRUCTION_ADDRESS: 
    +0
    fffffa80`10949070 16              ???

    STACK_TEXT:  
    fffff880`18e61f48 fffff800`01b03e49 : 00000000`0000001e ffffffff`c000001d fffffa80`10949070 00000000`00000000 : nt!KeBugCheckEx
    fffff880`18e61f50 fffff800`01ac9682 : fffff880`18e62718 00000000`00016800 fffff880`18e627c0 fffffa80`1094a800 : nt!KiDispatchException+0x1b9
    fffff880`18e625e0 fffff800`01ac77df : fffff880`18e627c0 fffff880`01673d00 fffffa80`108dca00 fffffa80`00000000 : nt!KiExceptionDispatch+0xc2
    fffff880`18e627c0 fffffa80`10949070 : fffffa80`0ccbf17a 00000000`00000000 fffffa80`099380e0 fffff880`02c94460 : nt!KiInvalidOpcodeFault+0x11f
    fffff880`18e62958 fffffa80`0ccbf17a : 00000000`00000000 fffffa80`099380e0 fffff880`02c94460 fffffa80`099380e0 : 0xfffffa80`10949070
    fffff880`18e62960 00000000`00000000 : fffffa80`099380e0 fffff880`02c94460 fffffa80`099380e0 fffff8a0`00000002 : 0xfffffa80`0ccbf17a


    STACK_COMMAND:  kb

    THREAD_SHA1_HASH_MOD_FUNC:  0b0d9bcc38c4f44d04362c81d71bdc0d75215439

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  f8ba0e08b449df9fd51220d0ae984216fde36cd9

    THREAD_SHA1_HASH_MOD:  d084f7dfa548ce4e51810e4fd5914176ebc66791

    FOLLOWUP_IP: 
    nt!KiDispatchException+1b9
    fffff800`01b03e49 cc              int     3

    FAULT_INSTR_CODE:  8b4865cc

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!KiDispatchException+1b9

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4f7912ee

    IMAGE_VERSION:  6.1.7600.16988

    FAILURE_BUCKET_ID:  X64_0x1E_c000001d_BAD_IP_nt!KiDispatchException+1b9

    BUCKET_ID:  X64_0x1E_c000001d_BAD_IP_nt!KiDispatchException+1b9

    PRIMARY_PROBLEM_CLASS:  X64_0x1E_c000001d_BAD_IP_nt!KiDispatchException+1b9

    TARGET_TIME:  2017-09-21T20:47:09.000Z

    OSBUILD:  7600

    OSSERVICEPACK:  16988

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK:  274

    PRODUCT_TYPE:  3

    OSPLATFORM_TYPE:  x64

    OSNAME:  Windows 7

    OSEDITION:  Windows 7 Server Enterprise TerminalServer SingleUserTS

    OS_LOCALE:  

    USER_LCID:  0

    OSBUILD_TIMESTAMP:  2012-04-02 10:46:06

    BUILDDATESTAMP_STR:  120401-1505

    BUILDLAB_STR:  win7_gdr

    BUILDOSVER_STR:  6.1.7600.16988.amd64fre.win7_gdr.120401-1505

    ANALYSIS_SESSION_ELAPSED_TIME:  bc2

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_0x1e_c000001d_bad_ip_nt!kidispatchexception+1b9

    FAILURE_ID_HASH:  {e478d584-4238-2c12-3a17-4ee47ab381b2}

    Followup:     MachineOwner
    ---------
    2017年9月22日 2:17

全部回复