I had it OC'd quite high 3.6gig on an E6600 which was fine for awhile but then during the summer (well the few warmer days we had) I started getting that error and random crashes in games... ran memtest and it came up with loads of random errors (which didn't seem like a RAM problem to me) - tried the RAM in my other PC and it checked out fine - so I put a fan on the NB and dropped the volts on it back -0.1 and its been fine ever since.
-
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.
The dreaded Display driver nvlddmkm stopped responding and has successfully recovered
- Thread starter mikeo
- Start date
I had it OC'd quite high 3.6gig on an E6600 which was fine for awhile but then during the summer (well the few warmer days we had) I started getting that error and random crashes in games... ran memtest and it came up with loads of random errors (which didn't seem like a RAM problem to me) - tried the RAM in my other PC and it checked out fine - so I put a fan on the NB and dropped the volts on it back -0.1 and its been fine ever since.
vertica
Thanks for that. If it happens again, new drivers (and making sure that things have been cleaned up correctly first) will be the next thing I try.
Though got to admit that I'm still a little confused as to why there are already several vesions of nvlddmkm.sys on my system (it's 6 I think) and each pair of these have a different date / size (so I'm assuming they are different). Especially as I've only installed one and only one set of graphics card drives! Can their driver install routine really be that bad, that they have not cleared duplicate / older version of nvlddmkm.sys out of the driver pack!? From all the evidence, it certainly looks that way!!!
Rroff
Thanks for the reply. My E8400 runs a fair bit cooler than your chip, especially at stock. Which is why initially I left the CPU fan on auto, which had it only spinning at half speed, since the last pseudo BSOD I've set the fan to a fixed 100% (hardly any noise increase) so that should increase the cooling for the NB as well. Though if all else fails, I'll consider tweaking the NB voltage.
Thanks for that. If it happens again, new drivers (and making sure that things have been cleaned up correctly first) will be the next thing I try.
Though got to admit that I'm still a little confused as to why there are already several vesions of nvlddmkm.sys on my system (it's 6 I think) and each pair of these have a different date / size (so I'm assuming they are different). Especially as I've only installed one and only one set of graphics card drives! Can their driver install routine really be that bad, that they have not cleared duplicate / older version of nvlddmkm.sys out of the driver pack!? From all the evidence, it certainly looks that way!!!
Rroff
Thanks for the reply. My E8400 runs a fair bit cooler than your chip, especially at stock. Which is why initially I left the CPU fan on auto, which had it only spinning at half speed, since the last pseudo BSOD I've set the fan to a fixed 100% (hardly any noise increase) so that should increase the cooling for the NB as well. Though if all else fails, I'll consider tweaking the NB voltage.
Soldato
- Joined
- 29 May 2005
- Posts
- 5,622
- Location
- West London
This happened once with my 8800GTS 512mb previously, straight after driver install. Never ever happened again. It ran 2 LCDs.
Happened every few minutes with these 4850s then sorted it with the new beta drivers.
Happened every few minutes with these 4850s then sorted it with the new beta drivers.
this problem is NOT random here
all games works fine. Folding 24/7 works fine. ATI Tool scan for artifact works fine. Folding+gaming works fine.
but if i leave Folding for more than (say) 6 hours, and try to play a video file, that error comes up 80% of the time.
it's really strange, and because i watch a lot of videos, i have to hold my breath EVERY time i launch a video
although i do suspect the RAM is to blame for other people here, as my OCZ Platinum 4GB used to have problems. changed to Corsair XMS2 8GB and haven't had that problem until i started Folding on 8800GTX.
all games works fine. Folding 24/7 works fine. ATI Tool scan for artifact works fine. Folding+gaming works fine.
but if i leave Folding for more than (say) 6 hours, and try to play a video file, that error comes up 80% of the time.
it's really strange, and because i watch a lot of videos, i have to hold my breath EVERY time i launch a video
although i do suspect the RAM is to blame for other people here, as my OCZ Platinum 4GB used to have problems. changed to Corsair XMS2 8GB and haven't had that problem until i started Folding on 8800GTX.
My brother has this problem, he's literally tried every trick in the book, and every trick you've mentioned to try and stop the error occurring.
So now he's sent his graphic card back to BFG.
http://forums.overclockers.co.uk/showthread.php?t=17913120&highlight=username_craig321
So now he's sent his graphic card back to BFG.
http://forums.overclockers.co.uk/showthread.php?t=17913120&highlight=username_craig321
This is the single biggest problem I've had with my pc over the past year and half ish.
For me, it's all down to dodgy drivers. I've had to make a collection of 'safe' drivers in case any new ones nvidia releases are not up to snuff.
The 177.83s are the worst I've seen for awhile, strangely the beta 177.92s are one of the most stable.
Safe drivers - 169.51 - 175.19 - 177.92. Every other causes a catastrophic fault in some way or another.
For me, it's all down to dodgy drivers. I've had to make a collection of 'safe' drivers in case any new ones nvidia releases are not up to snuff.
The 177.83s are the worst I've seen for awhile, strangely the beta 177.92s are one of the most stable.
Safe drivers - 169.51 - 175.19 - 177.92. Every other causes a catastrophic fault in some way or another.
Rezident
Well fingers crossed I've not had it happen again (though it was a totally random problem anyway). So whether turning the CPU fan to max has "really" sorted it, is any one's guess (though CPU temps have never been an apparent problem anyway). Maybe the extra cooling that doing this has created across the NB has helped, again is anyone's guess. Only other thing I tried, was tightening the screws that hold on the HSF on my graphics card (though again, temps did not "appear" to be a problem here anyway). Just glad it's not raised it's head again (yet). Managed to finish Company of heroes - Opposing Fronts and now well into Supreme Commander and all currently appears fine in PC land.
wuyanxu
"although i do suspect the RAM is to blame for other people here"
I'm sorry but I don't think it's as simple as that. Otherwise there must be an awful lot of duff memory doing the rounds and after many years of building PC's I'm inclined to say that this isn't the case. No offence meant.
Well fingers crossed I've not had it happen again (though it was a totally random problem anyway). So whether turning the CPU fan to max has "really" sorted it, is any one's guess (though CPU temps have never been an apparent problem anyway). Maybe the extra cooling that doing this has created across the NB has helped, again is anyone's guess. Only other thing I tried, was tightening the screws that hold on the HSF on my graphics card (though again, temps did not "appear" to be a problem here anyway). Just glad it's not raised it's head again (yet). Managed to finish Company of heroes - Opposing Fronts and now well into Supreme Commander and all currently appears fine in PC land.
wuyanxu
"although i do suspect the RAM is to blame for other people here"
I'm sorry but I don't think it's as simple as that. Otherwise there must be an awful lot of duff memory doing the rounds and after many years of building PC's I'm inclined to say that this isn't the case. No offence meant.
Last edited:
Yeah I'm pretty sure it's not my ram. Have undone all overclocks, everything is at stock now. Temporatures are well within tolerances (AH! resonance cascade)
This did not happen with the last whql drivers and has happened at least ten times with the current ones. Nvidia has managed to install SIXTEEN nvlddmkm.sys files on on system!
Never happened on XP 9(et) so I'm convinced it's between Vista and the drivers.
This did not happen with the last whql drivers and has happened at least ten times with the current ones. Nvidia has managed to install SIXTEEN nvlddmkm.sys files on on system!
Never happened on XP 9(et) so I'm convinced it's between Vista and the drivers.
A poll for this would be nice - Do you experience this problem?
1) Yes, and I tweak my mobo BIOS.
2) No, and I tweak my mobo BIOS.
3) Yes, and my mobo BIOS all at defaults/auto.
4) No, and my mobo BIOS all at defaults/auto.
Can't remember how many issues I had when had my nvidia cards.
1) Yes, and I tweak my mobo BIOS.
2) No, and I tweak my mobo BIOS.
3) Yes, and my mobo BIOS all at defaults/auto.
4) No, and my mobo BIOS all at defaults/auto.
Can't remember how many issues I had when had my nvidia cards.
It could help, it depends on what your problem is. This problem is VERY general and could be multiple things. I've seen people fix it by simply doing a uninstall/reinstall using DriverSweeper, other people have had to manually install the correct nvlddmkm.sys file from C:\NVIDIA\.
People have fixed it by turning Aero off, dreamscene off, desktop composition off, underclocking, reducing an overclock, using one stick of RAM at a time in their PC, replacing their RAM, changing RAM voltage, etc etc
Associate
- Joined
- 20 Aug 2005
- Posts
- 369
I have a factory overclocked MSI 8800 Ultra card. I always thought this problem was a hardware problem, as I tend to get it when I add more detail to games (mainly through upping AA)...
this fix worked for me from some clever boffins that work for amd/ati .
seems about fifty fifty chance off working on other forums i use , its all to do with how vista responds to tdr's .
run programmes type msconfig.
click the boot tab.
click the advanced options.
put a check in number off processors
and put relevant number in box ( ie 2 for dual 4 for quad )
then more importantly put a check in maximum memory box ( should highlight how much memory you have got use all )
click ok then apply
seems about fifty fifty chance off working on other forums i use , its all to do with how vista responds to tdr's .
run programmes type msconfig.
click the boot tab.
click the advanced options.
put a check in number off processors
and put relevant number in box ( ie 2 for dual 4 for quad )
then more importantly put a check in maximum memory box ( should highlight how much memory you have got use all )
click ok then apply
I totally agree that it could be any number (or even "combination") of things. I'm not even dismissing the idea that it can/could be memory related. Not necessarily duff memory but the fact that certain motherboards do not "get on" with certain makes/ratings of memory. Hence why when I do a new build I always research what other people have successfully used in any motherboard I'm interested in.
EG. I know myself that the new ASUS P45 mobos can be a bit touchy about what brand of memory (have a look at ASUS's own forum/s to see this!). One of the reasons that I want for a tried and tested P35 mobo this time. But I digress somewhat here!
slap ed
That's a new one on me. I'll add it to my list of "potential" resolutions if I have more problems.
One thing that does seem pretty obvious to me, is that Vista appears to be maybe a bit sensitive to responding to TDR's (too sensitive maybe?). Now I'm not totally blaming Vista for this problem, but I am sort of beginning to wonder if the driver has "really" stopped responding sometimes! An interesting thought!?
One thing from researching this problem that is becoming blatantly clear, is that there are many, many, many things that can cause/contribute to this problem/issue and hence it appears to be a matter of trying all the potential solutions until hopefully the problem can at least be "contained" if not totally eliminated. Wise words I expect, but not much help to those that can't find a solution.
PC's... great things when they work. But when they go wrong, they can frustrate the hell out of you.
EG. I know myself that the new ASUS P45 mobos can be a bit touchy about what brand of memory (have a look at ASUS's own forum/s to see this!). One of the reasons that I want for a tried and tested P35 mobo this time. But I digress somewhat here!
slap ed
That's a new one on me. I'll add it to my list of "potential" resolutions if I have more problems.
One thing that does seem pretty obvious to me, is that Vista appears to be maybe a bit sensitive to responding to TDR's (too sensitive maybe?). Now I'm not totally blaming Vista for this problem, but I am sort of beginning to wonder if the driver has "really" stopped responding sometimes! An interesting thought!?
One thing from researching this problem that is becoming blatantly clear, is that there are many, many, many things that can cause/contribute to this problem/issue and hence it appears to be a matter of trying all the potential solutions until hopefully the problem can at least be "contained" if not totally eliminated. Wise words I expect, but not much help to those that can't find a solution.
PC's... great things when they work. But when they go wrong, they can frustrate the hell out of you.
That is very interesting in my case - the last time it happened, before it blue-screened, I was able to get out of the game and back to desktop. It was flickering black and back to desktop but it definitely looked like it had recovered (apart from the game not responding - this has happened with multiple games so it's not a particular game). It took a full maybe-20 seconds to actually BSOD, so you could be on to something there.