"Display driver has Stopped responding and has recovered/restarted"

D

dot_Zen

Gawd
Joined
Feb 17, 2007
Messages
720
Many of you have had them, some of you hate them, others of you don't have a clue what this is..

Nvidia acknowledges the "issue" in their forums but only via a moderator and no ongoing communication with the users having the issue.

I come here today to tell you that Microsoft does have a document describing the reason, symptoms,and issues. As well as how hardware, software, and system manufactures can deal with the TDR issue..


Introduction

One of the most common stability problems in graphics is when the system appears completely "frozen" or "hung" while processing an end-user command or operation. Users generally wait a few seconds and then reboot the system by pressing the Power button. Usually the graphics processing unit (GPU) is "busy" processing intensive graphical operations, typically during gameplay. This results in nothing being updated on the screen, thus appearing to the user that the system is frozen.
This paper briefly describes the timeout detection and recovery (TDR) process in Windows Vista. It also documents the registry controls so developers can easily debug problems.
Click to expand...
Timeout Detection and Recovery

Windows Vista attempts to detect these problematic hang situations and recover a responsive desktop dynamically. In this process, the Microsoft Windows Display Driver Model (WDDM) driver is reinitialized and the GPU is reset. No reboot is necessary, which greatly enhances the user experience. The only visible artifact from the hang detection to the recovery is a screen flicker, which results from resetting some portions of the graphics stack, causing a screen redraw. Some older Microsoft DirectX applications may render to a black screen at the end of this recovery. The end user would have to restart these applications.[Snip]
Click to expand...
Next Steps

Graphics hardware vendors:
•Ensure that graphics operations (that is, DMA buffer completion) take no more than 2 seconds in end-user scenarios such as productivity and gameplay.
Graphics software vendors:
•Ensure that the DirectX graphics application does not run at a low frames per second (FPS) rate. As the FPS decreases, the likelihood of the GPU getting reset increases. If the application is running at 10 FPS or lower and a complex graphics operation is about to start, then a flush can be inserted.
•For running benchmark tests on low-end GPUs, use the aforementioned registry keys that control the TDR timeout. Remember that they should not be used in production systems because it would affect overall system stability and robustness. Use these keys only as a final solution.
System manufacturers:
•Work with the graphics hardware vendor to diagnose the TDR debug reports.
•Remember that any system that uses the aforementioned TDR registry keys to change the default values is a Windows Logo Program violation.
Click to expand...
For more information see:
http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx

Discuss.....
 
I got that error once, right after installing the newest Nvidia drivers. That was weeks ago, hasnt happened since.
 
I've seen it twice, most recently it was a result in overclocking, I believe. Now that I can overclock, I pushed my core a little higher than it ran in XP. I was gaming and it froze as if due to the core clock. But instead of having to restart, it simply restarted the driver or whatver. Pretty slick.
 
oh the infinite loop error...

the unsolved riddle that eludes them all :D


some day I hope they do solve this problem and fix it
 
m3th0dm4n said:
Happened all the time in Vista for me. Totally unacceptable.
Click to expand...


Um, do you understand what you're reading or what this implies?

Basically, to break it down for you, this should mitigate how many BSOD's can occur from faulty hardware or firmware(drivers).

It's a good thing, rather it's headed into a good direction.

Maybe I posted this in the wrong section....
 
You must log in or register to reply here.
Back
Top