已经把电脑蓝屏故障文本导出，求高人解答！在线等谢谢了！ - 瑞星卡卡安全论坛bbs.ikaka.com

瑞星卡卡安全论坛个人产品讨论区 瑞星杀毒软件 瑞星杀毒软件2011 已经把电脑蓝屏故障文本导出，求高人解答！在线等谢谢了！

	瑞星“1+2”全新解决方案巡展在广州画上圆满句号		叶院长揭秘：瑞星如何运用AI技术革新网络安全		俄乌冲突加剧网络攻击风险白俄罗斯政府遭APT攻击		瑞星ESM防病毒系统助力矿业大学筑牢网络安全防线
	实力拉满瑞星第四十七次通过VB100测评		携手老友，拥抱新精彩 —— 新论坛新活动，感谢你的陪伴		护航司法，瑞星助力山西省高院构建安全防线		人工智能在网络安全领域的风险和机遇

1

1 / 1 页

跳转页

[求助] 已经把电脑蓝屏故障文本导出，求高人解答！在线等谢谢了！

反派人物初生襁褓狮帖子:3 注册: 2011-01-02 来自:	发表于： 2011-01-02 23:11 \| 只看楼主短消息资料字号：小中大 1楼已经把电脑蓝屏故障文本导出，求高人解答！在线等谢谢了！ Microsoft (R) Windows Debugger Version 6.10.0003.233 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini010211-03.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 ntoskrnl.exe, Win32 error 0n2 * WARNING: Unable to verify timestamp for ntoskrnl.exe * ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055c1c0 Debug session time: Sun Jan 2 21:54:12.823 2011 (GMT+8) System Uptime: 0 days 3:54:52.479 ******************************************************************* * 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 ntoskrnl.exe, Win32 error 0n2 * WARNING: Unable to verify timestamp for ntoskrnl.exe * ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ............................................................... ................................................................ ..................... Loading User Symbols Loading unloaded module list .................... Unable to load image GamesGuardNet.dat, Win32 error 0n2 * WARNING: Unable to verify timestamp for GamesGuardNet.dat * ERROR: Module load completed but symbols could not be loaded for GamesGuardNet.dat ***************************************************************************** * * * Bugcheck Analysis * * * ***************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck 100000D1, {e156f180, 2, 0, ba043c7a} * Kernel symbols are WRONG. Please fix symbols to do analysis. * WARNING: Unable to verify timestamp for afd.sys * ERROR: Module load completed but symbols could not be loaded for afd.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 * * * ********************************************************************* ********************************************************************* * * * * * 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 * * * ********************************************************************* ******************************************************************* * 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 : GamesGuardNet.dat ( GamesGuardNet+2c7a ) Followup: MachineOwner --------- 用户系统信息：Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; QQDownload 667; InfoPath.2)
反派人物初生襁褓狮帖子:3 注册: 2011-01-02 来自:	分享到：

反派人物初生襁褓狮帖子:3 注册: 2011-01-02 来自:	发表于： 2011-01-02 23:11 \| 只看楼主短消息资料字号：小中大 2楼回复：已经把电脑蓝屏故障文本导出，求高人解答！在线等谢谢了！我想知道是什么原因导致蓝屏的，请各位高手帮帮忙！谢谢了！
反派人物初生襁褓狮帖子:3 注册: 2011-01-02 来自:

zengjie5927 版主帖子:7974 注册: 2006-01-22 来自:	发表于： 2011-01-03 00:28 \| 短消息资料字号：小中大 3楼回复：已经把电脑蓝屏故障文本导出，求高人解答！在线等谢谢了！请先参考这里的处理步骤 http://bbs.ikaka.com/showtopic-8404665.aspx
zengjie5927 版主帖子:7974 注册: 2006-01-22 来自:

瑞星工程师16 在线技术支持工程师帖子:9362 注册: 2008-09-08 来自:	发表于： 2011-01-03 11:02 \| 短消息资料字号：小中大 4楼回复：已经把电脑蓝屏故障文本导出，求高人解答！在线等谢谢了！蓝屏问题建议您参考版主提供的帖子链接，提供处理蓝屏问题所需的dump文件。如果无法生成该文件。请您跟帖说明，并提供系统日志和应用程序日志。（操作方法http://bbs.ikaka.com/showtopic-8404665.aspx已详细说明）
瑞星工程师16 在线技术支持工程师帖子:9362 注册: 2008-09-08 来自:

西藏耗牛飘泊而立狮帖子:568 注册: 2009-08-02 来自:火星，不解释	发表于： 2011-01-03 17:34 \| 短消息资料字号：小中大 5楼回复：已经把电脑蓝屏故障文本导出，求高人解答！在线等谢谢了！你的这个全部都是内核符号加载错误……神马都没说掀起你的头盖骨来，让我看看你的眼~~ 电信是个黑心厂商，一天劫持我几十遍
西藏耗牛飘泊而立狮帖子:568 注册: 2009-08-02 来自:火星，不解释

<<上一主题|下一主题>>

1

1 / 1 页

跳转页

页面顶部

Powered by Discuz!NT