*******************************************************************************
* *
* Bugcheck Analysis *
* *
******************************************************************************* VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 87fef490, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 9c6ca4ba, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data. Debugging Details:
------------------ *** ERROR: Module load completed but symbols could not be loaded for dxgmms1.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 ***
*** ***
*************************************************************************
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
********************************************************************* ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. FAULTING_MODULE: 84013000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4f02671d FAULTING_IP:
atikmpag+64ba
9c6ca4ba 8bff mov edi,edi DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT BUGCHECK_STR: 0x116 CURRENT_IRQL: 0 STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8d8d6b74 9e79a07b 00000116 87fef490 9c6ca4ba nt!KeBugCheckEx+0x1e
8d8d6b98 9e78e937 9c6ca4ba 00000000 00000002 dxgkrnl!TdrIsTimeoutForcedFlip+0xf4
8d8d6bbc 9e7ca92c 00000000 00000102 8976e788 dxgkrnl!TdrIsRecoveryRequired+0xb8
8d8d6c34 9e7f4944 fffffcfb 00086e66 00000000 dxgmms1+0x692c
8d8d6c5c 9e7f5065 00000000 00000000 00000000 dxgmms1+0x30944
8d8d6c98 9e7d18f0 8d8d6c90 89bb3210 87e9bb80 dxgmms1+0x31065
8d8d6d28 9e7f63c9 8976e788 8404a50e 8976e788 dxgmms1+0xd8f0
8d8d6d3c 9e7f6485 8976e788 00000000 896e6538 dxgmms1+0x323c9
8d8d6d50 8421cf5e 8976e788 a6682924 00000000 dxgmms1+0x32485
8d8d6d90 840c4219 9e7f6406 8976e788 00000000 nt!RtlAnsiStringToUnicodeString+0x19d
00000000 00000000 00000000 00000000 00000000 nt!KeInitializeTimerEx+0x3c8
STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP:
atikmpag+64ba
9c6ca4ba 8bff mov edi,edi SYMBOL_NAME: atikmpag+64ba FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmpag IMAGE_NAME: atikmpag.sys BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner
---------
电脑蓝屏，这是windbg分析下的代码，求解决啊
我知道是显卡驱动问题，不过换了几个驱动都没用

此贴必火，不火就是我弄沉的！

果断去换显卡然后再换系统