您的位置：程序门 -> windows专区 -> windows nt/2000/xp/2003

dmp文件的分析结果，那位帮忙看下

[收藏此页] [打印本页]选择字色：背景色：字体：[大][中][小]

dmp文件的分析结果，那位帮忙看下

发表于：2007-12-28 16:09:07 楼主

今天蓝屏一次，蓝屏代码是 0x00000050 （0x9cda0d40, 0x00000001, 0x9dbf5f6d, 0x00000000)
下面是我用微软的调试器分析dmp文件后的结果

microsoft （r) windows debugger version 6.8.0004.0 x86
copyright （c) microsoft corporation. all rights reserved.

loading dump file [c:\windows\minidump\mini122807-01.dmp]
mini kernel dump file: only registers and stack trace are available

symbol search path is: "d:\143;srv*c:\mylocalsymbols*http://msdl.microsoft.com/download/symbols"
ＥＸＥＣutable search path is:
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 1) mp （4 procs) free x86 compatible
product: server, suite: enterprise terminalserver singleuserts
kernel base = 0x80800000 psloadedmodulelist = 0x808a6ea8
debug session time: fri dec 28 14:36:40.109 2007 （gmt+8)
system uptime: 1 days 20:41:12.671
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, {9cda0d40, 1, 9dbf5f6d, 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 ***
*** ***
*************************************************************************
*** ***
*** 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 ***
*** ***
*************************************************************************

发表于：2007-12-28 16:09:461楼得分:0

*** ***
*** 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 ***
*** ***
*************************************************************************
*** ***
*** 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 ***
*** ***
*************************************************************************
probably caused by : http.sys （ http+1bf6d )

followup: machineowner
那位能帮忙分析下

下一篇：瑞星升级造成用户登陆即重启，换诺顿后系统日志记录：application popup 333
上一篇：怎么样在dos下添加一个服务

其他资讯