none
windows 2008r2 无故多次蓝屏重启,现收集小内存DUMP日志请大神帮忙分析下 RRS feed

  • 问题

  • 从9月20号开始前后一共崩溃了6次,我把minidump文件夹打包发到百度网盘上了。如果看不出来,是不是还得启用特殊池来收集?

    http://pan.baidu.com/s/1geNtTcB

    这是6个dump文件中最近一个文件的内容,这个50代码貌似跟第一次蓝屏的代码不一样

    Use !analyze -v to get detailed debugging information.
    BugCheck 50, {fffffa80757ff000, 1, fffff88006d517f5, 0}
    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************
    *** WARNING: Unable to verify timestamp for srv.sys
    *** ERROR: Module load completed but symbols could not be loaded for srv.sys
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : srv.sys ( srv+6c7f5 )
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffffa80757ff000, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff88006d517f5, If non-zero, the instruction address which referenced the bad memory
     address.
    Arg4: 0000000000000000, (reserved)
    Debugging Details:
    ------------------
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************
    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: srv
    FAULTING_MODULE: fffff80001663000 nt
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc257
    WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
     fffffa80757ff000
    FAULTING_IP:
    srv+6c7f5
    fffff880`06d517f5 c60300          mov     byte ptr [rbx],0
    MM_INTERNAL_CODE:  0
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
    BUGCHECK_STR:  0x50
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff800017541e4 to fffff800016d4f00
    STACK_TEXT: 
    fffff880`06e356f8 fffff800`017541e4 : 00000000`00000050 fffffa80`757ff000 00000000`00000001 fffff880`06e35860 : nt+0x71f00
    fffff880`06e35700 00000000`00000050 : fffffa80`757ff000 00000000`00000001 fffff880`06e35860 00000000`00000000 : nt+0xf11e4
    fffff880`06e35708 fffffa80`757ff000 : 00000000`00000001 fffff880`06e35860 00000000`00000000 00000000`00000000 : 0x50
    fffff880`06e35710 00000000`00000001 : fffff880`06e35860 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`757ff000
    fffff880`06e35718 fffff880`06e35860 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
    fffff880`06e35720 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`01862880 : 0xfffff880`06e35860

    STACK_COMMAND:  .bugcheck ; kb
    FOLLOWUP_IP:
    srv+6c7f5
    fffff880`06d517f5 c60300          mov     byte ptr [rbx],0
    SYMBOL_NAME:  srv+6c7f5
    FOLLOWUP_NAME:  MachineOwner
    IMAGE_NAME:  srv.sys
    BUCKET_ID:  WRONG_SYMBOLS
    Followup: MachineOwner
    ---------

    2017年10月9日 10:22

全部回复