My fix for the nvlddmkm error

[sucko_the_clown]

Well folks, after everything I've tried this seems to be the only fix that works. This is just a cut and paste from the eggheadcafe with some modifications. Be sure and read thru the whole thread.

http://www.eggheadcafe.com/software/aspnet/29415832/display-driver-nvlddmkm-s.aspx

1. Delete the nvlddmkm.sys file in the windows system32 drivers folder.
2. Navigate to the folder where the nvidia sef-extracting file put all the driver files. For me it was C:\Program Files\NVIDIA\WinVista64\169.25
3. You will see a file in there called "nvlddmkm.sy_" This is the file that is expanded into the system 32/drivers folder when you first install the nvidia driver. It somehow gets corrupt on the driver installation so you have to manually expand it and cut and paste to system32/drivers folder.
4. Open up command prompt.
5. See attached file for exact directions in cmd prompt.

Once the file is expanded, move it to the system32/drivers folder and reboot your computer.

You will notice that any uninstall and reinstall of nvidia drivers will not
remove the old nvlddmkm.sys file and will not overwrite it with the newer
version. You have to do it manually. I do not know why this happens but who
cares as long it is fixed.

If you try this please give me feedback as to if it worked for you or not.

[LovingSticky]

That must be some bug on your system, you can easily verify nvlddmkm.sys file version via Hardware tab under System properties, or via NVIDIA Control Panel. They will be allright.

[sucko_the_clown]

Scratch it, the TDR error came back. This is getting annoying.

[FastRedPonyCar]

I tried every trick in the book and I think it was the heat getting to the gpu. Reason I say this is becuase I re-installed XP and fired up a game and the game would lock up and if I hit control alt delete quickly enough, I could jump out of the game and I'd see a little notification down by the clock saying the driver stopped communicating.

I haven't bothered going back to vista to see if this happens again but that's what I think it was on my machine.

[Stanley Pain]

I don't think there's "one" unique thing that causes that error. Seems that sometimes it's hardware releated and other times software. Although, anecdotal evidence seems to favour the hardware side.

[$n][pErMan]

I think its related to nVidia's ****ty drivers. I never had the problem on Vista 32-bit... but on 64-bit my FSX is taking a **** all the time with this error and also WiC on DX10 mode. Annoying the **** outta me. Might even use my Vista 32-bit again as my primary OS its so annoying. I mean come on nvidia.. its been how long sense Vista first came out? Get it right already!!! :mad:

[LORD-eX-Bu]

uh... its a problem with the OS, I had the problem on Vista 32-bit... may even be a hardware problem.

[$n][pErMan]

uh... its a problem with the OS, I had the problem on Vista 32-bit... may even be a hardware problem.
I doubt its a problem with the OS... at least if it was... I would THINK nVidia could find a way to bypass it. I think its ****ty driver coding. I noticed when I tried the new beta drivers I got the error even faster in FSX than I did with the previous drivers I had in x64. As for a hardware problem... care to explain how it would only show up in Vista? Or has there been cases in XP as well? I also never had it in Vista 32-bit.... well maybe once way back in March... but never sense in x86 Vista.

[LORD-eX-Bu]

I was getting the nv4disp.dll error in XP at the same time I was getting the nvlddmkm errors in Vista. I contacted MSI and they said that it was something wrong with the memory on my GTS... so I sent it in for RMA, got the new one and haven't had the problem since(they replaced it last march).

There are alot of causes for the problem, it could have something to do with your system memory timings or running a driver cleaner or a ton of other stuff.

[methimpikehoses]

There are alot of causes for the problem, it could have something to do with your system memory timings or running a driver cleaner or a ton of other stuff.

U R v3ry halpfool.

[LORD-eX-Bu]

hurr

[methimpikehoses]

hurr

:lol:

[sucko_the_clown]

Well I finally contacted BFG to see if they had any possible fixes to the TDR error. They sent an email back saying I need to call for an RMA number.
When I contacted them by phone and told them the problem (nvlddmkm error) they said that my card (8800 Ulta) had an old bios and needed to be sent back to them so they could flash it with the most recent one. There is an icompatibility with my current bios (video card) and windows vista.

I will report back when I get the card back from BFG.

This is the second card I've RMA'd to BFG.

GRRRRRR!!!!!

[LORD-eX-Bu]

heh, I had to RMA twice to MSI before I got rid of the error :D

[$n][pErMan]

Interesting.... the error is related to a BIOS perhaps? Keep us posted man. I can't live w/o my video card though for any length of time... hopefully something better comes out soon :p

[hell_of_doom227]

It's a bios revision problem. Certain bios versions causes this error.

[FastRedPonyCar]

hmmm I wonder if that's what's up with my msi ultra...

[sucko_the_clown]

Just to give everyone an update, I bought an evga 8800 GTS 512(G92). I've run these games @ 1900x1200 (Stalker, HL2, Bioshock, Crysis, and Fear Perseus Mandate). I have not had ONE TDR error with the 8800 GTS. This leads me to believe it was infact an old bios on the Ultra card that was causing the probem. My Ultra is RMA'd back to BFG for the BIOS flash.

Finally WinVista x64 + Nvidia + Play Games.:captnkill:

[Dragunov]

I just flashed my BIOS myself, changed the *.bin to *.rom with nibitor

Flash was succesful, but still got those error, gonna try with reinstalling driver now

[slaWter]

I just flashed my BIOS myself, changed the *.bin to *.rom with nibitor

Flash was succesful, but still got those error, gonna try with reinstalling driver now

Hope the driver reinstall will help!
I'm thinking about flashing my card if it really solves this problem.

[Dragunov]

Nope, not solution, my driver said there is not nvidia hardware in machine (169.32), so reinstalled 169.25

[slaWter]

Nope, not solution, my driver said there is not nvidia hardware in machine (169.32), so reinstalled 169.25

Did you try the 169.28?

[Dragunov]

No, not yet, didn't have time left and on Monday I leave to Barcelona with GF

[Quick209]

Just posting a link to a fix I did that resolved a whole lot of issues in this that I would like to share but going to post the link to my original post. Give it a look.

http://www.nvnews.net/vbulletin/showthread.php?t=86550&page=39