nvlddmkm.sys errors and crashes with Vista32/64bit

KG26_Alpha · #1 05-25-2009, 09:59 PM

I was having trouble with IL2 1946 with the error message nvlddmkm has stopped responding.

These links explain the problem and the registry edit shown fixed the problem for me.

http://www.microsoft.com/whdc/device...meout.mspx#E1B

http://forums.nvidia.com/index.php?showtopic=31913

Turning off the timeout detection:

1. Regedit.
2. Navigate to: HKLM System>Current Control Set>Control>Graphics Drivers
3. Add the following DWORD: TdrLevel and set the value to 0.
4. Reboot.

Feuerfalke · #2 05-27-2009, 10:32 PM

The fix does not eliminate the problem ( a memory conflict ) - it only removes the error-message by disabling the check and thus does not reset the driver.

On the downside, your PC will not be able to take action when it should. e.g. in case over-overheating, over-voltage or something like that and you will not be able to recover the graphics-driver if it crashes as the system will no longer notice the crash.

I'd also like to note this problem is not limited to Vista. Due to 99% the same files Windows7 suffers from the same problem.

The problem seems to be originating from 2 different problems colliding:
1. Memory running at the edge of stability.
2. Incompatibility of hardware with Windows power-saving routines.

If you choose desktop-high performance option in energy-saving options and also disable voltage being dynamically decreased for PCI/PCIe-cards, you eliminate 90% of the problem.

GF_Mastiff · #3 05-28-2009, 07:38 AM

or uninstall those drvrs and try again by doing a clean install of Nvidia drvrs.

I get that error in ATI drvrs stop responding its an error that pops up when you have been playing DX games and then run a opn GL game try running runtime restart command or reboot the computer to run open gl.

Feuerfalke · #4 05-28-2009, 08:21 AM

It's not a driver problem or a faulty installation.

It's a windows component that randomly does not correctly address memory.

Reinstalling the drivers, rebooting, underclocking, switching graphics cards, buying a new PSU, replacing memory, etc. does help as much as standing on one foot for 2 minutes or make a sack of rice fall over in China.

KG26_Alpha · #5 05-28-2009, 10:14 AM

Quote:

Originally Posted by Feuerfalke

The fix does not eliminate the problem ( a memory conflict ) - it only removes the error-message by disabling the check and thus does not reset the driver.

On the downside, your PC will not be able to take action when it should. e.g. in case over-overheating, over-voltage or something like that and you will not be able to recover the graphics-driver if it crashes as the system will no longer notice the crash.

I'd also like to note this problem is not limited to Vista. Due to 99% the same files Windows7 suffers from the same problem.

The problem seems to be originating from 2 different problems colliding:
1. Memory running at the edge of stability.
2. Incompatibility of hardware with Windows power-saving routines.

If you choose desktop-high performance option in energy-saving options and also disable voltage being dynamically decreased for PCI/PCIe-cards, you eliminate 90% of the problem.

Hmm your generalizing too much, a problem most people do with this error.

Something to bear in mind regarding my problem and this fix.

My hardware was rock solid under Win XP 32/64

Only under Vista did these errors occur.

Also Win 7 the error was there but as that's the beta and RC versions its a non valid response. afaic

This tells me that Vista is screwed, there's nothing wrong with my hardware.

This error is produced by TDR .

Its unnecessary to have it running, read the Microsoft link I provided, they tell you the registry edits themselves to fix the problem.

Feuerfalke · #6 05-28-2009, 11:01 AM

I agree with you 100% that generalizing is one of the biggest problems with this bug.

Just check out http://www.nvlddmkm.com/

There are 14 methods of fixing this problem and all claim to have the definite answer, because something worked for them. The reason is simple: The error has different causes and different effects. The only thing that remains the same is the reset and the error message.

Now, if you state that this is the ultimate fix, that is not really true. The TDR does produce the hardware-reset and the error message, but it does not eliminate the cause why the TDR is triggered: A more than 1-second freeze of your graphics card!

You should also not fall for Microsofts explanation. If you dig a bit deeper, you'll find that Microsoft released about 20 similar fixes for various bugs in Vista that are not as critical for everydays use, but still give error messages or show up in the event manager. The fixes, however do all follow the same principle: Disable the error-message, ignore and hope it works.

In other words: In case of fire disable the firealarm and all goes well. I don't see why this is sold as a professional "fix" by MS.

And I don't want to disappoint you on Win7, but the only differences between Vista and Win7 are the optics, the installation-routine and the much improved marketing campaign. There are several professional magazines which proofed that the structures running Vista and Win7 are not only similar but to 99% identical.

Keeping this in mind, it's also pretty sure the bug will be in Win7-final, too. I followed this problem for over a year now and MS strategy did not change: It's the fault of nVidia and ATI not that of MS. Nothing has changed concerning that attitude.

Am I just refering to 2nd hand information? No.

I had the problem myself when I got my ATI4870 last year. I thought it was the card and literally tested all possible fixes (including yours). Some made the crashes appear less often, some didn't help a thing. Then I found that in any combination with one of my memory stick not plugged in, it worked perfect, plugging it back in I got a crash after 30 seconds into IL2.

On my other PC I tested it for fun and found the same error appearing in Win7. Again testing all components I found it only worked flawlessly without my old IDE-DVD-ROM drive and disabled IDE-support in the BIOS.

So again, I'm glad your PC works with this trick, but it is not a general fix and people have to know that it is not fixing a bug, but silencing the alarm.