New
#11
I did not see the FurMark results; I must have missed them. Where are they?
You definitely have a video problem.
Note that the cause can be in subsystem. Do yo have another video card you can try?STOP 0x00000117: VIDEO_TDR_TIMEOUT_DETECTED
Usual causes: Video driver/sub-system
No.. I do not have another video card I can try...
Any other suggestions? Thanks for the help so far.
Where did you post your FurMark results. I must be blind; I did not see them. Do you have any additional mini dumps later than the one you uploaded? If so, please upload them. Have you tried to reseat your graphics card?
Right above your post but since you say you can't see them I've uploaded them to external site: http://i37.tinypic.com/2uzcxtz.jpg
I do not have anymore mini dumps, the last one was from 14/08/2010 which I've already uploaded...
Also I've googled for half hour and couldn't find updated AtiPcie.sys, last one I found was from 2007 which isn't good at all...
One more thing, When I looked at Event Viewer I see alot [Really, alot] of messages about amdkmdag:
External link: http://i36.tinypic.com/52gh8j.jpg
And It goes on, 13/8, 14/8 etc...
There isn't any details about this information just Binary data...
This isn't normal... right?
I don't think there is an update available for AtiPcie.sys. Don't worry about it for now.
The event viewer items are information items. They are not errors. You can right click on any of them, select properties, and read the information.
I am thinking your problem is either your graphics card or possibly your power supply. I don't know a way to check either of these possibilities short of trying another graphics card and another power supply. Remember the dump definitely pointed to a graphics card error. A faulty or failing power supply can trigger all kinds of errors.
Here is another crash dump from five minutes ago...
Another thing when the games crash the computer does not restart automatically I hear some noise and than the screen goes black, I have to press the restart button on the case for the computer to restart completely.
This is obviously a video error. The dumps blames atikmpag.sys. For more information on TDR errors, read this post:STOP 0x00000117: VIDEO_TDR_TIMEOUT_DETECTED
Usual causes: Video driver/sub-system
Video's crashing the display driver (ATI HD5870)
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_WD-20100817-2227.zip\WD-20100817-2227.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Debug session time: Tue Aug 17 15:27:10.167 2010 (GMT-4) System Uptime: 1 days 22:53:27.792 Loading Kernel Symbols ............................................................... ................................................................ ................ Loading User Symbols Mini Kernel Dump does not contain unloaded driver list ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 117, {fffffa8004a7b4e0, fffff88003eb9c80, 0, 0} *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys Probably caused by : atikmpag.sys ( atikmpag+6c80 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * 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: fffffa8004a7b4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff88003eb9c80, 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+6c80 fffff880`03eb9c80 ?? ??? 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`031d44a0 fffff880`03f544ef : fffffa80`04a7b4e0 fffff8a0`0e55d8b7 00000000`00000000 fffff880`03f54234 : watchdog!WdDbgReportRecreate+0xa3 fffff880`031d49c0 fffff880`03f54f6d : fffff8a0`0e6b4ffc fffff8a0`09b1ae10 fffff8a0`0e55d8b7 00000000`00157745 : dxgkrnl!TdrUpdateDbgReport+0xcb fffff880`031d4a10 fffff880`03f55bda : fffffa80`04a7b4e0 fffffa80`04a7b4e0 fffffa80`0469c010 fffffa80`04f50410 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d fffff880`031d4ab0 fffff880`0460ff07 : fffffa80`04a7b4e0 00000000`00000000 fffffa80`0469c010 fffffa80`04f50410 : dxgkrnl!TdrIsRecoveryRequired+0x17a fffff880`031d4ae0 fffff880`04639b75 : fffff8a0`ffffffff 00000000`00a4d6d8 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`031d4bc0 fffff880`0460b2d5 : fffffa80`04f50410 fffffa80`00000000 00000000`00a4d6d8 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`031d4bf0 fffff880`04637e7a : 00000000`00000000 fffffa80`0469c010 00000000`00000080 fffffa80`04f50410 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9 fffff880`031d4d00 fffff800`02d78c06 : 00000000`01fccafd fffffa80`055efa10 fffffa80`03973890 fffffa80`055efa10 : dxgmms1!VidSchiWorkerThread+0xba fffff880`031d4d40 fffff800`02ab2c26 : fffff800`02c4ee80 fffffa80`055efa10 fffff800`02c5cc40 fffff880`0122c534 : nt!PspSystemThreadStartup+0x5a fffff880`031d4d80 00000000`00000000 : fffff880`031d5000 fffff880`031cf000 fffff880`08c7db60 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: atikmpag+6c80 fffff880`03eb9c80 ?? ??? SYMBOL_NAME: atikmpag+6c80 FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmpag IMAGE_NAME: atikmpag.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c33d53e FAILURE_BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys Followup: MachineOwner ---------
Finally, The problem is solved... I took the computer to my PC vendor, the problem was the PSU overheating and that made the graphic card fail... I'm not sure why the crash dumps blamed ATI.
Also my computer case is not big enough for all this big hardware and there is a lot of heat I need to find a new case now that will help me with cooling down my hardware... any suggestions?