nvlddmkm.sys keeps crashing

[maniac]

As the title suggests the file nvlddmkm.sys keeps crashing. it crashes to practically everything even playing limbo (which doesnt need that much power) the screen usually goes black and doesnt come back on, sometimes it also bsod's.

i am currently running an evga gtx580 at stock clocks using the latest 301.42 drivers, till now tried reseating the card and re installing the drivers making sure to do a clean install everytime.

dont know what to do having a gaming machine on my desk with the only ability to play solitaire -.-

I NEED HELP !

 

[PetrolHead247]

Have you tried rolling back to previous drivers or trying the latest beta driver?

 

[CPMFW]

probably a driver issue...
as above roll back the drivers!

 

[maniac]

tried installing 296.10 and it kept crashing, now i am running 306.02 beta drivers and i got an opengl error when i launched the evga oc scanner, didn't crash tho, the monitor only went black for a couple of seconds and came back

 

[Rastalovich]

These days, that error, particularly when it pops up saying the drivers recovered, tells me the gfxcard has a problem when asked to do work that's more than basic desktop.

 

[SnW]

These days, that error, particularly when it pops up saying the drivers recovered, tells me the gfxcard has a problem when asked to do work that's more than basic desktop.

This
I get that ERROR code when F@H and its because one of the chips in my GTX295 is fubbered !

 

[Rastalovich]

Pretty much.

There was a driver released way back in the Vista days that came up with this error for too sensitive a reason. Since then alot has changed, and I'm sure they've fine tuned it to pick up on card problems. Be nice if they officially documented it - but then the majority of us get is because we've oc'd (too much).

Last one I had was an nvidia based laptop. User reported this error @ desktop, then came the bluescreens, then the graphic output died completely.

 

[maniac]

just to let everybody know, it was a faulty power supply, i just rma'd it from scan as it was still under warranty, everything works fine now

 

[Excalabur50]

Nice to see the problem found and sorted.