A few minutes ago, my screen cut off then flickered a couple of times before it came back on. After which I got a pop up message stating that the Nvidia driver had stopped responding but has now recovered. Anyone else had this happen? Any reason for concern? I'm using the latest driver for 64 bit W7.
Never seen that and I have almost identical hardware to you. I wouldn't worry about it. Just a glitch in the Matrix.
FWIW, I've run Windows 7 on the rig in my sig for a couple months so I think the drivers are fine. If you hadn't gotten the popup message then I'd wonder if your monitor is starting to die.
Transco901 wrote:
Never seen that and I have almost identical hardware to you. I wouldn't worry about it. Just a glitch in the Matrix.
FWIW, I've run Windows 7 on the rig in my sig for a couple months so I think the drivers are fine. If you hadn't gotten the popup message then I'd wonder if your monitor is starting to die.
It's a fairly new monitor, so yeah. That'd suck. I'm damn glad it recovered too. I just hope this won't be a recurring issue. If it hadn't recovered, how the heck would I have fixed it? That is, of course, assuming I knew what it was.
PS2Fish wrote:
Samuel71 wrote:I get it a lot when I'm overclocking my video card... it means that the hardware has become unstable. When I get those, it's time to back off the clocks.
I don't OC my GPU. Just my processor.
Yes, I've been getting these. It's not a monitor failure, it's a driver failure. I'm running the latest beta ForceWare which happens to be much more stable than the previous WHQL one but I'm still getting problems. I discovered that restarting will temporarily fix the problem for a while. I don't know if it's just the drivers, the hardware or a combination of both as I'm having chunks of my PC malfunction. I've had them before I OC'd my video card and now that my second 8800 GTX has died and I suppose my last one is dying I decided to milk out as much as I can from it by OC'ing it. So I don't think it's because of an aggressive overclock. You'd blue screen/freeze before that.
^ It doesn't for me. Just went back into BIOS and reloaded my OC profile. One thing I noticed that the FSB ratio was set to Auto. When I reloaded it, it was at 8.5. Not sure what that was about or if it even matters, but the OS still doesn't reflect the OC. My CPU config in BIOS has the OC speed though.
PS2Fish wrote:^ It doesn't for me. Just went back into BIOS and reloaded my OC profile. One thing I noticed that the FSB ratio was set to Auto. When I reloaded it, it was at 8.5. Not sure what that was about or if it even matters, but the OS still doesn't reflect the OC. My CPU config in BIOS has the OC speed though.
I'm also having a similar problem where I'm stuck at a particular overclock. I can't go over 2.8 GHz, even if I set it in the BIOS it'll just go back to 2.8 GHz. I used to be able to run it at 3.5 GHz +. ='(
I'm running an Intel Core 2 Duo E6600.
PS2Fish wrote:
powwow71 wrote:Fish, do a fresh install of the latest nvidia win 7 191.xx nvidia drivers or you are going to be experiencing these kinds of errors a lot
Will do. Can I just install it over the existing or do I need to uninstall first?
Yep. NVIDIA also made it so that you don't have to restart whenever you install over existing ones.
Transco901 wrote:^ what are you saying? Since you installed win7 your OC is not the same? I installed win7 and my E6600 is still showing at it's OC'ed speed of 3GHz in Win7.
Soy confundido
No, I was overclocked at 3.5 when I was using Windows 7. For the purpose of stability I lowered it down to 2.8 and now that my computer is about dead I thought to just boost it all the way up and milk as much as I can out of it... but it won't apply. I'm stuck at 2.8. Meh, it doesn't matter. My computer is such a mess right now it's not even funny.
powwow71 wrote:
Synchronous Failure wrote:
PS2Fish wrote:
powwow71 wrote:Fish, do a fresh install of the latest nvidia win 7 191.xx nvidia drivers or you are going to be experiencing these kinds of errors a lot
Will do. Can I just install it over the existing or do I need to uninstall first?
Yep. NVIDIA also made it so that you don't have to restart whenever you install over existing ones.
I'm old school with driver installs. i normally uninstall the previous one first, then install the new one
That's probably the best thing to do but I'm too lazy to even hit the restart button after installing drivers.
Synchronous Failure wrote:
...I don't think it's because of an aggressive overclock. You'd blue screen/freeze before that.
Every time I've ever gotten the "Nvidia driver stopped responding" error, it was while stress-testing a video card overclock. The screen turns off (for a few seconds), and when it turns back on, the message is there and my video card's clocks have been throttled (as shown by the drastically lowered framerate of whatever stress test I'm running at the time). Of course, Fish's case may be different, but I'm certain the message has nothing to do with driver problems in my case.
Playing: World of Goo (PC)
Score: 8.8/10
Samuel71 wrote:
Synchronous Failure wrote:
...I don't think it's because of an aggressive overclock. You'd blue screen/freeze before that.Every time I've ever gotten the "Nvidia driver stopped responding" error, it was while stress-testing a video card overclock. The screen turns off (for a few seconds), and when it turns back on, the message is there and my video card's clocks have been throttled (as shown by the drastically lowered framerate of whatever stress test I'm running at the time). Of course, Fish's case may be different, but I'm certain the message has nothing to do with driver problems in my case.
Not for yours but I am almost certain it does with Fish and I. Or perhaps it is the hardware or both. My overclocks always produce a system failure before the drivers say or do anything. But I'm always the odd one out.
Found this at EVGA's site.
NVIDIA statement on TDR Error Messages
Some Windows Vista users have reported that their systems are displaying an error message that says: "Display driver stopped responding, but has successfully recovered." This is called a Timeout Detection and Recovery error message.
Timeout Detection and Recovery (TDR) is a new feature of Windows Vista that attempts to detect problematic situations and recover to a functional desktop without forcing a reboot. Hangs can occur when the GPU is processing intensive graphics operations, typically during gameplay, and nothing is being updated on the monitor. To the user it appears that the system is frozen with no resolution to the problem; in previous operating systems users generally had to wait a few seconds and then reboot.
The TDR error message "Display driver stopped responding and has recovered" lets the user know that the NVIDIA display driver (specifically the "nvlddmkm.sys" file) has been re-initialized and the GPU is reset without requiring a reboot. The only visible artifact from the recovery is a screen flicker, the result of a screen redraw. Note that some older Microsoft DirectX applications may render to a black screen at the end of the TDR, requiring the user to restart these applications.
TDRs are not specific to a single driver problem, and can occur for a variety of reasons. When they occur, diagnostic information is collected in the form of a debug report that is sent to Microsoft through the Online Crash Analysis (OCA) mechanism if the user opts to provide feedback.
NVIDIA encourages users to submit their own bug reports via the NVIDIA Vista Quality Assurance Program, using the keyword "TDR" in the description of the problem. The NVIDIA bug report link is here:
https://surveys.nvidia.com/index.jsp?pi=749...8f09
We understand that many users have expressed frustration with this issue, and we apologize for the inconvenience. Since the NVIDIA v101.41 beta driver release, NVIDIA has been fixing many TDR issues reported by users. Our software team is currently preparing a new driver which will dramatically reduce the number of TDR errors that users have reported on the forums. Thank you for your patience.
powwow71 wrote:
PS2Fish wrote:Found this at EVGA's site.
NVIDIA statement on TDR Error Messages
Some Windows Vista users have reported that their systems are displaying an error message that says: "Display driver stopped responding, but has successfully recovered." This is called a Timeout Detection and Recovery error message.
Timeout Detection and Recovery (TDR) is a new feature of Windows Vista that attempts to detect problematic situations and recover to a functional desktop without forcing a reboot. Hangs can occur when the GPU is processing intensive graphics operations, typically during gameplay, and nothing is being updated on the monitor. To the user it appears that the system is frozen with no resolution to the problem; in previous operating systems users generally had to wait a few seconds and then reboot.
The TDR error message "Display driver stopped responding and has recovered" lets the user know that the NVIDIA display driver (specifically the "nvlddmkm.sys" file) has been re-initialized and the GPU is reset without requiring a reboot. The only visible artifact from the recovery is a screen flicker, the result of a screen redraw. Note that some older Microsoft DirectX applications may render to a black screen at the end of the TDR, requiring the user to restart these applications.
TDRs are not specific to a single driver problem, and can occur for a variety of reasons. When they occur, diagnostic information is collected in the form of a debug report that is sent to Microsoft through the Online Crash Analysis (OCA) mechanism if the user opts to provide feedback.
NVIDIA encourages users to submit their own bug reports via the NVIDIA Vista Quality Assurance Program, using the keyword "TDR" in the description of the problem. The NVIDIA bug report link is here:
https://surveys.nvidia.com/index.jsp?pi=749...8f09e040b4a437a
We understand that many users have expressed frustration with this issue, and we apologize for the inconvenience. Since the NVIDIA v101.41 beta driver release, NVIDIA has been fixing many TDR issues reported by users. Our software team is currently preparing a new driver which will dramatically reduce the number of TDR errors that users have reported on the forums. Thank you for your patience.in other words, you will get this message. And if it happens, tough shit. Reboot your computer lol
Lmao
If only all error messages were like that...
