Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Graphics_Driver_TDR_Timeout


  • Please log in to reply
3 replies to this topic

#1 Nathan D

Nathan D

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:11:24 AM

Posted 29 September 2011 - 01:57 PM

Hi,

Recently my computer display has been freezing and goes black, i have updated the graphics card driver and no luck, the system is my own custom build and has been stable for a good 6 months so seems wierd how this is happening all of a sudden. It happens during normal operation, not a gamer so dont use PC for that purpose. Please See Specs Below and Kernel Dump Log From WinDbg

Specs :

OS : Windows 7 x64
CPU : Intel i3 550 Clarkdale 3.2Ghz - Overclocked to 4.3Ghz (Tested used Intel Burn Test - So is a Stable OC, been running for 6 motnsh no problems)
CPU Cooler : Coolermaster Hyper 212
Mobo : MSI H55M - ED55
PSU : 600w Corsair Builer Series
Ram : 2 x 4Gb Mushkin Silverline 1333Mhz DDR3 9-9-2-4 (Standard, Not O/C'ed)
GPU : MSI ATI Radeon HD5670 OC 1024MB PCI Express
3 x CoolerMaster Case Fans + Aerocool LCD Fan Controller (So no problems with overheating)


WinDbg Log :


Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WD-20110929-1929.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element
Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e0f000 PsLoadedModuleList = 0xfffff800`0304ce50
Debug session time: Thu Sep 29 19:29:44.782 2011 (UTC + 1:00)
System Uptime: 0 days 5:18:17.844
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, {fffffa800db64010, fffff880073ae45c, 0, 0}

Unable to load image 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
Probably caused by : atikmpag.sys ( atikmpag+745c )

Followup: MachineOwner
---------

2: 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: fffffa800db64010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880073ae45c, 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+745c
fffff880`073ae45c ?? ???

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`057ba190 fffff880`0414b4ef : fffffa80`0db64010 102906c9`a00038bf 00000000`00000000 fffffa80`0f3be901 : watchdog!WdDbgReportRecreate+0xa3
fffff880`057ba6b0 fffff880`0414bf6d : fffff8a0`32f5cffc fffff8a0`2cf451a0 fffff8a0`32e058c4 00000000`00157738 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`057ba700 fffff880`0414cbda : fffffa80`0db64010 fffffa80`0db64010 fffffa80`0c3c67c0 fffffa80`0f3be010 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d
fffff880`057ba7a0 fffff880`042cbf07 : fffffa80`0db64010 00000000`00000000 fffffa80`0c3c67c0 fffffa80`0f3be010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`057ba7d0 fffff880`042f9d7e : 00000000`ffffffff 00000000`0012ab10 fffff880`057ba930 fffffa80`0f3be010 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`057ba8b0 fffff880`042f5ca5 : fffffa80`0b275000 ffffffff`feced300 fffffa80`09925dc0 fffff880`042da8af : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`057ba8f0 fffff880`042f5e5d : fffffa80`0b275000 fffffa80`0f3be010 fffffa80`0b276600 00000000`00000000 : dxgmms1!VidSchiWaitForCompletePreemption+0x7d
fffff880`057ba9e0 fffff880`042f4d3c : 00000000`000000af 00000000`0002b54a fffffa80`09925dc0 fffffa80`0f3be010 : dxgmms1!VidSchiSendToExecutionQueueWithWait+0x171
fffff880`057baae0 fffff880`042f4398 : fffff800`00b96000 fffff880`042f3d00 fffffa80`00000000 fffffa80`00002d80 : dxgmms1!VidSchiSubmitRenderCommand+0x920
fffff880`057bacd0 fffff880`042f3e96 : 00000000`00000000 fffffa80`0c3c67c0 00000000`00000080 fffffa80`0f3be010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`057bad00 fffff800`03124166 : fffff880`08dc0bc0 fffffa80`0fae9040 fffffa80`06c625f0 fffff800`02e78d87 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`057bad40 fffff800`02e5f486 : fffff800`02ff9e80 fffffa80`0fae9040 fffff800`03007c40 fffff880`01234a90 : nt!PspSystemThreadStartup+0x5a
fffff880`057bad80 00000000`00000000 : fffff880`057bb000 fffff880`057b5000 fffff880`08e7ea90 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+745c
fffff880`073ae45c ?? ???

SYMBOL_NAME: atikmpag+745c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4dae3558

FAILURE_BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys

Followup: MachineOwner
---------



Any Suggests - I know its a graphics card issue, but ive tried updating driver's and rolling back still no joy, really annoying me know.

Any Info/Suggests much appreciated

Thanks,
Nathan

BC AdBot (Login to Remove)

 


#2 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:06:24 AM

Posted 30 September 2011 - 02:43 PM

Hello welcome to Bleeping Computer and welcome to the Windows 7 video card crash club.

I had issues with my Nvidia GeForce 6200 doing the same thing, windows recovered from an unexpected error with..... I debugged my driver and the video card bit the dust.

I am not on that computer because I am presently waiting for another video card to come in to replace my dead Nvidia 6200.

During the debugging of the nvlddmkm.sys driver, my video card went kaput and displayed a black screen right as the nvlddmkm.sys driver loaded. Debugging a few more times caused the card to display nothing.

If you Google nvlddmkm.sys or atikmpag.sys 9 out of 10 hits will be Windows 7 32 or 64 Bit errors related to "windows recovered from an unexpected error related to atikmpag.sys or
nvlddmkm.sys and Direct X.

I had a link saved on my other computer, which I won't be able to get until my video card comes in to replace my 6200, but it covered this error extensively and I wish I could remember the link off the top of my head.

If your card is like my 6200, it is bricked and the chip would have to be replaced if you wished to save the card. You are better off buying a new card, the chip requires some special tools to replace it.

I plan on doing extensive research once my system is back up again as to why both Nvidia and ATI/AMD video cards are experiencing high time out errors with windows 7.

That is what your problem was, it was taking your video card longer than 3 seconds to respond and windows chooses to force a shut down and restart of your video stream.

There is a setting in the windows REGISTRY that can be changed to 5 seconds or even longer to prevent this VIDEO_TDR_TIMEOUT_DETECTED error from displaying, however your graphics will still lag during that time frame, where it would normally cause a brief blackout of your video and then the notice popping up from your notification area.

Bruce.
Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:

#3 Nathan D

Nathan D
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:11:24 AM

Posted 03 October 2011 - 05:04 PM

thanks for the info, ive actually swapped the card t a new PCI-E slot on my mobo and all seems to be fine, both slots are both 2.0 x 16 so dont know why it was mis-behaving in the other slot.

It was fine for a goood 6 months seems very strange, may just invest ina new card anyway to be on the safe side

thanks

#4 MrBruce1959

MrBruce1959

    My cat Oreo


  • BC Advisor
  • 6,377 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Norwich, Connecticut. in the USA
  • Local time:06:24 AM

Posted 13 October 2011 - 06:53 AM

Well to update you, I received a new GeForce 6200 video card, this one being 512MB instead of 256MB like my other one was.

Turns out the slot on the motherboard was also an issue as well. I tried recooking the motherboard hoping to correct a possible solder joint issue.

If you have ever tried replacing a slot on a motherboard before or not, let me tell you the solder they are using these days on electronics is very hi temp solder and it takes a lot of heat to bake a board hot enough to get an AGP or PCI-E slot off of the board with one pull.

Usually the plastic slot softens and the 124 pins remain in the motherboard while the slot slips off of the pins. You can not get those pins back into the slot without mega issues.

Motherboards are two sided highways of thousands circuit traces and it is one hell of a chore cleaning those remaining pins out of the board, cleaning the holes out where the 124 pins once entered the motherboard holes and clean up the board for the application of another AGP slot.

The next chore is getting the new slot into the holes without a single pin bending and missing the hole, the next chore is getting the solder to flow on both sides of the motherboard, specially the solder connections underneath the slot.
Once the slot is in the board, there is no way to place a soldering iron tip on the traces under it.

Keep in mind, some pins solder on the top of the board, others solder on the bottom side, those on the bottom are easy because they are in plain view, while the top connections are now hidden under the plastic slot.

If anyone reading this thread ever wishes to replace a slot, it always best to replace with a new undamaged slot.

I often use digi-key as a motherboard parts replacement source, they're web address is http://www.digikey.com you do not need a business account to order parts from them.
There is a menu on the left side of that page, look for the one called catalog, or use the search bar and type what you're looking for, chances are they will have it, including most connectors or chips found on any electronics hardware.

Bruce.

Edited by MrBruce1959, 13 October 2011 - 07:07 AM.

Welcome to Bleeping Computer! :welcome:
New Members: Please click here for the Bleeping Computer Forum Board Rules
 
My Career Involves 37 Years as an Electronics Repair Technician, to Which I am Currently Retired From.

I Am Currently Using Windows 10 Home Edition.

As a Volunteer Staff Member of Bleeping Computer, the Help That I Proudly Provide Here To Our BC Forum Board Membership is Free of Charge. :wink:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users