Overclock.net banner
Cancel

nvlddmkm problem, please help if possible

828 Views 6 Replies 5 Participants Last post by  Bahlzeron, 
1
I have read some background on this issue that i am having. However, my only difference is that i do not get any BSODs like most people do. I don't know if it is something with any of my hardware, which i highly doubt because i don't get any BSODs. I didn't get this problem when i was using the 190.62 nvidia drivers, yet when i upgraded to the 195.62 i get this problem constantly.

Driver Error: Display driver nvlddmkm stopped responding and has successfully recovered.

System Specs:
Windows 7 64bit Ultimate
E8400 @ 4.0 Ghz
EVGA GTX 285 OCed to the SSC speeds

They are all stable and tested completely. I don't know if this problem is a known driver problem or what but it really gets on my nerves in which the clocks get locked up on the 2D clocks of the card and i have to restart my pc.

Please help, if anyone know a possible fix gladly appreciate it.
Reply
Save
Like
1 - 7 of 7 Posts
TwoCables
Quote:


Originally Posted by 1 sK~
View Post

I have read some background on this issue that i am having. However, my only difference is that i do not get any BSODs like most people do. I don't know if it is something with any of my hardware, which i highly doubt because i don't get any BSODs. I didn't get this problem when i was using the 190.62 nvidia drivers, yet when i upgraded to the 195.62 i get this problem constantly.

Driver Error: Display driver nvlddmkm stopped responding and has successfully recovered.

System Specs:
Windows 7 64bit Ultimate
E8400 @ 4.0 Ghz GTX 285 OCed to the SSC speeds

They are all stable and tested completely. I don't know if this problem is a known driver problem or what but it really gets on my nerves in which the clocks get locked up on the 2D clocks of the card and i have to restart my pc.

Please help, if anyone know a possible fix gladly appreciate it.

I recommend going back to 190.62 using Driver Sweeper. I know how this sounds, but sometimes we have to find the driver that works best with our particular system.

Here's how to correctly use Driver Sweeper once it is installed:
  1. Use the Programs and Features control panel to uninstall the NVIDIA display driver (I can't help it: that's just what it's called).
  2. Reboot into Safe Mode (hold F8 during the transition from the POST to the loading of Windows).
  3. Once in Safe Mode, open Driver Sweeper and choose "NVIDIA - Display".
  4. Click "Clean".
  5. Finish up and reboot normally.
  6. Install driver 190.62.
This should get you back to 190.62 which was working properly. This way you can wait until the next driver version after 195.62 to see if that one works any better. Oh, and don't worry: you're not alone.
See less See more
Reply
Save
Like
Aiden327
I get the same error occasionally. I am running 186. I am interested to what is causing this, my monitor loses signal but I hear my games still going. Then it says that dll stopped working an has recovered and monitor comes back on.

Using my sig rig, stock clocks.

Thanks,

Aiden
Reply
Save
Like
TwoCables
Quote:


Originally Posted by Aiden327
View Post

I get the same error occasionally. I am running 186. I am interested to what is causing this, my monitor loses signal but I hear my games still going. Then it says that dll stopped working an has recovered and monitor comes back on.

Using my sig rig, stock clocks.

Thanks,

Aiden

Like I said, I was having the same problem. But I fixed it by finding a driver that works better on my system. It happens to be 190.38, but for all we know, it could be 190.62 for you, or 191.07, or 195.62 - or even a Beta release. Either way, when there are driver problems like this, just switch to a different driver and see how it goes. And always, always use Driver Sweeper as I described above.
See less See more
Reply
Save
Like
1
Okay, somehow i found my solution. It looks like the new nvidia drivers don't allow me to overclock my GPU. Why, i don't know, maybe it is just an issue with the drivers. I had to reflash my card to default clocks and i haven't been getting this error no more. Hopefully this helps out. I was thinking going back to the 190.62 drivers that worked fine with the OC on the card, but i am going to mess around with these drivers see if i can find any other solutions.
Reply
Save
Like
Y
i had a similar problem with 195.62 beta drivers.Whenever I tried to overclock the GPU, my screen would start artifacting. when i reverted back to 186 drivers, the problem went away
Reply
Save
Like
B
Don't mean to resurrect a (sorta) dead thread.. but what worked for me (so far) was while in safe mode before I ran Driver Sweeper, I deleted the NVIDIA folder in C/:. I had two different driver versions in it. Until I did this I had NO luck with ANY drivers.

Hope this helps some peeps. And as far as I can tell it's a Vista/7 bug (32 & 64), pretty much zero problems like this in XP.
Reply
Save
Like
1 - 7 of 7 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Overclock.net
A forum community dedicated to overclocking enthusiasts and testing the limits of computing. Come join the discussion about computing, builds, collections, displays, models, styles, scales, specifications, reviews, accessories, classifieds, and more!
Full Forum Listing
Explore Our Forums
Hardware News Intel CPUs PC Gaming NVIDIA Water Cooling
Top