nvlddmkm stopped responding ?

[emfiend]

Just to add one more experience to this....

Q6600 is at 3.0Ghz and is undervolted to 1.3v. System has been running fine with the 8800GT since I got it last november.

Last week I got an Accelero S1. Wasn't happy with temps from 8800gt factory cooler. Took meticulous care to remove all remnants of the old thermal compound (netting?) from the video proc and mem sinks using Goof Off.

Put it back into my case (TT Armor) which, incidentally, has horrible alignment with the PCI slots and I had to push hard to get the retaining screw on, the same way I had to when it had the original factory cooler. This is the only thing that I *think* would have been a source for problems.

Since then, persistent nvlddmkm messages... I'm screwed.

 

[ZK2007]

Just an update to this nvlddmkm driver problem.. still a thing of the past. I've since updated to Vista 32bit SP1 and still running perfectly. It's been 6 months without so much as a hiccup. My system runs 24/7 365 days a year and I game quite a bit on it so it's been through some harsh testing. Granted it didn't need "testing" to crash on that nvidia chipset board, either. Just moving the mouse would send my system into a downward spiral it seemed. I run Dreamscenes, multiple monitors, everything I throw at it is done flawlessly. I love my system, though now I wouldn't mind owning a 9800 series video card, but not about to spend $600+ for it so soon after getting my 8800gtx working like it should on my intel board. I couldn't see how I'd notice any real world difference between the two anyways.

 

[rizorith]

I still get crashes with this. Gotta love a bug first reported in April of 07 is still around.

 

[coloumb]

I'm pretty much fed up with Vista and nVidia as well. Time to revert back to XP as the nvlddmkm driver issue should've been fixed by now. It's been over a year since this issue has been happening and neither nVidia or MS seems to be doing anything about it.

The real annoyance of this is that it's very random. I can play games without a hiccup for days then out of the blue - the issue will happen multiple times. Usually a system reboot fixes the issue.

 

[taltamir]

Originally posted by: rizorith
I still get crashes with this. Gotta love a bug first reported in April of 07 is still around.

That isn't "a bug". It is a symptom. you get that message when the video card crashes. It could be because of:
Driver Bugs - many were fixed already, others have yet to be fixed.
Vista bugs - many were fixed, others yet to be.
Faulty hardware
Overclocking
Software bug - A specific game can have a bug that causes that. I have seen many, and many were fixed.
Etc.

Read the thread before you post in it. All it is, is that the video card was restarted by vista because it crashed for some reason. That is the INTENDED thing, because in XP it will result in the entire system freezing and you had to hit the reset button. Now it restarts the video card. The problem is still that the video card crashed.

 

[Slacker]

Originally posted by: taltamir

Originally posted by: rizorith
I still get crashes with this. Gotta love a bug first reported in April of 07 is still around.

That isn't "a bug". It is a symptom. you get that message when the video card crashes. It could be because of:
Driver Bugs - many were fixed already, others have yet to be fixed.
Vista bugs - many were fixed, others yet to be.
Faulty hardware
Overclocking
Software bug - A specific game can have a bug that causes that. I have seen many, and many were fixed.
Etc.

Read the thread before you post in it. All it is, is that the video card was restarted by vista because it crashed for some reason. That is the INTENDED thing, because in XP it will result in the entire system freezing and you had to hit the reset button. Now it restarts the video card. The problem is still that the video card crashed.

I dual boot xp and vista, the problem happens in vista only, xp is fine, and the card has been fine in xp for quite a while.

 

[ShadowFlareX]

I get this problem randomly although very seldomly since I switched over to Rampage Formula from Abit IN9 32X-MAX. In my case, I have a feeling this is more down to the RAM speed. You see, I never get this problem on my Abit IN9 board, but my RAM was always running at 800MHz. If I set the RAM to 900MHz or higher, I'll get the lovely nVRAID corruption warnings. It was one of the main reasons I switched boards.

Now that I've switched boards, I run 1066MHz RAM with no problem, apart from this seldom occasions of nvlddmkm stopped responding error.