• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

nvlddmkm display driver has stopped responding...

T

The_Juggernaut

n00b
Joined
Mar 24, 2007
Messages
23
Ok. Well, I just got World in Conflict the other day and it's an awesome game. It runs great on the system in my sig running Vista Home Premium 32-bit on max settings and 1680x1050.

So everything's running smoothly until I beat the first level and the game shifts to the cut scene. At that point, the game appears to freeze up for about 15-20 seconds. Afterwards, the screen flashes black and goes to the desktop, giving me a message in the taskbar that reads: "A display driver nvlddmkm has stopped responding and has recovered." From then on, the display driver will continually crash and recover unless I reboot my system.

This only happens to me in World in Conflict it seems as I've never had this message even after hours of playing Supreme Commander, Counterstrike, Oblivion, etc. This is the first DX10 game I've run though (which might be why I've never seen the message before).

I have the the latest non-beta drivers for my 8800GTX and Vista is fully updated. I've also looked all over the internet and it looks like this problem happens a lot, but I haven't found a solid fix yet. If anybody could help me with this issue, I'd really appreciate it, I wanna play WiC bad :(.
 
Download the 169.71 beta drivers and follow this uninstall process.

Uninstall from Program's and Software. Reboot to safemode. Delete the Display Adapter from Device Manager, Delete the driver when asked. Delete the Nvidia folder (root). Delete all NV*.* files (MAKE SURE THEY ARE NVIDIA files!!). Clean the registry. You can also use a driver cleaner for the file deletion part. Reboot to normal mode and install 169.71 beta drivers.

Try running it with Vsync off and see if that helps. Try it at 1280X800 (same aspect as 1680X1050.
 
Thanks for the advice, I'll give it a try. I just have two questions:

When you say "delete the Nvidia folder (root)," do you mean the driver files or the files in System32?

My second question is how do I delete all the old Nvidia files, or will driver cleaner take care of all of the right ones for me (and if driver cleaner does, does it also take care of the Nvidia root folder)?

Thanks.
 
I have the same problem also, I am using the recent stable nvidia drivers. Does the beta driver fix this issue in WiC or something?
 
I've actually had more stability issues with the 163.71 beta drivers, myself. As with most things YMMV but I think the current "tree" is iffy at best. Had more luck with the 163.69 betas than the WHQL'd version, which hardly makes sense.
 
Delete C:\Nvidia. Find all the Nvidia files in C:\windows\system32\drivers and get rid of them. Drive Cleaner is pretty decent.

I found that the beta did better, but as the above poster says, it's not always going to be good for you. I read both the good and the bad. Its at least a step.

Nvidia's drivers and vista aren't "ripe" just yet.
 
Sean said:
Nvidia's drivers and vista aren't "ripe" just yet.
Click to expand...

I wouldn't say that. They did very well with the 160 series and the earlier 163.xxs. I think what we're running in to here is a rush, a major push, to optimize for Crysis before release, which appears to be breaking other things that were working just fine as of around 163.44ish.
 
You must log in or register to reply here.
Back
Top