• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Display driver stopped responding

A few peeps claimed they had it on their cards till they got it RMA'd and replacement never got same issue.
Click to expand...

happened to me with my 7600GT got it evry so often somtimes 3 times in 1 day then green lines etc got new card (didnt reinstall drivers as same model clock speeds etc) hant had it for 5 weeks? lol
 
joedeath332 said:
I got this error when i tried Vista,, needless to say several drivers later , i uninstalled Vista and went back to XP :D :D
Click to expand...

I have had same sort of error with a factory overclocked 7800gt card ,underclocking by 10mhz fixed the problem in both XP and Vista in my case,only difference is Vista gives you more info on the crash/error.

Its not really Vista specific,FYI I actually found the cause and fix when I was using XP,by the time I moved over to Vista I just did the same thing ie underclocked 10 mhz and problem fixed (100% stability in all games).

Bottomline its either faulty card or overclocked card causing the problem ,so not really OS problem.Symptoms are random crashes or freezes with some games(in both XP and Vista in my case unless I reduce my factory overclocked speed like above).
They don't make video cards like they use too.
 
Last edited:
Pure luck or co , as peeps over on Nvidia forums on multiple threads have tried all sorts inc underclocking and I aint seen it in XP TBH but only used this card about 2 months in XP.
 
helmutcheese said:
Pure luck or co , as peeps over on Nvidia forums on multiple threads have tried all sorts inc underclocking and I aint seen it in XP TBH but only used this card about 2 months in XP.
Click to expand...

Took me almost a year to find the problem when I was using XP,tried different drivers etc..some games would work fine others would not,then I had a bright spark to underclock my factory OC video card by 10mhz and problem solved.(you could argue its a faulty card since obviously can't run stable at factory overclocked speed).

When I moved over to Vista I knew what to do since I was still using the same video card, which will be getting replaced soon.
 
Last edited:
In my experience, it's always been one of two things.

1. Duff/excessively overclocked system RAM

2. Duff/excessively overclocked video card RAM (possibly core, but less likely).

And if things were running on the limit in XP, chances are Vista will, by default, take it over that limit and cause instabilities.

Even demanding apps such as Prime/Crysis can be perfectly stable in XP, yet buckle in Vista.
 
Last edited:
This error is why I sold my 8800GT, even though it's a great card.

AA not applying properly, texture corruption, and this stupid error.

Things aren't perfect on the ATi side but at least it semi-works.
 
:rolleyes:This is a common issue with the big green's drivers! Its basically because there driver team is too lazy to talk to
MS and write the code to remove old driver files when you 'uninstall' them,(they are protected by windows wilst in session) and on installing new drivers it doesnt overwrite existing ones, but creates a new directory with new files of the same name.

Go to your windows directory and search for nv*.*

The results will show you will have several duplicates of the nvlddmkm.sys file that crashes, a good install has several (not sure how many) but this method corrects any duplicates!

i presume the issue is that windows looks at the numerous driver files all telling it slightly different things and gets confused so 'stops responding and recovers! lol

anyway there are numerous and rubbish methods of sorting this problem, and only one i have found that works:

****Easy and quick**** (only removes problem files)

1) download and install 'remove on reboot' www.snapfiles.com/get/removereboot.html, this handy little program goes into your right click menu and allows you to flag files for deletion whilst windows isnt protecting them (proceed with caution, idiots will delete something important!!!)

2)delete the Nvidia 'unpacked installer' folder, by default c:\Nvidia

3)Go into safe mode, uninstall all nvidia graphics drivers

4)reboot in safe mode (yay 640*480 :rolleyes:)

5)go to windows directory and search for nv*.* and mark for deletion all copies of nvlddmkm.sys

6)reboot in safe mode

7)run driver package, unpack and install new drivers

8)reboot once more and no more problems :D

..... well until your next driver install:mad:

*****Complete method*****

As above but uninstall all nvidia drivers (inc. mobo etc as applicable)
then mark for deletion anything nv related!
then reinstall as above


i have only ever used the quick method and it works, but i know some of you out there will want all the old junk NV left behind gone:p

I accept no responsiblity for loss of files accidently marked for deletion, and obviously if anyone other than yourself (or if you dont trust yourself!) uses the pc, remove the deletion software afterwards!

hope this helps!
 
Last edited:
i think its to do with overclocking. im using the official 169.25 drivers and have had no issues with them, cant see the need for any new drivers since there are no problems with the current official ones.

as for that nvlddmkm.sys error, i can very easily replicate it. all i have to do is clock the gpu core to 850mhz and run rthdribl for a few seconds and the system BSOD's with the nvlddmkm.sys.

so id say its related to overclocking issues.
and also as willhub mentions it to me that he has had that issue before and he has overclocked his card and he hasnt even tested his oc out properly using ATi Tool to stress the gpu as much as possible so for him the nvlddmkm.sys issue is expected.

for those testing out the drivers or complaining, try running your card at stock speeds for a while and see how things go.
 
lol, i stand corrected on the oc front then!

but the method i've mentioned does work, has sorted out the issue on both my laptop (7600) and my desktop (3x8800gtx) havent had a single error since!
 
vertica said:
lol, i stand corrected on the oc front then!

but the method i've mentioned does work, has sorted out the issue on both my laptop (7600) and my desktop (3x8800gtx) havent had a single error since!
Click to expand...

I dont think its to do with OC, it may make it more Freq.

I am going to try your little trick next time (where are the next weeks promised drivers). :)
 
I used to get this very often, and ended up going back to XP.
But I recently re-installed my vista 64 HDD and updated to SP1 with the last 169 beta's and all seemed well, I had a lot of gaming over several nights with DX9 and 10 titles with no issues, I presumed MS and NV had found the problem and sorted it, maybe not if the problem persists for you .....
 
Burned_Alive said:
Suffering from this at the moment with my ATI cards :(
Click to expand...

don't suppose you're running dual screens? i was also getting the problem as soon as i hooked up a 2nd screen - back on single screen i don't have any problems at all. bloody annoying because having a 2nd screen is handy - plus the old monitor is too crap to sell so it's just sat here doing nothing at the moment. :( :p
 
You must log in or register to reply here.
Back
Top Bottom