none
DUMP日志请教问题原因 RRS feed

  • 常规讨论

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


    Loading Dump File [C:\Users\hpms\Desktop\10.25.52.12\Mini033012-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are 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+                                    *
    *********************************************************************
    Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
    Product: Server, suite: Enterprise TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
    Debug session time: Fri Mar 30 16:30:15.139 2012 (GMT+8)
    System Uptime: 284 days 6:01:03.436
    *********************************************************************
    * 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+                                    *
    *********************************************************************
    Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ...............................................................
    ....................................................
    Loading User Symbols
    Loading unloaded module list
    ..................................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {bc5f0a10, 0, bf97d7d1, 0}

    ***** 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 win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    *** WARNING: Unable to verify timestamp for msgpc.sys
    *** ERROR: Module load completed but symbols could not be loaded for msgpc.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                                     ***
    ***                                                                   ***
    *************************************************************************
    *********************************************************************
    * 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 : msgpc.sys ( msgpc+3d00 )

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

    2: 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: bc5f0a10, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: bf97d7d1, If non-zero, the instruction address which referenced the bad memory
     address.
    Arg4: 00000000, (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                                     ***
    ***                                                                   ***
    *************************************************************************
    *********************************************************************
    * 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: msgpc

    FAULTING_MODULE: 80800000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  45d6998d

    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
     bc5f0a10

    FAULTING_IP:
    win32k+17d7d1
    bf97d7d1 ??              ???

    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 8085ecf1 to 80827c63

    STACK_TEXT: 
    WARNING: Stack unwind information not available. Following frames may be wrong.
    b8fa0218 8085ecf1 00000050 bc5f0a10 00000000 nt+0x27c63
    b8fa0290 8088c798 00000000 bc5f0a10 00000000 nt+0x5ecf1
    b8fa02a8 bf97d7d1 badb0d00 00000000 80a5c3d9 nt+0x8c798
    b8fa0348 bf80e390 ea40c3f8 034c0000 0005db3c win32k+0x17d7d1
    b8fa09ec bf80ff7c ea40c3f8 034c0000 0005db3c win32k+0xe390
    b8fa0a74 bf80feb6 ea40c3f8 034c0000 0005db3c win32k+0xff7c
    b8fa0ac4 bf80fb94 00000001 ea40c3f0 e7ca1568 win32k+0xfeb6
    b8fa0af4 bf8118e2 00000001 ea40c3f0 e7ca1568 win32k+0xfb94
    b8fa0b2c bf818a10 b8fa0c88 00000020 ea40c3f0 win32k+0x118e2
    b8fa0bb4 bf819009 b8fa0c88 00000020 00000001 win32k+0x18a10
    b8fa0bfc bf818f36 b8fa0c88 00000020 00000001 win32k+0x19009
    b8fa0d44 8088978c 000868b0 00000020 00000001 win32k+0x18f36
    b8fa0d64 7c9585ec badb0d00 0006fd3c 00000000 nt+0x8978c
    b8fa0d68 badb0d00 0006fd3c 00000000 00000000 0x7c9585ec
    b8fa0d6c 0006fd3c 00000000 00000000 00000045 msgpc+0x3d00
    b8fa0d70 00000000 00000000 00000045 00000000 0x6fd3c


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    msgpc+3d00
    badb0d00 ??              ???

    SYMBOL_STACK_INDEX:  e

    SYMBOL_NAME:  msgpc+3d00

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  msgpc.sys

    BUCKET_ID:  WRONG_SYMBOLS

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

    请教是什么原因引起的msgpc.sys文件崩溃的,是某一个进程还是别的么?多谢~

     

    2012年4月1日 4:40

全部回复

  • 不太好判断准确原因,但应该不是特定进程引起 MSGPC.SYS 错误。
     
    建议测试一下安全模式会不会出现此问题。如果安全模式也有,可能是内存错误或 NTFS 卷损坏;如果安全模式正常,应该是软件兼容问题导致。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "huamk"
     
    IMAGE_NAME: msgpc.sys
    请教是什么原因引起的msgpc.sys文件崩溃的,是某一个进程还是别的么?多谢~
     
     
    2012年4月1日 22:25
    版主
  • 就蓝屏了一次,然后就好了!analyze -v的信息

    到现在也没再出现过,会是硬件的问题吗?多谢多谢.

    2: 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: bc5f0a10, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: bf97d7d1, If non-zero, the instruction address which referenced the bad memory
     address.
    Arg4: 00000000, (reserved)

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


    Could not read faulting driver name

    READ_ADDRESS:  bc5f0a10

    FAULTING_IP:
    win32k!bLoadTTF_Cache+1f
    bf97d7d1 8b06            mov     eax,dword ptr [esi]

    MM_INTERNAL_CODE:  0

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  csrss.exe

    CURRENT_IRQL:  1

    TRAP_FRAME:  b8fa02a8 -- (.trap 0xffffffffb8fa02a8)
    ErrCode = 00000000
    eax=b8fa0338 ebx=e76f4af0 ecx=00000000 edx=00000000 esi=bc5f0a10 edi=e76f4b14
    eip=bf97d7d1 esp=b8fa031c ebp=b8fa0348 iopl=0         nv up ei ng nz ac po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010292
    win32k!bLoadTTF_Cache+0x1f:
    bf97d7d1 8b06            mov     eax,dword ptr [esi]  ds:0023:bc5f0a10=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 8085ecf1 to 80827c63

    STACK_TEXT: 
    b8fa0218 8085ecf1 00000050 bc5f0a10 00000000 nt!KeBugCheckEx+0x1b
    b8fa0290 8088c798 00000000 bc5f0a10 00000000 nt!MmAccessFault+0xb25
    b8fa0290 bf97d7d1 00000000 bc5f0a10 00000000 nt!KiTrap0E+0xdc
    b8fa0348 bf80e390 ea40c3f8 034c0000 0005db3c win32k!bLoadTTF_Cache+0x1f
    b8fa09ec bf80ff7c ea40c3f8 034c0000 0005db3c win32k!bLoadTTF+0x33
    b8fa0a74 bf80feb6 ea40c3f8 034c0000 0005db3c win32k!bLoadFontFile+0x228
    b8fa0ac4 bf80fb94 00000001 ea40c3f0 e7ca1568 win32k!ttfdSemLoadFontFile+0x4c
    b8fa0af4 bf8118e2 00000001 ea40c3f0 e7ca1568 win32k!PDEVOBJ::LoadFontFile+0x3a
    b8fa0b2c bf818a10 b8fa0c88 00000020 ea40c3f0 win32k!vLoadFontFileView+0x94
    b8fa0bb4 bf819009 b8fa0c88 00000020 00000001 win32k!PUBLIC_PFTOBJ::bLoadFonts+0x1dc
    b8fa0bfc bf818f36 b8fa0c88 00000020 00000001 win32k!GreAddFontResourceWInternal+0xad
    b8fa0d44 8088978c 000868b0 00000020 00000001 win32k!NtGdiAddFontResourceW+0x163
    b8fa0d44 7c9585ec 000868b0 00000020 00000001 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0006fd6c 00000000 00000000 00000000 00000000 0x7c9585ec


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    win32k!bLoadTTF_Cache+1f
    bf97d7d1 8b06            mov     eax,dword ptr [esi]

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  win32k!bLoadTTF_Cache+1f

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME:  win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  45d6a129

    FAILURE_BUCKET_ID:  0x50_win32k!bLoadTTF_Cache+1f

    BUCKET_ID:  0x50_win32k!bLoadTTF_Cache+1f

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

     

    2012年4月5日 3:10
  • 那可以再观察一阵,看看问题会不会再次出现。硬件问题的可能性不大。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "huamk"
     
    就蓝屏了一次,然后就好了!analyze -v的信息
    到现在也没再出现过,会是硬件的问题吗?多谢多谢.
     
     
    2012年4月5日 20:07
    版主