locked
服务器意外重启,windebug分析C:\WINDOWS\MEMORY.DMP内容如下,请是是什么问题引起服务器重启?谢谢! RRS feed

  • Question

  • Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [G:\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (16 procs) Free x64
    Product: Server, suite: Enterprise TerminalServer SingleUserTS
    Built by: 3790.srv03_sp2_gdr.090805-1438
    Machine Name:
    Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140
    Debug session time: Thu Oct 29 14:02:45.171 2009 (GMT+8)
    System Uptime: 0 days 0:59:59.917
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe -
    Loading Kernel Symbols
    ...............................................................
    ....................................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00000000`7efdf018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 3B, {c0000096, fffffadd8cf743d6, fffffadd8755eeb0, 0}

    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    Page 7e606 not present in the dump file. Type ".hh dbgerr004" for details
    Page 7e54d not present in the dump file. Type ".hh dbgerr004" for details
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command 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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *** ERROR: Module load completed but symbols could not be loaded for kerneld.amd64
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command 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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command 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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Probably caused by : kerneld.amd64 ( kerneld+13d6 )

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

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

    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000096, Exception code that caused the bugcheck
    Arg2: fffffadd8cf743d6, Address of the exception record for the exception that caused the bugcheck
    Arg3: fffffadd8755eeb0, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.

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

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    Page 7e606 not present in the dump file. Type ".hh dbgerr004" for details
    Page 7e54d not present in the dump file. Type ".hh dbgerr004" for details
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command 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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command 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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command 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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************

    ADDITIONAL_DEBUG_TEXT: 
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: kerneld

    FAULTING_MODULE: fffff80001000000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  47119e9f

    EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {

    FAULTING_IP:
    kerneld+13d6
    fffffadd`8cf743d6 0f32            rdmsr

    CONTEXT:  fffffadd8755eeb0 -- (.cxr 0xfffffadd8755eeb0)
    rax=000000008010204c rbx=fffffadda665dd60 rcx=00000000000000ee
    rdx=fffffadda60c3530 rsi=fffffadda60c3530 rdi=fffffadda6cddd80
    rip=fffffadd8cf743d6 rsp=fffffadd8755f6c0 rbp=000000000000000c
     r8=fffffadda618e340  r9=0000000000000000 r10=fffffadda8fef740
    r11=fffffadda665dd60 r12=fffffadda60c3530 r13=0000000000000001
    r14=0000000000000001 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    kerneld+0x13d6:
    fffffadd`8cf743d6 0f32            rdmsr
    Resetting default scope

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0x3B

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff8000127f111 to fffffadd8cf743d6

    STACK_TEXT: 
    fffffadd`8755f6c0 fffff800`0127f111 : 00000000`00000001 fffffadd`8755fcf0 fffffadd`8755fcf0 00000000`00000000 : kerneld+0x13d6
    fffffadd`8755fa70 fffff800`0127ec16 : 00000000`00000100 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtDeviceIoControlFile+0x551
    fffffadd`8755fb90 fffff800`0102e33d : fffff6fb`7dbed000 fffff800`010295d0 fffffadd`a79475f0 00000000`7efd7000 : nt!NtDeviceIoControlFile+0x56
    fffffadd`8755fc00 00000000`78b53e48 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ZwUnloadKey+0x20ad
    00000000`05c1f098 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x78b53e48


    FOLLOWUP_IP:
    kerneld+13d6
    fffffadd`8cf743d6 0f32            rdmsr

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  kerneld+13d6

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  kerneld.amd64

    STACK_COMMAND:  .cxr 0xfffffadd8755eeb0 ; kb

    BUCKET_ID:  WRONG_SYMBOLS

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

    0: kd> lmvm kerneld
    start             end                 module name
    fffffadd`8cf73000 fffffadd`8cf7b000   kerneld    (no symbols)          
        Loaded symbol image file: kerneld.amd64
        Image path: \??\C:\DOCUME~1\clg\LOCALS~1\Temp\RarSFX0\kerneld.amd64
        Image name: kerneld.amd64
        Timestamp:        Sun Oct 14 12:44:15 2007 (47119E9F)
        CheckSum:         00005B15
        ImageSize:        00008000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    0: kd> lmvm nt
    start             end                 module name
    fffff800`01000000 fffff800`01496000   nt         (export symbols)       ntkrnlmp.exe
        Loaded symbol image file: ntkrnlmp.exe
        Image path: ntkrnlmp.exe
        Image name: ntkrnlmp.exe
        Timestamp:        Wed Aug 05 22:09:36 2009 (4A7992A0)
        CheckSum:         00463AC4
        ImageSize:        00496000
        File version:     5.2.3790.4566
        Product version:  5.2.3790.4566
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        1.0 App
        File date:        00000000.00000000
        Translations:     0804.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft(R) Windows(R) Operating System
        InternalName:     ntkrnlmp.exe
        OriginalFilename: ntkrnlmp.exe
        ProductVersion:   5.2.3790.4566
        FileVersion:      5.2.3790.4566 (srv03_sp2_gdr.090805-1438)
        FileDescription:  NT Kernel & System
        LegalCopyright:   (C) Microsoft Corporation. All rights reserved.
    0: kd> .cxr 0xfffffadd8755eeb0
    rax=000000008010204c rbx=fffffadda665dd60 rcx=00000000000000ee
    rdx=fffffadda60c3530 rsi=fffffadda60c3530 rdi=fffffadda6cddd80
    rip=fffffadd8cf743d6 rsp=fffffadd8755f6c0 rbp=000000000000000c
     r8=fffffadda618e340  r9=0000000000000000 r10=fffffadda8fef740
    r11=fffffadda665dd60 r12=fffffadda60c3530 r13=0000000000000001
    r14=0000000000000001 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    kerneld+0x13d6:
    fffffadd`8cf743d6 0f32            rdmsr

    Friday, December 25, 2009 7:29 AM

Answers

  • This is the Windows Home Server forum. I think you're looking for a forum for some other Microsoft operating system, which you'll find over here .
    I'm not on the WHS team, I just post a lot. :)
    Friday, December 25, 2009 3:32 PM
    Moderator