Updated 24th February 2012:[list]
[*] Additional information on potential driver bug triggering TDRs with 28x.xx and 290.xx drivers. EDIT - updated 29th Feb, a number of users reporting 295.73 resolves the issue.
[*] More examples of the problem being fixed added
[*] Updated Microsoft definitions and links
[/list]
This thread has grown quite lengthy, but hopefully is still useful for people. If you are having 'driver not responding' errors then please read this post so that you understand exactly what the issue is and how varied the causes can be - plus you may find a resolution within.

Just as a 'disclaimer' here, this thread is not intended for everyone to post their problems on... The purpose of this thread is to try and help you, but also to prevent multiple topics on the same subject. Lots of people have seen these errors, so hopefully this thread should help you understand exactly what you are seeing before you post. I have seen and responded to a lot of TDR related topics now where people have not made the effort to do any prior searching.

The generic error people visit this forum for is: 'Display driver nvlddmkm stopped responding and was recovered.'

This is also seen as:
'Display driver atikmdag stopped responding and was recovered.' (AMD/ATI cards)
'Display driver xxxxxxxx stopped responding and was recovered.' (others)

Also noted as nvlddmkm.sys, atikmdag.sys, and xxxxxxxx.sys bug-check/BSOD.

As a starting note, this is not an nVidia issue. It is not an ATI issue either. These errors are triggered by a Windows service called 'Timeout Detection and Recovery' (TDR). You will only see this error on Windows Vista and Windows 7, as TDR is a feature of the new WDDM driver model (implemented first in Windows Vista). TDR is supposed to be there to help stop BSOD's by resetting the GPU and/or driver when there is an issue or long delay. If the problem happens multiple times in a row, a BSOD can occur.

If you are having this problem frequently then you will probably find it very frustrating, however be reassured that the problem is normally perfectly solvable, although can take some troubleshooting to resolve. I personally have seen this issue on two separate nVidia builds, and an Intel onboard GPU.

[b]How does TDR work?[/b]
[size="2"][quote][u]Timeout Detection and Recovery[/u]
Windows Vista and later operating systems attempt to detect situations in which computers appear to be completely "frozen". They then attempt to dynamically recover from the frozen situations so that their desktops are responsive again. This process of detection and recovery is known as timeout detection and recovery (TDR). In the TDR process, the operating system's GPU scheduler calls the display miniport driver's [url="http://msdn.microsoft.com/en-us/library/windows/hardware/ff559815(v=vs.85).aspx"]DxgkDdiResetFromTimeout[/url] function to reinitialize the driver and reset the GPU. Therefore, end users are not required to reboot the operating system, which greatly enhances their experience. The only visible artifact from the hang detection to the recovery is a screen flicker. This screen flicker results when the operating system resets some portions of the graphics stack, which causes a screen redraw. Some legacy DirectX applications (for example, those DirectX applications that conform to DirectX versions earlier than 9.0) might render to a black screen at the end of this recovery. The end user would have to restart these applications.

The following sequence briefly describes the TDR process:

[list]1. Timeout detection
The GPU scheduler, which is part of the DirectX graphics kernel subsystem (Dxgkrnl.sys), detects that the GPU is taking more than the permitted amount of time to execute a particular task. The GPU scheduler then tries to preempt this particular task. The preempt operation has a "wait" timeout, which is the actual TDR timeout. This step is thus the timeout detection phase of the process. The default timeout period in Windows Vista and later operating systems is 2 seconds. If the GPU cannot complete or preempt the current task within the TDR timeout period, the operating system diagnoses that the GPU is frozen.

To prevent timeout detection from occurring, hardware vendors should ensure that graphics operations (that is, DMA buffer completion) take no more than 2 seconds in end-user scenarios such as productivity and game play.

2. Preparation for recovery:
The operating system's GPU scheduler calls the display miniport driver's DxgkDdiResetFromTimeout function to inform the driver that the operating system detected a timeout. The driver must then reinitialize itself and reset the GPU. In addition, the driver must stop accessing memory and should not access hardware. The operating system and the driver collect hardware and other state information that could be useful for post-mortem diagnosis.

3. Desktop recovery:
The operating system resets the appropriate state of the graphics stack. The video memory manager, which is also part of Dxgkrnl.sys, purges all allocations from video memory. The display miniport driver resets the GPU hardware state. The graphics stack takes the final actions and restores the desktop to the responsive state. As previously mentioned, some legacy DirectX applications might render just black at the end of this recovery, which requires the end user to restart these applications. Well-written DirectX 9Ex and DirectX 10 and later applications that handle Device Remove technology continue to work correctly. An application must release and then recreate its Direct3D device and all of the device's objects. For more information about how DirectX applications recover, see the Windows SDK.[/list][/quote][/size]

[b]Limiting Repetitive GPU Hangs and Recoveries[/b]
[size="2"][quote]
Beginning with Windows Vista with Service Pack 1 (SP1) and Windows Server 2008, the user experience has been improved in situations where the GPU hangs frequently and rapidly. Repetitive GPU hangs indicate that the graphics hardware has not recovered successfully. In these situations, the end user must shut down and restart the operating system to fully reset the graphics hardware. If the operating system detects that six or more GPU hangs and subsequent recoveries occur within 1 minute, the operating system bug-checks the computer on the next GPU hang.[/quote][/size]

[b]TDR Error Messaging[/b]
[size="2"][quote]Throughout the TDR process (that is, the process of detecting and recovering from situations where a GPU stops operating), the desktop is unresponsive and thus unavailable to the end user. In the final stages of recovery, a brief screen flash occurs that is similar to the brief screen flash that occurs when the end user changes the screen resolution. After the operating system has successfully recovered the desktop, the following informational message appears to the end user.

The operating system also logs the preceding message in the Event Viewer application and collects diagnosis information in the form of a debug report. If the end user opted in to provide feedback, the operating system returns this debug report to Microsoft through the Online Crash Analysis (OCA) mechanism.[/quote][/size]

It is possible to disable the TDR service or make [url="http://msdn.microsoft.com/en-us/library/windows/hardware/ff569918(v=vs.85).aspx"]changes[/url] to the registry in order to increase the timeout period or turn off the service, however please note that this is not recommended nor supported, and in fact doing so is considered a Windows Logo Program violation.

For the original Microsoft links to the above quoted information, please see [url="http://msdn.microsoft.com/en-us/library/windows/hardware/ff570088(v=vs.85).aspx"]here[/url] and [url="http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx"]here[/url].

_________________________________________________________

Now you know what exactly the error is, you probably want to stop it happening. I would like to tell you that there is a one-stop fix that I could recommend, but unfortunately, TDR events can be caused by many different problems. First off though, if your computer has been bough 'off-the-shelf' and is brand new, then you should think about talking to where you bought it from.

[b]Common issues that can cause a TDR:[/b]
[list]
[*]Incorrect memory timings or voltages
[*]Insufficient/problematic PSU
[*]Corrupt driver install
[*]Overheating
[*]Unstable overclocks (GPU or CPU)
[*]Incorrect MB voltages (generally NB/SB)
[*]Faulty graphics card
[*]A badly written driver or piece of software, but this is an unlikely cause in most cases
[*]Driver conflicts
[*]Another possibility that people tend not to like to hear, is that you are simply asking too much of your graphics card. What I mean by this, is that if you have your settings too high and the graphics card struggles and falls to very low FPS, then something graphically complex occurs, the GPU may not be able to respond and a TDR error may occur
[*]Some users have experienced TDR errors whilst browsing the web with the 280.xx, 285.xx and 290.xx drivers. Please head to [url="http://forums.nvidia.com/index.php?showtopic=223716"]this link[/url] to clarify if this is relevant to you - this is quite a specific issue which seems to predominantly affect web browsing as opposed to gaming. Some users have found that changing the power management mode to 'Prefer Maximum Performance' has helped, with many others reporting that 295.73 has resolved the issue.
[/list]

[b]Things to check or consider initially in your troubleshooting:[/b]
[list]
[*]Check for newer driver version or cleanly uninstall/re-install your drivers. Great description of how to do this [url="http://forums.nvidia.com/index.php?showtopic=169555&hl"]here[/url] (full credit to DJNOOB for this).
[*]If you have multiple 'GPU tools' like EVGA Precision and MSI Afterburner installed, consider that it is only advisable to have one tool such as this at any one time.
[*]If the issue is only with a specific game, check for patches.
[*]If this is a new problem for you, have you just added any new hardware or updated/installed any new drivers? Consider rolling them back.
[*]Check temperatures. Its important you check these at load, which is generally when a TDR event will occur. Everest Ultimate Edition is a good tool for this, or OCCT's GPU stress test. If things are too hot, you can use tools such as EVGA Precision to increase GPU fan speeds on graphics cards. Cleaning your system of dust can help temperatures significantly. Common sense will normally tell you if something is too hot, but if you aren't sure, the information is generally available online.
[*]Check that your RAM is running at the correct settings as defined by the manufacturer.
[*]Remove any overclocks on your system and test with stock clocks. This includes memory, CPU and GPU (even factory OC'd cards). Best to try each separately so you can be sure if one solves the issue.
[*]Attempt a CMOS reset to return all BIOS settings to default. This is a good hardware troubleshooting step as it also resets the IRQ assignments - you can normally reset the CMOS either through a jumper on the motherboard (see manual), or by disconnecting the mains power and taking out the motherboard battery for 5 minutes. You will likely need to go in to the BIOS after this reset to check the memory timings/voltages are correct, as these will not always do so automatically.
[/list]

[b]Additional steps:[/b]
[list]
[*]Run memtest (memtest.org). This should complete with NO errors.
[*]If you have just installed a new graphics card, check your PSU ratings. Is it providing enough power, and most importantly enough Amps on the 12V rail.
[*]If you are using SLI, try each card separately to see if the fault lies with one.
[*]Try graphics card/cards in another computer if you can.
[/list]
_________________________________________________________

As most people who end up reading this will have slightly custom computers in one way or the other, please try to remember that checking things like RAM timings & PSU voltage go hand in hand with modifying or building a computer. A lot of people assume that any hardware they buy and plug in should just work, and any software they then install should be fine also... this is not entirely true. No hardware or software vendor can truly recreate all of the different possible combinations, so do expect some tinkering to be required every once in a while.

For those with laptops, I appreciate there are a lot of steps here you cannot complete. However, the confined space of a laptop plus dust and age can mean that overheating is a real possibility. Beyond this you need to look at reinstalling drivers and software, and then you should be looking at potential hardware issues and likely an RMA (assuming of course you have not been overclocking in software or making changes in the BIOS).

_________________________________________________________

[b]Programs to use for stress testing CPU:[/b]
- Prime95 (would advise running for at least a few hours).
- Intel Burntest (run at least a few passes)
- OCCT (good linpack test for CPU)

I can highly recommend Everest/AIDA64 as this shows you ALL your temperatures, including other GPU components. It is however not free - you can download a trial but it has some functions limited (including some temperatures).

At the end of the day, try not to become too frustrated with the issue. Generally a solution can be found. There a lot of topics you can look back on in relation to this issue, and a lot of good people around on this (and other) forums who are happy to help, assuming of course you are willing to take advice! People understand frustration, but they aren't going to help you if you are rude or abusive... an FYI for those who just want a slanging match!

If you post a topic regarding this issue, please state you system specs in as much detail as you can, plus anything you have tried so far. Feel free to PM me if you are having no luck and I will do my best to advise.

This thread has grown quite lengthy, but hopefully is still useful for people. If you are having 'driver not responding' errors then please read this post so that you understand exactly what the issue is and how varied the causes can be - plus you may find a resolution within.

Just as a 'disclaimer' here, this thread is not intended for everyone to post their problems on... The purpose of this thread is to try and help you, but also to prevent multiple topics on the same subject. Lots of people have seen these errors, so hopefully this thread should help you understand exactly what you are seeing before you post. I have seen and responded to a lot of TDR related topics now where people have not made the effort to do any prior searching.

The generic error people visit this forum for is: 'Display driver nvlddmkm stopped responding and was recovered.'

Also noted as nvlddmkm.sys, atikmdag.sys, and xxxxxxxx.sys bug-check/BSOD.

________________________________________________________

As a starting note, this is not an nVidia issue. It is not an ATI issue either. These errors are triggered by a Windows service called 'Timeout Detection and Recovery' (TDR). You will only see this error on Windows Vista and Windows 7, as TDR is a feature of the new WDDM driver model (implemented first in Windows Vista). TDR is supposed to be there to help stop BSOD's by resetting the GPU and/or driver when there is an issue or long delay. If the problem happens multiple times in a row, a BSOD can occur.

If you are having this problem frequently then you will probably find it very frustrating, however be reassured that the problem is normally perfectly solvable, although can take some troubleshooting to resolve. I personally have seen this issue on two separate nVidia builds, and an Intel onboard GPU.

How does TDR work?

Timeout Detection and Recovery

Windows Vista and later operating systems attempt to detect situations in which computers appear to be completely "frozen". They then attempt to dynamically recover from the frozen situations so that their desktops are responsive again. This process of detection and recovery is known as timeout detection and recovery (TDR). In the TDR process, the operating system's GPU scheduler calls the display miniport driver's DxgkDdiResetFromTimeout function to reinitialize the driver and reset the GPU. Therefore, end users are not required to reboot the operating system, which greatly enhances their experience. The only visible artifact from the hang detection to the recovery is a screen flicker. This screen flicker results when the operating system resets some portions of the graphics stack, which causes a screen redraw. Some legacy DirectX applications (for example, those DirectX applications that conform to DirectX versions earlier than 9.0) might render to a black screen at the end of this recovery. The end user would have to restart these applications.

The following sequence briefly describes the TDR process:

1. Timeout detection

The GPU scheduler, which is part of the DirectX graphics kernel subsystem (Dxgkrnl.sys), detects that the GPU is taking more than the permitted amount of time to execute a particular task. The GPU scheduler then tries to preempt this particular task. The preempt operation has a "wait" timeout, which is the actual TDR timeout. This step is thus the timeout detection phase of the process. The default timeout period in Windows Vista and later operating systems is 2 seconds. If the GPU cannot complete or preempt the current task within the TDR timeout period, the operating system diagnoses that the GPU is frozen.

To prevent timeout detection from occurring, hardware vendors should ensure that graphics operations (that is, DMA buffer completion) take no more than 2 seconds in end-user scenarios such as productivity and game play.

2. Preparation for recovery:

The operating system's GPU scheduler calls the display miniport driver's DxgkDdiResetFromTimeout function to inform the driver that the operating system detected a timeout. The driver must then reinitialize itself and reset the GPU. In addition, the driver must stop accessing memory and should not access hardware. The operating system and the driver collect hardware and other state information that could be useful for post-mortem diagnosis.

3. Desktop recovery:

The operating system resets the appropriate state of the graphics stack. The video memory manager, which is also part of Dxgkrnl.sys, purges all allocations from video memory. The display miniport driver resets the GPU hardware state. The graphics stack takes the final actions and restores the desktop to the responsive state. As previously mentioned, some legacy DirectX applications might render just black at the end of this recovery, which requires the end user to restart these applications. Well-written DirectX 9Ex and DirectX 10 and later applications that handle Device Remove technology continue to work correctly. An application must release and then recreate its Direct3D device and all of the device's objects. For more information about how DirectX applications recover, see the Windows SDK.

Limiting Repetitive GPU Hangs and Recoveries

Beginning with Windows Vista with Service Pack 1 (SP1) and Windows Server 2008, the user experience has been improved in situations where the GPU hangs frequently and rapidly. Repetitive GPU hangs indicate that the graphics hardware has not recovered successfully. In these situations, the end user must shut down and restart the operating system to fully reset the graphics hardware. If the operating system detects that six or more GPU hangs and subsequent recoveries occur within 1 minute, the operating system bug-checks the computer on the next GPU hang.

TDR Error Messaging

Throughout the TDR process (that is, the process of detecting and recovering from situations where a GPU stops operating), the desktop is unresponsive and thus unavailable to the end user. In the final stages of recovery, a brief screen flash occurs that is similar to the brief screen flash that occurs when the end user changes the screen resolution. After the operating system has successfully recovered the desktop, the following informational message appears to the end user.

The operating system also logs the preceding message in the Event Viewer application and collects diagnosis information in the form of a debug report. If the end user opted in to provide feedback, the operating system returns this debug report to Microsoft through the Online Crash Analysis (OCA) mechanism.

It is possible to disable the TDR service or make changes to the registry in order to increase the timeout period or turn off the service, however please note that this is not recommended nor supported, and in fact doing so is considered a Windows Logo Program violation.

For the original Microsoft links to the above quoted information, please see here and here.

_________________________________________________________

Now you know what exactly the error is, you probably want to stop it happening. I would like to tell you that there is a one-stop fix that I could recommend, but unfortunately, TDR events can be caused by many different problems. First off though, if your computer has been bough 'off-the-shelf' and is brand new, then you should think about talking to where you bought it from.

Common issues that can cause a TDR:

Incorrect memory timings or voltages

Insufficient/problematic PSU

Corrupt driver install

Overheating

Unstable overclocks (GPU or CPU)

Incorrect MB voltages (generally NB/SB)

Faulty graphics card

A badly written driver or piece of software, but this is an unlikely cause in most cases

Driver conflicts

Another possibility that people tend not to like to hear, is that you are simply asking too much of your graphics card. What I mean by this, is that if you have your settings too high and the graphics card struggles and falls to very low FPS, then something graphically complex occurs, the GPU may not be able to respond and a TDR error may occur

Some users have experienced TDR errors whilst browsing the web with the 280.xx, 285.xx and 290.xx drivers. Please head to this link to clarify if this is relevant to you - this is quite a specific issue which seems to predominantly affect web browsing as opposed to gaming. Some users have found that changing the power management mode to 'Prefer Maximum Performance' has helped, with many others reporting that 295.73 has resolved the issue.

Check for newer driver version or cleanly uninstall/re-install your drivers. Great description of how to do this here (full credit to DJNOOB for this).

If you have multiple 'GPU tools' like EVGA Precision and MSI Afterburner installed, consider that it is only advisable to have one tool such as this at any one time.

If the issue is only with a specific game, check for patches.

If this is a new problem for you, have you just added any new hardware or updated/installed any new drivers? Consider rolling them back.

Check temperatures. Its important you check these at load, which is generally when a TDR event will occur. Everest Ultimate Edition is a good tool for this, or OCCT's GPU stress test. If things are too hot, you can use tools such as EVGA Precision to increase GPU fan speeds on graphics cards. Cleaning your system of dust can help temperatures significantly. Common sense will normally tell you if something is too hot, but if you aren't sure, the information is generally available online.

Check that your RAM is running at the correct settings as defined by the manufacturer.

Remove any overclocks on your system and test with stock clocks. This includes memory, CPU and GPU (even factory OC'd cards). Best to try each separately so you can be sure if one solves the issue.

Attempt a CMOS reset to return all BIOS settings to default. This is a good hardware troubleshooting step as it also resets the IRQ assignments - you can normally reset the CMOS either through a jumper on the motherboard (see manual), or by disconnecting the mains power and taking out the motherboard battery for 5 minutes. You will likely need to go in to the BIOS after this reset to check the memory timings/voltages are correct, as these will not always do so automatically.

Additional steps:

Run memtest (memtest.org). This should complete with NO errors.

If you have just installed a new graphics card, check your PSU ratings. Is it providing enough power, and most importantly enough Amps on the 12V rail.

If you are using SLI, try each card separately to see if the fault lies with one.

Try graphics card/cards in another computer if you can.

_________________________________________________________

As most people who end up reading this will have slightly custom computers in one way or the other, please try to remember that checking things like RAM timings & PSU voltage go hand in hand with modifying or building a computer. A lot of people assume that any hardware they buy and plug in should just work, and any software they then install should be fine also... this is not entirely true. No hardware or software vendor can truly recreate all of the different possible combinations, so do expect some tinkering to be required every once in a while.

For those with laptops, I appreciate there are a lot of steps here you cannot complete. However, the confined space of a laptop plus dust and age can mean that overheating is a real possibility. Beyond this you need to look at reinstalling drivers and software, and then you should be looking at potential hardware issues and likely an RMA (assuming of course you have not been overclocking in software or making changes in the BIOS).

_________________________________________________________

Programs to use for stress testing CPU:

- Prime95 (would advise running for at least a few hours).

- Intel Burntest (run at least a few passes)

- OCCT (good linpack test for CPU)

Programs to use for stress testing GPU:

- OCCT

- 3DMark Vantage

- 3DMark 11 (DX11 GPUs only)

- Any of the Crysis series

Programs to use for monitoring temperatures:

- EVGA Precision (GPU only)

- MSI Afterburner (GPU only)

- Everest Ultimate Edition (now known as AIDA 64)

- CoreTemp (CPU only)

- RealTemp (CPU only)

- OCCT (stress testing and temp monitoring)

I can highly recommend Everest/AIDA64 as this shows you ALL your temperatures, including other GPU components. It is however not free - you can download a trial but it has some functions limited (including some temperatures).

At the end of the day, try not to become too frustrated with the issue. Generally a solution can be found. There a lot of topics you can look back on in relation to this issue, and a lot of good people around on this (and other) forums who are happy to help, assuming of course you are willing to take advice! People understand frustration, but they aren't going to help you if you are rude or abusive... an FYI for those who just want a slanging match!

If you post a topic regarding this issue, please state you system specs in as much detail as you can, plus anything you have tried so far. Feel free to PM me if you are having no luck and I will do my best to advise.

I genuinely appreciate your post because there are thousands of us with this problem, myself included. What makes it even more frustrating is that some of us do post exact specifics and exact troubleshoot options that we have tried and still no help from anyone. I am speaking personally. I have listed my specs, the error message, and every single bit of knowledge that I have found for my problem and trouble shoot options that have failed.

So, I am replying to your message, hoping someone will look at what I have posted numerous time and hopefully a response.

I genuinely appreciate your post because there are thousands of us with this problem, myself included. What makes it even more frustrating is that some of us do post exact specifics and exact troubleshoot options that we have tried and still no help from anyone. I am speaking personally. I have listed my specs, the error message, and every single bit of knowledge that I have found for my problem and trouble shoot options that have failed.

So, I am replying to your message, hoping someone will look at what I have posted numerous time and hopefully a response.

DaNegotiator, if you are encountering TDRs, you should make a thread in an appropriate forum. jimbonbon posted this thread to provide more information regarding TDRs and specifically asked that users seeking troubleshooting assistance not post their issues in this thread. Though you have done so quite respectfully, you hijacked his thread and did exactly what his asked not be done. If you with to pursue an specific user's assistance the appropriate method is to send them a PM with a link to your thread. I would suggest against posting your issue in a PM to a single member; create a thread and PM the link.

jimbonbon, thanks for the excellent contribution of information. I will add this post to the sticky with NVIDIA's statement about TDRs stickied at the top of this forum.

DaNegotiator, if you are encountering TDRs, you should make a thread in an appropriate forum. jimbonbon posted this thread to provide more information regarding TDRs and specifically asked that users seeking troubleshooting assistance not post their issues in this thread. Though you have done so quite respectfully, you hijacked his thread and did exactly what his asked not be done. If you with to pursue an specific user's assistance the appropriate method is to send them a PM with a link to your thread. I would suggest against posting your issue in a PM to a single member; create a thread and PM the link.

jimbonbon, thanks for the excellent contribution of information. I will add this post to the sticky with NVIDIA's statement about TDRs stickied at the top of this forum.

Amorphous

Attachments

This is not a regularly monitored account. Please contact Kris@NVIDIA for assistance.

NVIDIA Focus Group Members receive free software and/or hardware from NVIDIA from time to time to facilitate the evaluation of NVIDIA products. However, the opinions expressed are solely those of the members.

[quote name='Amorphous' post='560560' date='Jul 2 2009, 07:14 AM']DaNegotiator, if you are encountering TDRs, you should make a thread in an appropriate forum. jimbonbon posted this thread to provide more information regarding TDRs and specifically asked that users seeking troubleshooting assistance not post their issues in this thread. Though you have done so quite respectfully, you hijacked his thread and did exactly what his asked not be done. If you with to pursue an specific user's assistance the appropriate method is to send them a PM with a link to your thread. I would suggest against posting your issue in a PM to a single member; create a thread and PM the link.

jimbonbon, thanks for the excellent contribution of information. I will add this post to the sticky with NVIDIA's statement about TDRs stickied at the top of this forum.

Amorphous[/quote]

Again, apologies amorphous. As I said before, no one would respond to my numerous posts. This is the first time in a long time I got feedback or a message so quickly. I editted the post and removed most of the information. Because you would like to sticky this thread, feel free to completely remove my thread as it would only allow me to edit it. I will make another post, hoping for some legit responses.

[quote name='Amorphous' post='560560' date='Jul 2 2009, 07:14 AM']DaNegotiator, if you are encountering TDRs, you should make a thread in an appropriate forum. jimbonbon posted this thread to provide more information regarding TDRs and specifically asked that users seeking troubleshooting assistance not post their issues in this thread. Though you have done so quite respectfully, you hijacked his thread and did exactly what his asked not be done. If you with to pursue an specific user's assistance the appropriate method is to send them a PM with a link to your thread. I would suggest against posting your issue in a PM to a single member; create a thread and PM the link.

jimbonbon, thanks for the excellent contribution of information. I will add this post to the sticky with NVIDIA's statement about TDRs stickied at the top of this forum.

Amorphous

Again, apologies amorphous. As I said before, no one would respond to my numerous posts. This is the first time in a long time I got feedback or a message so quickly. I editted the post and removed most of the information. Because you would like to sticky this thread, feel free to completely remove my thread as it would only allow me to edit it. I will make another post, hoping for some legit responses.

I genuinely appreciate your post because there are thousands of us with this problem, myself included. What makes it even more frustrating is that some of us do post exact specifics and exact troubleshoot options that we have tried and still no help from anyone. I am speaking personally. I have listed my specs, the error message, and every single bit of knowledge that I have found for my problem and trouble shoot options that have failed.

So, I am replying to your message, hoping someone will look at what I have posted numerous time and hopefully a response.[/quote]

Hi DaNegotiator... No problem at all, glad its useful! I'll keep an eye for your post and try to lend some help if I can. How often i'm on here rather varies depending on my work load!

[quote name='Amorphous' post='560560' date='Jul 2 2009, 07:14 AM']DaNegotiator, if you are encountering TDRs, you should make a thread in an appropriate forum. jimbonbon posted this thread to provide more information regarding TDRs and specifically asked that users seeking troubleshooting assistance not post their issues in this thread. Though you have done so quite respectfully, you hijacked his thread and did exactly what his asked not be done. If you with to pursue an specific user's assistance the appropriate method is to send them a PM with a link to your thread. I would suggest against posting your issue in a PM to a single member; create a thread and PM the link.

jimbonbon, thanks for the excellent contribution of information. I will add this post to the sticky with NVIDIA's statement about TDRs stickied at the top of this forum.

Amorphous[/quote]

Thanks Amorphous, and of course no problem at all! :) Thanks for the sticky-ness.

I genuinely appreciate your post because there are thousands of us with this problem, myself included. What makes it even more frustrating is that some of us do post exact specifics and exact troubleshoot options that we have tried and still no help from anyone. I am speaking personally. I have listed my specs, the error message, and every single bit of knowledge that I have found for my problem and trouble shoot options that have failed.

So, I am replying to your message, hoping someone will look at what I have posted numerous time and hopefully a response.

Hi DaNegotiator... No problem at all, glad its useful! I'll keep an eye for your post and try to lend some help if I can. How often i'm on here rather varies depending on my work load!

[quote name='Amorphous' post='560560' date='Jul 2 2009, 07:14 AM']DaNegotiator, if you are encountering TDRs, you should make a thread in an appropriate forum. jimbonbon posted this thread to provide more information regarding TDRs and specifically asked that users seeking troubleshooting assistance not post their issues in this thread. Though you have done so quite respectfully, you hijacked his thread and did exactly what his asked not be done. If you with to pursue an specific user's assistance the appropriate method is to send them a PM with a link to your thread. I would suggest against posting your issue in a PM to a single member; create a thread and PM the link.

jimbonbon, thanks for the excellent contribution of information. I will add this post to the sticky with NVIDIA's statement about TDRs stickied at the top of this forum.

Amorphous

Thanks Amorphous, and of course no problem at all! :) Thanks for the sticky-ness.

Ive tried everything....IS my 8400GS dead?, ive tested it with some hp hardware detection software said its fine....Its fine at the moment on the windows aero...but playing a game...5 min into a game it will go purple and green and then freeze??? and its not the drivers becasue the 190.XX have been working very well for me untill like 2 weeks ago??..ive tried all different tuypes of drivers....even 169.XX still doesnt fix the game freezing problems....my ram is good (2.0GB)....sounds like a half deads GPU?

Ive tried everything....IS my 8400GS dead?, ive tested it with some hp hardware detection software said its fine....Its fine at the moment on the windows aero...but playing a game...5 min into a game it will go purple and green and then freeze??? and its not the drivers becasue the 190.XX have been working very well for me untill like 2 weeks ago??..ive tried all different tuypes of drivers....even 169.XX still doesnt fix the game freezing problems....my ram is good (2.0GB)....sounds like a half deads GPU?

temp is around 59oC on start up then goes to around 70oC on idle and then around 98 while playing a game....looking at the nividia website these a normal temps, nvidia said the max is 105oC, its futuremark free?

temp is around 59oC on start up then goes to around 70oC on idle and then around 98 while playing a game....looking at the nividia website these a normal temps, nvidia said the max is 105oC, its futuremark free?

Ohk i downloaded and ran FurMark...tried the benching marking test and stablity test but they were unable to complete, as about 5 seconds into it the screen goes black and nothing happens, i have to al ctrl delete to get task manager and end program...same with cod waw and cod 4....seems that anything graphically intensive will make my GPU driver to crash....Sound like a dying GPU?

Ohk i downloaded and ran FurMark...tried the benching marking test and stablity test but they were unable to complete, as about 5 seconds into it the screen goes black and nothing happens, i have to al ctrl delete to get task manager and end program...same with cod waw and cod 4....seems that anything graphically intensive will make my GPU driver to crash....Sound like a dying GPU?

Eh... I've been getting this nvlddmkm.sys problem for about a month or 2 now.. kind of.

It randomly happened somewhat late at night while at my computer. My computer got the BSOD and shutdown. I restarted... right before log in screen, got the nvlddmkm.sys BSOD again. I continuously got it and could not reach the login screen. I then went on another computer, looked it up, renamed nvlddmkm.sys to nvlddmkm.sys.old and it would boot up.. except that I do not think my driver's would be working properly because for example, I would not be able to get the same desktop resolutions... Anyway, I tried my onboard gpu by taking out 7900gs (which had been working for 1-2 years without problems) and it worked for about a month, until today. Today, it randomly got the same error for even my onboard gpu. What is the problem? I have tried that expanding nvlddmkm.sy_ etc etc... im soo confused. I'm also willing to have like remoet access help from someone lol

Then, I took out my 7900gs (which had been working for 1-2 years without problems) and

Eh... I've been getting this nvlddmkm.sys problem for about a month or 2 now.. kind of.

It randomly happened somewhat late at night while at my computer. My computer got the BSOD and shutdown. I restarted... right before log in screen, got the nvlddmkm.sys BSOD again. I continuously got it and could not reach the login screen. I then went on another computer, looked it up, renamed nvlddmkm.sys to nvlddmkm.sys.old and it would boot up.. except that I do not think my driver's would be working properly because for example, I would not be able to get the same desktop resolutions... Anyway, I tried my onboard gpu by taking out 7900gs (which had been working for 1-2 years without problems) and it worked for about a month, until today. Today, it randomly got the same error for even my onboard gpu. What is the problem? I have tried that expanding nvlddmkm.sy_ etc etc... im soo confused. I'm also willing to have like remoet access help from someone lol

Then, I took out my 7900gs (which had been working for 1-2 years without problems) and

temp is around 59oC on start up then goes to around 70oC on idle and then around 98 while playing a game....looking at the nividia website these a normal temps, nvidia said the max is 105oC, its futuremark free?[/quote]

temp is around 59oC on start up then goes to around 70oC on idle and then around 98 while playing a game....looking at the nividia website these a normal temps, nvidia said the max is 105oC, its futuremark free?