nvlddmkm is not responding

Whenever I play a game, nvlddmkm stopped responding is annoying me. Is there a way to fix this problem. Thank you

See suggestions given in similar type of threads: http://forums.techarena.in/vista-help/686029.htm
http://forums.techarena.in/vista-har...ces/686036.htm
http://forums.techarena.in/monitor-v...rds/930017.htm
http://forums.techarena.in/vista-har...ces/689444.htm

I also had the same problem...
Windows Vista Layers OpenGL on top Of Direct X causing a Huge Decres in Preformance... To Get around this You have to change windows theme to Classic. (Ugly) but it works. World OF warcraft runs great no Problems....


Disabling the Areo Visuals Stops the DirectX and fixes the Problem for me..

Hope you have the same Luck..

This bug/error appears to be a Vista driver issue, and for me its driving me nuts trying to fix. I'm hoping this thread can be a place where tried hardware/software etc fixes can be posted for all to share--I've had little success with this and am curious what others have tried and their results.

For me, I had no problems until updating from 100.65 to 101.70. Since then -the bug inevitably recurrs under any conditions, at any time (sometimes just after first boot, other times won't be until after hrs of gameplay).

FIX ATTEMPTS
- Tried uninstalling/reinstalling 100.65--error continues.
- Set all BIOS voltages from AUTO to their hard spec--error continues.
- Disabled SLI--error continues.
- Reinstall 158.18 clean--error continues.
- Reinstall 158.18 over itself--error continues.
- Tried registry hack:
*HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contr ol\GraphicsDrivers
*ADDED TdrDdiDelay (REG_DWORD) 20
*ADDED TdrDelay (REG_DWORD) 20 --error continues.
- Swapped SLI bridge; switched SLI connector ports--error continues.

FIXES TO ATTEMPT:
- Run one card at a time for awhile to determine if this is indeed a hardware issue.
- Install a driver previous to 100.65
- Underclock video cards (Not an option IMO..should run stable as-is)
- Underclock RAM (Again not an option IMO)
- Start RMA'ing hardware (I don't think this will help as I'm pretty sure its a software issue)

Some users have solved the problem by actually uninstalling a windows hot fix, the "KB952287" patch. (Vista Users)