| Thread Tools |
9th May 2010, 10:15 | #1 |
Posts: n/a
| Display driver nvlddmkm stopped responding and has successfully recovered Okay, I'm at my wits end here so I'm going to reach out for any chance of sage knowledge about this issue, specifically related to overclocking a Core i7 CPU. I've only had this issue with Core i7's. Is there some method to fix this or BIOS setting that might? So far I get this Event log message from both games and F@H, although more often from Folding@home. I've tested with two CPUs, two motherboards, two brands of RAM, three NVIDIA GPUs, multiple drives/OS installs, and two power supplies. I still get driver reset messages with all of them, and the only common factor seems to be my overclocks. You guys have experience taking hardware to the limits and running 3D benchmarking programs, so I'm guessing this problem has been run into before and worked around, somehow? |
9th May 2010, 10:22 | #2 |
[M] Reviewer Join Date: May 2010 Location: Romania
Posts: 148,578
| I had this problem in two situations till now : crappy drivers and needed a reinstall or video card VRM problems (the video card did not display any artifacts, but the screen was going blank for a bit and when it was coming back I was getting that error; sometimes I was getting the error without the blank screen). After replacing the video card with an identical one, the problem was gone. What video card/cards are we talking about? If we are talking about the new GTXes, there are problems with BIOSes from multiple manufacturers with these cards, and some promised to release BIOS fixes. Last edited by Stefan Mileschin : 9th May 2010 at 10:29. |
9th May 2010, 11:01 | #3 |
Posts: n/a
| Hey Stefan! Thanks for the reply. EVGA GTX 260 (original + fully watercooled) EVGA GTX 260 Core 216 EVGA GTX 285 The screen flips black when it resets. Causes a 2-5 second game freeze if a game is playing, or it corrupts the F@H work unit that was folding. I've had this problem ever since I built the system, but always thought it was for some different reason or another because it is intermittent. A few times it gets so bad I can't play a game, others it doesn't show up for days. I would have tried an ATI card, but until Stanford fully switches to a universal GPGPU codebase ATI's folding performance is still underwhelming at best. And at this point I don't think it would fix it anyway... |
9th May 2010, 11:38 | #4 |
[M] Reviewer Join Date: May 2010 Location: Romania
Posts: 148,578
| Dear Kougar, No problem, just trying to help. I know the folding applications stress a lot the video card and in many cases you can hear the so called "coil noise". Have you also tried older video drivers to see if you have the same problem? Also, what OS do you use? Windows 7, Vista? If using windows 7, I would also try Vista to see if the problem manifests again. On the non-watercooled cards, also try to run the fan at a higher speed, not AUTO, to see if its not an overheating problem. Last edited by Stefan Mileschin : 9th May 2010 at 11:43. |
9th May 2010, 12:59 | #5 | ||
Posts: n/a
| Quote:
Quote:
I tried maxing out the fan speed on the 285, but GPU temps are not the issue. Even with the fans on auto Furmark 1.8.0 doesn't overheat these cards or force the driver crash. | ||
9th May 2010, 18:17 | #6 |
[M] Reviewer Join Date: May 2010 Location: Romania
Posts: 148,578
| Have you also tried to install other older drivers? (by using also a driver cleaner prior to installation) |
10th May 2010, 04:19 | #7 |
Posts: n/a
| I've had this problem since the 180 drivers onwards. Yes I've tried driver cleaner and driver sweeper. |
10th May 2010, 06:26 | #8 |
[M] Reviewer Join Date: May 2010 Location: Romania
Posts: 148,578
| If you deactivate PhysX in the drivers, will the problem persist? |
10th May 2010, 13:09 | #9 |
Posts: n/a
| I deactivated PhysX. So far so good... if the problem doesn't reoccur within a week I can be sure your suggestion resolved it. I'll cross my fingers on this one. |
10th May 2010, 13:25 | #10 |
[M] Reviewer Join Date: May 2010 Location: Romania
Posts: 148,578
| I really hope the problem gets solved. Damn Nvidias' crappy driver programmers. Please update me in this thread. |
Thread Tools | |
| |