Hi !
Thanks for reading this and try to solve my problem.
So, when I'm playing games like Crysis 2, Wow, Lol and more, my pc crashing ~10/15 min after i have launch a game and a black sreen appears.
I tried some solutions to fix it like:
-formatting computer
-update bios mobo
-update chipset mobo
-update/downgrade graphics drivers (safemode + driver sweeper)
-crashs occur with my old RADEON HD 5850, replaced by a HD 6870 by RMA, but crashs still occur
-memtest, 0 errors founded.
-ATI Tray Tool 3D module, crash after 30s/2min.
My pc is clean, all drivers updated, lastest version for all.
When playing, GPU temperature is not over 60°C (around 55/60°C) and CPU temp is about 60/62°C. 12V rail at 11.77V/11.80V.
A good friend and me think the problem is hardware, like alim, or motherboard. But voltages and temps appear so good. So, I require your help to have a better opignion of the problem.
Hard or soft ? And what can i do to solve it ?
Config :
-Windows 7 x64 SP1
-Intel Core i7 860 Socket 1156 2.8GHz
-Motherboard : ASUS P7P55D-E
-RAM 4Go DDR3 G.Skill F3-10666 (9.9.9.24, 1.5V/1.55V)
-GPU ATI RADEON HD 6870
-Alim Cooler Master GX 650W
I can give you other systems informations if you ask me it.
I link you the lastest dmp file.
(For all crashs it's the same dmp, 0x117, atikmpag.sys. If you want to see others ask me !)
Code:
[QUOTE]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa80048604e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800718580c, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
atikmpag+780c
fffff880`0718580c ?? ???
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
BUGCHECK_STR: 0x117
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`08df2490 fffff880`07ea75f7 : fffffa80`048604e0 fffff8a0`0de4d5f6 00000000`00000000 fffff880`07ea733e : watchdog!WdDbgReportRecreate+0xa3
fffff880`08df29b0 fffff880`07ea8075 : fffff8a0`0dfa4ffc fffff8a0`0c940650 fffff8a0`0de4d5f6 00000000`00157a06 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`08df2a00 fffff880`07ea8ce2 : fffffa80`048604e0 fffffa80`048604e0 fffffa80`048f71b0 fffffa80`0591f410 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d
fffff880`08df2aa0 fffff880`07f4ff07 : fffffa80`048604e0 00000000`00000000 fffffa80`048f71b0 fffffa80`0591f410 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`08df2ad0 fffff880`07f7dd5a : fffffa80`ffffffff 00000000`00053e8c fffff880`08df2c30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`08df2bb0 fffff880`07f4b29e : fffffa80`0591f410 ffffffff`feced300 fffffa80`048f71b0 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`08df2bf0 fffff880`07f77e7a : 00000000`00000000 fffffa80`048f71b0 00000000`00000080 fffffa80`0591f410 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`08df2d00 fffff800`02d34fee : 00000000`02726e69 fffffa80`0569db60 fffffa80`036ea040 fffffa80`0569db60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`08df2d40 fffff800`02a8b5e6 : fffff880`009ea180 fffffa80`0569db60 fffff880`009f50c0 fffff880`0121f384 : nt!PspSystemThreadStartup+0x5a
fffff880`08df2d80 00000000`00000000 : fffff880`08df3000 fffff880`08ded000 fffff880`08df2550 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmpag+780c
fffff880`0718580c ?? ???
SYMBOL_NAME: atikmpag+780c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e95eae3
FAILURE_BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys
BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys
Followup: MachineOwner
---------
6: kd> kb
RetAddr : Args to Child : Call Site
fffff880`07ea75f7 : fffffa80`048604e0 fffff8a0`0de4d5f6 00000000`00000000 fffff880`07ea733e : watchdog!WdDbgReportRecreate+0xa3
fffff880`07ea8075 : fffff8a0`0dfa4ffc fffff8a0`0c940650 fffff8a0`0de4d5f6 00000000`00157a06 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`07ea8ce2 : fffffa80`048604e0 fffffa80`048604e0 fffffa80`048f71b0 fffffa80`0591f410 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d
fffff880`07f4ff07 : fffffa80`048604e0 00000000`00000000 fffffa80`048f71b0 fffffa80`0591f410 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`07f7dd5a : fffffa80`ffffffff 00000000`00053e8c fffff880`08df2c30 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`07f4b29e : fffffa80`0591f410 ffffffff`feced300 fffffa80`048f71b0 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`07f77e7a : 00000000`00000000 fffffa80`048f71b0 00000000`00000080 fffffa80`0591f410 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff800`02d34fee : 00000000`02726e69 fffffa80`0569db60 fffffa80`036ea040 fffffa80`0569db60 : dxgmms1!VidSchiWorkerThread+0xba
fffff800`02a8b5e6 : fffff880`009ea180 fffffa80`0569db60 fffff880`009f50c0 fffff880`0121f384 : nt!PspSystemThreadStartup+0x5a
00000000`00000000 : fffff880`08df3000 fffff880`08ded000 fffff880`08df2550 00000000`00000000 : nt!KxStartSystemThread+0x16
6: kd> .bugcheck
Bugcheck code 00000117
Arguments fffffa80`048604e0 fffff880`0718580c 00000000`00000000 00000000`00000000
[/QUOTE]
[/QUOTE]Sorry for my bad written english !
Read english is so easy but write a correctly sentence... ;p
Thanks for your help.
Froze.[/QUOTE]
[B]We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.
The procedure:
* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.
To ensure minidumps are enabled:
* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.
"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".
Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.
As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.
If playing with video driver versions hasn't helped, make sure the box is not overheating.
Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.
If so, it might be as simple as dust buildup and subsequently inadequate cooling.
I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help [URL]http://www.sevenforums.com/crash-lockup-debug-how/63320-stop-0x116-video_tdr_error-troubleshooting.html[/URL]
[/B]
