电脑蓝屏。WINDBG分析下来的，看不懂？

caocao658

电脑刚升级，我说下基本情况吧CPU：I5 760 主板：华硕P7H55-M 显卡：迪兰恒进(Dataland)HD6850恒金1G 775/4000 1024M/256位 GDDR5 PCI-E 显卡 内存：金士顿DDR3 4G2 一共8G 电源：振华(SUPER FLOWER)战蝶400W电源 刚配时候一点问题都没 跑暗黑3啊 没出现过什么状况。一开始只配了一根4G内存后来加过一根4G 过了几天，玩暗黑3收卡屏幕 声音也卡主了，死机。热启动后进游戏又自动重启了。以后几天一切正常。。。也没去管它。昨天看优酷视频时候。电脑直接蓝屏了。。。。。我就搞不清状况了
DMP文件显示这个，又看不懂
osoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\061912-19250-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 \SystemRoot\system32\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 x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0421a000 PsLoadedModuleList = 0xfffff800`0445e670
Debug session time: Tue Jun 19 20:06:49.437 2012 (GMT+8)
System Uptime: 0 days 2:21:45.888
*********************************************************************
* 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 \SystemRoot\system32\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 \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8003c724e0, fffff8800581e768, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.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 : atikmpag.sys ( atikmpag+8768 )

Followup: MachineOwner

流年春去

应该是提示路径无效的。也就是说找不到引导盘。

caocao658

斑竹什么意思？？？不是显卡问题吗

流年春去

caocao658 发表于 2012-6-20 14:32
斑竹什么意思？？？不是显卡问题吗

你把那些英文用谷歌翻译一下，就大概能看清楚了。
另，你试下，能启动到安全模式不。

caocao658

流年春去 发表于 2012-6-20 14:37
你把那些英文用谷歌翻译一下，就大概能看清楚了。
另，你试下，能启动到安全模式不。

不是系统能进去的，也不蓝屏 就是看视频要蓝屏。。
对了我内存应该是8G 64位系统。。
但是系统属性里显示8G(3.96G)可用。。。
会不会内存问题。。用软件看显示两根内存，但是进BIOS只认出1根内存。。会不会蓝屏是这个原因造成的
进系统后显示异常中恢复 ATI DRIVER停止工作。。

流年春去

你把显卡驱动重新安装一下，看看能行不。

caocao658

流年春去 发表于 2012-6-20 14:47
你把显卡驱动重新安装一下，看看能行不。

OK 驱动重新装了 以前没蓝屏过。。。就昨天悲剧啊。

流年春去

caocao658 发表于 2012-6-20 14:51
OK 驱动重新装了 以前没蓝屏过。。。就昨天悲剧啊。

现在呢，一看视频还是蓝屏吗
你进安全模式，恢复到最近的正确配置

caocao658

流年春去 发表于 2012-6-20 15:02
现在呢，一看视频还是蓝屏吗
你进安全模式，恢复到最近的正确配置

我开了很多视频 目前也没出现过。。。。
看以后情况了
还有一情况斑竹
我8G内存 在系统属性里只显示3.96G可用。。。
什么情况？

流年春去

caocao658 发表于 2012-6-20 15:05
我开了很多视频 目前也没出现过。。。。
看以后情况了
还有一情况斑竹

你是什么系统啊，XP的话不支持大内存。