积极答复者
大家能不能帮我看下我的dump文件啊？谢谢了啊！
问题
-
电脑都是在用的时候，一下子跳电般的重启了，一次是在开VM虚拟机，一次是看网页，都是跳电黑屏重启了，家里供电好的，代码如下，麻烦大神们能不能看看告诉我下啊？麻烦了！
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Administrator\Desktop\012315-20592-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 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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x84a3b000 PsLoadedModuleList = 0x84b85850
Debug session time: Fri Jan 23 20:52:14.110 2015 (GMT+8)
System Uptime: 0 days 7:40:59.351
*********************************************************************
* 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 igdkmd32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, 801ea000, 0, 0}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*** WARNING: Unable to verify timestamp for NETIO.SYS
*** ERROR: Module load completed but symbols could not be loaded for NETIO.SYS
*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
*** WARNING: Unable to verify timestamp for ipnat.sys
*** ERROR: Module load completed but symbols could not be loaded for ipnat.sys
*** WARNING: Unable to verify timestamp for tdx.sys
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
*** WARNING: Unable to verify timestamp for kisnetm.sys
*** ERROR: Module load completed but symbols could not be loaded for kisnetm.sys
*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : igdkmd32.sys ( igdkmd32+7f5bc )
Followup: MachineOwner
---------
答案
-
显示驱动程序有毛病。你看看是不是在浏览器或虚拟机使用 3D 加速时容易出现蓝屏？
Alexis Zhang
http://mvp.microsoft.com/zh-cn/mvp/Jie%20Zhang-4000545
http://blogs.itecn.net/blogs/alexis推荐以 NNTP Bridge 桥接新闻组方式访问论坛。
本帖是回复帖，原帖作者是楼上的 "龙魂天仞"
| 电脑都是在用的时候，一下子跳电般的重启了，一次是在开VM虚拟机，一次是看网页，都是跳电黑屏重启了，家里供电好的，代码如下，麻烦大神们能不能看看告诉我下啊？麻烦了
- 已建议为答案 MedicalSMicrosoft contingent staff, Moderator 2015年2月2日 6:05
- 已标记为答案 MedicalSMicrosoft contingent staff, Moderator 2015年2月4日 3:28
-
首先，楼主的symbol库没有设置正确。请在symbol库路径输入如下信息：
SRV*X:\localsymbols*http://msdl.microsoft.com/download/symbols
X:\localsymbols 这个路径可以随便改。它会下载一个蛮大的包。
具体可以查一下windbg怎么设置symbol库。
然后这个debug的结果里唯一出现的一个文件为igdkmd32.sys，就像Alexis说的，这个文件和显示有关。因为缺少更多信息，推荐你首先去下载并安装一下适合的显卡驱动试一下。最好去官网下载，不要在三方网站或者使用三方工具下载。
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
- 已编辑 MedicalSMicrosoft contingent staff, Moderator 2015年1月26日 10:07
- 已建议为答案 MedicalSMicrosoft contingent staff, Moderator 2015年2月2日 6:05
- 已标记为答案 MedicalSMicrosoft contingent staff, Moderator 2015年2月4日 3:28
全部回复
-
显示驱动程序有毛病。你看看是不是在浏览器或虚拟机使用 3D 加速时容易出现蓝屏？
Alexis Zhang
http://mvp.microsoft.com/zh-cn/mvp/Jie%20Zhang-4000545
http://blogs.itecn.net/blogs/alexis推荐以 NNTP Bridge 桥接新闻组方式访问论坛。
本帖是回复帖，原帖作者是楼上的 "龙魂天仞"
| 电脑都是在用的时候，一下子跳电般的重启了，一次是在开VM虚拟机，一次是看网页，都是跳电黑屏重启了，家里供电好的，代码如下，麻烦大神们能不能看看告诉我下啊？麻烦了
- 已建议为答案 MedicalSMicrosoft contingent staff, Moderator 2015年2月2日 6:05
- 已标记为答案 MedicalSMicrosoft contingent staff, Moderator 2015年2月4日 3:28
-
首先，楼主的symbol库没有设置正确。请在symbol库路径输入如下信息：
SRV*X:\localsymbols*http://msdl.microsoft.com/download/symbols
X:\localsymbols 这个路径可以随便改。它会下载一个蛮大的包。
具体可以查一下windbg怎么设置symbol库。
然后这个debug的结果里唯一出现的一个文件为igdkmd32.sys，就像Alexis说的，这个文件和显示有关。因为缺少更多信息，推荐你首先去下载并安装一下适合的显卡驱动试一下。最好去官网下载，不要在三方网站或者使用三方工具下载。
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
- 已编辑 MedicalSMicrosoft contingent staff, Moderator 2015年1月26日 10:07
- 已建议为答案 MedicalSMicrosoft contingent staff, Moderator 2015年2月2日 6:05
- 已标记为答案 MedicalSMicrosoft contingent staff, Moderator 2015年2月4日 3:28
