NVLDDMKM.dll forcing upgrade

N

Niksa

Limp Gawd
Joined
Feb 8, 2005
Messages
228
My friend is using a Vista system with: SLI ECS N8800GTS-512MX GeForce 8800GTS (G92) 512MB 256-bit GDDR3 PCI Express 2.0 x16 HDCP and a
EVGA 123-YW-E175-A1 LGA 775 NVIDIA nForce 750i FTW SLI ATX Intel Motherboard
Q6600, 4 GB RAM, etc.

He keeps getting this NVLDDMKM.dll error (and many other problems with the vid card) when watching movies or playing games. I posted about this in the NVidia board a long time ago, but there was not really a solution available.

Now he is looking to upgrade. Does anyone know if the GTX 260 has this problem as well (driver issues)? I haven't seen any reports of it, but just checking. Or should he just go ATI?
 
NVLDDMKM.dll is from Nvidia so he should go ATI to clear his mind.
Honestly, though -- I've NEVER had one of these errors...
 
That error only states that the driver did crash but not why it crashed. Do a search for ATIKMDAG or IGFX and you will find the same error from ATI and Intel. NVIDIA has a support article with diagnostic steps at http://nvidia.custhelp.com/cgi-bin/nvidia.cfg/php/enduser/std_adp.php?p_faqid=22. If he can, try the card in another system. If it does the same thing in a previously working system than it should be a faulty card and just replacing it will fix that.

The GTX260 will be a pretty decent jump in performance coming from an 8800GT and has been a very stable card for us. Be sure that you pair it with a high quality power supply.
 
I was having countless issues with this myself earlier this year and last year. Started with XP and continued into vista. I solved my problem by ditching the Striker Extreme.

However I later re-examined the problem with the Striker Extreme and long story short... 2 striker extremes had bunk memory controllers that fried and then friend the memory with them which was causing these errors.

Personally... after that experience... i stay away from nvidia chipsets. I had 6 680i boards all give me the same problems. However a P5K Premium, Maximus Formula, and a couple P5E-VM's all based on intel P35/X38 chipsets work flawless once I replace the fried from from the 680i boards.

If you have some spare memory to try in it try that first and if the motherboard or mem is OC'ed at all reduce it to stock (preferably around 800mhz on the memory)

Also as previous poster said try the video card in a known working computer and see if you can duplicate the error. If not then its something else in the system.
 
Ok - we are going to check the video card first and then move from there. I hope it's not the motherboard though, simply because that is truly a hassle. :/

We designed this system back in June with the help of [H] and at the time, no one connected this error with a specific card or motherboard or a combination. I think the motherboard and the card are both fairly popular and commonly used together, so it would surprise me if it's not a random defect, because then everyone with the 750i and 8800 SLI would be having this problem and it would have been isolated a long time ago, right?
 
Niksa said:
Ok - we are going to check the video card first and then move from there. I hope it's not the motherboard though, simply because that is truly a hassle. :/

We designed this system back in June with the help of [H] and at the time, no one connected this error with a specific card or motherboard or a combination. I think the motherboard and the card are both fairly popular and commonly used together, so it would surprise me if it's not a random defect, because then everyone with the 750i and 8800 SLI would be having this problem and it would have been isolated a long time ago, right?
Click to expand...

Go over to the EVGA forums and just see how muny problems these boards have (i also realize this is kind of moot due to the fact of the mass number of boards out there in relation to the number who post on forums...)


At anyrate its not just an open and shut case. Start off with trying the video card in another rig. if the card proves to be good then i would suggest running memtest86+ over night and see what comes out of it (though my system at one point would pass memtest and all other stress tests out there yet randomly lock up or give me that dreaded nvidai dll error). After that try some different ram.

Good luck.
 
Oh - I mean I believe you Bun-bun with the NVidia Chipsets. I'm going to build my own computer this week, hopefully, and I'm going to take your advice about the mobo for certain. :)

Sadly, my friend no longer lives in the same state as I do, and I'm not sure if he will be able to find another person to help him test, but hopefully he can work something out! I will pass the advice along and I'll update this thread if this is fixed in the future.

Thanks guys!
 
You must log in or register to reply here.
Back
Top