一玩游戏就蓝屏

[daijie_china]

原来是用的xp，玩游戏的时候突然蓝屏过一次以后重启继续玩结果就以后的每次一玩游戏机器就黑屏假死（屏幕黑屏无显示，主机还在运行）（原来玩的还好好的，玩魔兽，cf都可以的，根本不存在机器配置低的问题），后来我按照网上的信息把机箱的灰尘除了，显卡驱动也更新了，还有等等一些方法我也都试过了，还是不行。有人说是ghost系统不稳定，我就装xp安装纯净版的，还是不行，现在我换成了windows7试了下，还是这个情况，好在windows7 可以显示错误信息，现在我把它贴出来，请大家帮看下
问题签名:
问题事件名称: BlueScreen
OS 版本: 6.1.7100.2.0.0.256.1
区域设置 ID: 2052

有关该问题的其他信息:
BCCode: 116
BCP1: FFFFFA80018114E0
BCP2: FFFFF88004077F7C
BCP3: FFFFFFFFC0000001
BCP4: 0000000000000003
OS Version: 6_1_7100
Service Pack: 0_0
Product: 256_1

有助于描述该问题的文件:
C:\Windows\Minidump\061909-18656-01.dmp
C:\Users\nemo\AppData\Local\Temp\WER-59671-0.sysdata.xml

[daijie_china]

自己顶，不让帖子沉了，大虾们帮帮忙啊

[jxc25]

BCCode: 116 //显示驱动失败
BCP1: FFFFFA80018114E0 //失败点
BCP2: FFFFF88004077F7C//驱动名
BCP3: FFFFFFFFC0000001 //微软1号错误
BCP4: 0000000000000003 //未知

[scriptfan]

晕，买的什么水货显卡啊？

[shuihan20e]

jf

[xuzheng318]

显卡问题！

[古井荡月]

换个显卡驱动试试。。

[neohope]

你的显示芯片是什么？去找最新驱动试试，另外有些芯片有缺陷的

[archdevil1]

重新装个新的驱动试试

[novernover]

如果超频了 降回默认试试

[stonepeter]

Windows7的Update可能有一些可选的你的显卡驱动,试试看能否修复你的问题.
还有一种可能就是机器会不会过热?你可以试一下打开节能选项试试看.
http://topic.csdn.net/u/20090619/14/9b84eb49-4310-469e-a63f-38f6e855278d.html
当然,换个显卡试试是最有意义的.

[saharaye]

应该是驱动的问题吧

[wwj027]

兼容性问题

[susedemei]

大虾们帮帮忙啊

[hitman1102]

http://blog.sina.com.cn/s/blog_4bb6d5cc0100dxtn.html

[daijie_china]

问题已经由jxc25 大虾帮我找出，但问题还没解决，先结贴给分，等下在开一贴
Loading Dump File [C:\Users\nemo\Desktop\062509-15734-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 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02a66000 PsLoadedModuleList = 0xfffff800`02c9fe90
Debug session time: Thu Jun 25 00:02:42.110 2009 (GMT+8)
System Uptime: 0 days 0:03:11.032

[daijie_china]

*********************************************************************
* 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, {fffffa8000f73010, fffff88004863f7c, ffffffffc0000001, 3}

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

[daijie_china]

*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : atikmdag.sys ( atikmdag+11f7c )

Followup: MachineOwner