Nvlddmkm stopped responding is getting VERY OLD...

[AdamK47]

Actually, after flashing back to an unoverclocked 8800GTX BIOS I still got the error. I'm 99.9999% certain that this error has nothing to do with my hardware. It's a driver problem.

[badboy64]

just wait. unfortunately the error comes back, just maybe not as often.
I been running the newer drivers past 1 day already and hasn't crashed period. Still running card at 660/2000 and system overclocked too.

[badboy64]

this **** ****ing sucks. This ******* error is driving me insane. To top things off I started getting nv4_disp.dll errors in XP... **** YOU NVIDIA!

Never buying another nvidia product again. Piece of ****.
Sounds more like a hardware problem than a driver problem. Maybe card is overheating or not enough case cooling. As I haven't got any BSOD or the nv4_disp.dll errors in both WinXP 32-bit and 64-bit. Still running card at 660/2000. Well then get a ati card if you think they are problem free with their drivers. :rolleyes:

[AdamK47]

I upgraded my power supply yesterday from an Antec Neo HE 430W to an Antec Neo HE 550W. So far so good. I've looped the nVidia smoke demo with two instances of Prime 95 for the past 14 hours. It hasn't gone this far without the error before.

[DarkOneX]

I upgraded my power supply yesterday from an Antec Neo HE 430W to an Antec Neo HE 550W. So far so good. I've looped the nVidia smoke demo with two instances of Prime 95 for the past 14 hours. It hasn't gone this far without the error before.

Lol this problem has nothing to do with power supplies, it's drivers and software. PowerDVD was the ONLY thing causing it for me, I quit using it and use Media Player instead, no more error, so that means PowerDVD peeps need to fix their shiz.

[chiklit]

Lol this problem has nothing to do with power supplies, it's drivers and software. PowerDVD was the ONLY thing causing it for me, I quit using it and use Media Player instead, no more error, so that means PowerDVD peeps need to fix their shiz.

It's probably a combination of both since different things seem to be fixing it for different people. For me it was 100.95 and 101.41 drivers that caused it for me while on 100.65 and 101.70 I haven't seen it once. While for others it was faulty memory, not enough power, or PowerDVD.

[AdamK47]

Lol this problem has nothing to do with power supplies, it's drivers and software. PowerDVD was the ONLY thing causing it for me, I quit using it and use Media Player instead, no more error, so that means PowerDVD peeps need to fix their shiz.

I had an Antec Neo HE 430 Watt with this system (http://www.anandtech.com/mysystemrig.html?rigid=208). It put the 430 Watt PS at it's edge with everything going. I tried getting the error by running what I know could reproduce the problem. It didn't happen at all yesterday.

[Slammin]

Definitely drivers. I've just done a clean install of Vista64 on this machine, a clean install of VistaX86 on an AMD machine, and they both will do it occasionally running 101.70. Had it with 100.41 as well on the AMD box.

[Peoples-Agent]

Are there any blasted drivers out that don't give this error?

Preferably ones that can make use of 7800 cards in SLI.

[hfxchaos]

drivers drivers drivers..got the error in vista32 all the #@$ng time, got mad, upgraded to vista64 and that actually sovled 90% of my problems...however error came back and tried running all stock speeds, still didnt change the frequency of the error..no matter what drivers or overclock i will still randomly get the error. the fact that i never got the error in winxp with the exact same hardware also points towards nvidia being retards..

[Peoples-Agent]

drivers drivers drivers..got the error in vista32 all the #@$ng time, got mad, upgraded to vista64 and that actually sovled 90% of my problems...however error came back and tried running all stock speeds, still didnt change the frequency of the error..no matter what drivers or overclock i will still randomly get the error. the fact that i never got the error in winxp with the exact same hardware also points towards nvidia being retards..

It is the drivers dude, only got these errors after shifting to Vista myself.

[JaxMacFL]

I've never had that error. Been using 100.65 WHQL since released with vista 64.

[hfxchaos]

its a pain in the a$$. im about ready to just install xp again (even though it wont use my 4gb ram, at this point i dont care). but im thinkin that as soon as i do it, they will release new vista drivers that will cure the problem.. so im just puttin it off everytime..

what the hell happened to their monthly driver releases? the last non beta release on nvidia's site was february..

[Peoples-Agent]

I get this error everytime I boot up, every single time... then it clears itself,and can use the PC as normal.

Weird.

[sclaws]

I just started getting this error repeatedly since installing 101.70 drivers. I uninstalled and reinstalled 101.41 and this issue is still occuring now! I'm out of ideas...and very disappointed in nVidia. IMO they used to be a reliable, competitive company who actually cared about quality. Those days appear to be gone for now. :thumbdwn:

[Slammin]

Well, I'm not getting it anymore. I turned off LinkBoost. LinkBoost bumps your PCI bus up to 125MHz on this mobo and I was already overclocking the PCI bus on my AMD box as well. Set it to 100MHz there too and the error went away. Been almost two days now and so far so good. My AMD box has two 7800GTX, so this problem and fix seem consistent between 8800 and 7800, at least for me.

I think the driver is extra sensitive to PCI bus frequency.

[Peoples-Agent]

Well, I'm not getting it anymore. I turned off LinkBoost. LinkBoost bumps your PCI bus up to 125MHz on this mobo and I was already overclocking the PCI bus on my AMD box as well. Set it to 100MHz there too and the error went away. Been almost two days now and so far so good. My AMD box has two 7800GTX, so this problem and fix seem consistent between 8800 and 7800, at least for me.

I think the driver is extra sensitive to PCI bus frequency.

It can't be that..... mine is set to 100, always has been.

System was stable and solid in XP.

Anything else changed on your system?

[chiklit]

It can't be that..... mine is set to 100, always has been.

System was stable and solid in XP.

Anything else changed on your system?

Is there any reason there can't be more than one cause for this error? It's just a generic error saying the display drivers have crashed.
There doesn't have to be just one cause or fix for it.

drivers drivers drivers..got the error in vista32 all the #@$ng time, got mad, upgraded to vista64 and that actually sovled 90% of my problems...however error came back and tried running all stock speeds, still didnt change the frequency of the error..no matter what drivers or overclock i will still randomly get the error. the fact that i never got the error in winxp with the exact same hardware also points towards nvidia being retards..

You're not going to get this error in XP because the error doesn't exist in XP, afaik. If the display drivers were to crash in XP the computer would either freeze or you'd get a BSOD. Whereas in Vista it's able to shutdown and restart the drivers without needing to restart the entire system. Though this has a down-side since if it's something like an overheating issue that's causing the crashes then it'll throw the drivers into a cycle of crashing and restarting every second and you'd have to do a hard reset anyway.

[Harry_Krishna]

Guys, FWIW, its not the NVidia drivers, or the 8800. I even got this error when I tired an ATi X1950 X-Fires card, just now it said a problem with the R300 driver.

To make a long story short, with the 680i LT mobo I just bought, found that it would not boot with both OCZ PC2 8500 SLI RAM in it, and would not boot if I put one of the two sticks in it. Now I know why my original 680i (AR) model would not boot, and the LED stayed at C1 - there was a memory post error!

Shortly will put the original board back in with new RAM I just bought. Though wonder if I should have gone with the Corsair SLI memory instead of going back to the OCZ SLI ones?

[Slammin]

Guys, FWIW, its not the NVidia drivers, or the 8800. I even got this error when I tired an ATi X1950 X-Fires card, just now it said a problem with the R300 driver.

To make a long story short, with the 680i LT mobo I just bought, found that it would not boot with both OCZ PC2 8500 SLI RAM in it, and would not boot if I put one of the two sticks in it. Now I know why my original 680i (AR) model would not boot, and the LED stayed at C1 - there was a memory post error!

Shortly will put the original board back in with new RAM I just bought. Though wonder if I should have gone with the Corsair SLI memory instead of going back to the OCZ SLI ones?


That ram says it needs 2.1v. Most 680i mobos default to 1.8v. My ram also is spec'd at 2.1-2.4v but luckily it will boot with 1.8v default bios settings.

Seems a lot of folks with Sli ram are having issues with 680i mobos in general though.

[sclaws]

I've decided to disable SLI for awhile and see if the error returns. This morning it happened twice already while just browsing different webpages.

[Harry_Krishna]

That ram says it needs 2.1v. Most 680i mobos default to 1.8v. My ram also is spec'd at 2.1-2.4v but luckily it will boot with 1.8v default bios settings.

Seems a lot of folks with Sli ram are having issues with 680i mobos in general though.I had the volts set to auto, will test this out. As for the heck of it, I am running 3 GIGs at the moment, it is not set to SLI mode, and so running at 800.

[Harry_Krishna]

Well, so far after a few hours now, I can confirn that it was the OCZ PC2 8500 SLI memory that was BAD! With my old motherboard back in (the original 680i, not the LT), and the new OCZ memory I just bought installed, it works and NO nvlddmkm errors as of yet!!!!!!!! If I put the original ram back in, even with the new RAM, the machine won't even boot! Time to RMA the RAM now.

[Lfctony]

Got it yesterday with the 101.70s during a CnC3 game. Back to the 100.65s for now.

[Tho Jo Smale]

I'm getting this error constantly with Startrek: Legacy.

I'm about ready to toss the entire case out the fricken window.


Vista is ghey.



JC