nvlddmkm has stopped responding!!! OMG please help.

This topic is locked from further discussion.

Avatar image for Shrinekeeper
Shrinekeeper

331

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#1 Shrinekeeper
Member since 2003 • 331 Posts

Ok, so my friend and I pretty much built our computer at the same time, he went AMD I went Intel. He got a 9600gt I got a 9800gtx. Now he is getting the cursed nvlddmkm error and we have tried everything just about. I on the other hand have been lucky enough not to have any issues as of yet.

We have tried several different version of Nvidia Drivers, we have manually set timers/voltage for his Ram. We have booted up in safe mode and ran Driver Cleaner, plus we manually removed nvlddmkm.sys and replace it with a newer version. NOTHING seems to work. I have read countless pages upon pages of people having this problem with both nvidia and ati cards. So is this a Vista issue or perhaps a hardware issues somewhere along the line?

Has anyone at all managed to fix this problem with some off the wall fix that we may have not thought of? Any help at all would be more than appreciated.

Avatar image for ch5richards
ch5richards

2912

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#2 ch5richards
Member since 2005 • 2912 Posts

When does he get the error?

I get it sometimes, but only in certain games, like WiC, and there is another one I remember getting it in, but I forget what game it is now. Since I only get the error in these 2 games, I feel my problem is with the games themselves not the hardware. But if it is happening in every game or even out of games, then I think you have a problem.

Avatar image for Shrinekeeper
Shrinekeeper

331

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#3 Shrinekeeper
Member since 2003 • 331 Posts

As crysis is the only game he has at the moment I'm not sure if I would say its a game issue. But when he tries to run a stress test on his video card he is getting the error as well. I would say its a video card hardware issue but I find that hard to believe as this problems seems to be very wide spread. Everything he has is at stock speed and his temps seem to be fine.

I finally managed to get this error on my PC, yes I entionally attempted to cause this error (silly me) by OCing my 9800gtx by quite a bit its stock is 675/1100 and I bumped it up to 832/1280 and finally got the error while playing crysis. I lowered it back down to stock and problem fixed. But as i said earlier is card is not overclocked manually or stocked.

I dunno what the deal is and am not sure if Microsoft or Nvidia needs to be burned down to the ground, or if its something else entirely. But it sucks to spend $900 on a PC and the damn thing not even do what you bought it for.

Avatar image for nimatoad2000
nimatoad2000

7505

Forum Posts

0

Wiki Points

0

Followers

Reviews: 5

User Lists: 0

#4 nimatoad2000
Member since 2004 • 7505 Posts

check out the nviida forums, theirs a few pages on multiple posts for the problem your having, the 700 mobo series is problem rigged and the the 9 series has some driver bugs atm.

i had it once and i fixed it by - uninstall all your nvidia drivers, mobo / gpu .. everything, delete the nvidia folder, reboot to safe mode, run driver cleaner pro , make sure everything is whiped, restart into safe mode again, install all your drivers, but it seems you have done that so i hope the nvidia forums give you a better alternative answer.

Avatar image for Plo_Koon_basic
Plo_Koon_basic

801

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#5 Plo_Koon_basic
Member since 2003 • 801 Posts
also make sure your ram is working properly. i had the issue and found out that it was my Ram, so i had to RMA it and now it runs fine.
Avatar image for Shrinekeeper
Shrinekeeper

331

Forum Posts

0

Wiki Points

0

Followers

Reviews: 0

User Lists: 0

#6 Shrinekeeper
Member since 2003 • 331 Posts

Yea he is going to bring his PC over Sun. and I am going to put my Ram in his PC and see if that fixes the problem. Also he does not have a nvidia chipset mobo, but we did not install the drivers in safe mode, we did that in regular mode. Would that have anything to do with it?