Hello,Post it this on the fs2004 forums and i've been to post here."nvlddmkm has stopped responding and has successfully recovered." Just won't go away. I get it during taxi or landing whether it is a payware airport, freeware airport, or default airport. I tried every driver that nvidia released and so far nothing. I'm this close to just quit this hobby.Has anyone been able to find a solution for this problem? Or has been able to minimize the severity of this error?Your help is much appreciated.

Hello,Post it this on the fs2004 forums and i've been to post here."nvlddmkm has stopped responding and has successfully recovered." Just won't go away. I get it during taxi or landing whether it is a payware airport, freeware airport, or default airport. I tried every driver that nvidia released and so far nothing. I'm this close to just quit this hobby.Has anyone been able to find a solution for this problem? Or has been able to minimize the severity of this error?Your help is much appreciated.

It is not FSX/FS9 problem but a problem with your Nvidia drivers not being properly installed. Uninstall your display drivers then run a driver cleaner. Reinstall the display driver and make sure UAC is turned off and disable any anti-virus programs until the display driver has been reinstalled. Here's a link to one fix which pretty much reiterates what I have stated above: http://www.overclockers.com/forums/showthread.php?t=518749. This is pretty much a problem with Vista and earlier operating systems. I haven't heard about this issue yet with Windows 7 64 bit users.Best regards,Jim

It is not FSX/FS9 problem but a problem with your Nvidia drivers not being properly installed...This is pretty much a problem with Vista and earlier operating systems. I haven't heard about this issue yet with Windows 7 64 bit users.Best regards,Jim

I'll be first. It happened today, flying the LevelD 767 in FSX with the 257.21 Nvidia drivers, GTX285, and WIN7 x64. Before anyone asks, no, I had not properly uninstalled the 197.45 drivers which had worked without problems. For some dumb reason I decided to see if the suggestion that Nvidia had improved their install routines was true. :( Perhaps not, so I'll now run the driver cleaner and reinstall the drivers and see what happens.Claude(i7-860, ASUS P7P55D Deluxe, 4GB Memory. Not overclocked at present)

I'll be first. It happened today, flying the LevelD 767 in FSX with the 257.21 Nvidia drivers, GTX285, and WIN7 x64. Before anyone asks, no, I had not properly uninstalled the 197.45 drivers which had worked without problems. For some dumb reason I decided to see if the suggestion that Nvidia had improved their install routines was true. :( Perhaps not, so I'll now run the driver cleaner and reinstall the drivers and see what happens.Claude(i7-860, ASUS P7P55D Deluxe, 4GB Memory. Not overclocked at present)

there have been posts that driver cleaners can cause problems. With the nVidia drivers, it is not required to un-install them and it is not required to use any third party cleaner. I have spent the last month upgrading drivers countless times by simpy installing the latest and greatest. In fact, if you uninstall a nvidia driver, it restores your previous version automagically. If you are in an undefined state of corruption, keep uninstalling all video drivers back to the virgin stock windows VGA. I do use and reccomend that you use registry mechanic to clean and compact your reg and then install your desired vid driver. All will be fine!!

Scott is right on the money, when I first got my new gtx 480 I was getting that crash all the time. A forum member told me to stop using a driver cleaner and stop uninstalling previous drivers, just install any new ones right over top of the old ones. Haven't had a crash yet.

I will add to the list of people saying to stop using driver cleaners. With my GTX 275, 470, and 480, I installed the drivers from the CD, and from then on I downloaded drivers from Nvidia and installed them right over whatever driver I was currently using. Using this method, the only crashes I ever had were related to overclocking the 470/480 to far, and some UsePools=0/ENB Series combination issues.

This error has plagued many users of Vista (and W7 gamers are also reporting it) for a long time, and it's not necessarily as simple as just being a driver error. It's telling you that Windows has detected a hang in the graphics subsystem (GPU and/or driver), and that it is resetting the subsystem (which results in crashing FS). It can be caused by a faulty driver installation, a faulty/underpowered/overheated GPU, and possibly even latency issues as a side effect of other misbehaving devices. I had this problem cropping up with a 285GTX and the problem turned out to be intermittent GPU issues that forced an RMA. There's some evidence that the nVidia reference design for some of the 285GTX boards has the voltage regulators set so that the GPU chip is on the ragged edge of being undervolted, and unstable when run hard for long periods of time as a result. I've never seen this problem with my 8800GTX or my 480.Two things I would recommend are a fresh driver install, and possibly loosening the TDR timeout parameters in the registry a bit. See http://www.microsoft.com/whdc/device/displ...dm_timeout.mspxPer the article, I added DWORD values to bump the TdrDdiDelay and TdrDelay values up to 20, and it cut way back on the problem with the old misbehaving 285. You can also set TdrLevel to 0 which disables the TDR recovery process altogether, but this will cause a hard lockup of the system if there's a legitimate GPU hang and not just something causing an intermittent but excessive delay in graphics system response.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

This error has plagued many users of Vista (and W7 gamers are also reporting it) for a long time, and it's not necessarily as simple as just being a driver error. It's telling you that Windows has detected a hang in the graphics subsystem (GPU and/or driver), and that it is resetting the subsystem (which results in crashing FS). It can be caused by a faulty driver installation, a faulty/underpowered/overheated GPU, and possibly even latency issues as a side effect of other misbehaving devices. I had this problem cropping up with a 285GTX and the problem turned out to be intermittent GPU issues that forced an RMA. There's some evidence that the nVidia reference design for some of the 285GTX boards has the voltage regulators set so that the GPU chip is on the ragged edge of being undervolted, and unstable when run hard for long periods of time as a result. I've never seen this problem with my 8800GTX or my 480.Two things I would recommend are a fresh driver install, and possibly loosening the TDR timeout parameters in the registry a bit.Bob,Your post succinctly summarizes what I was finding on the web. The error ain't necessarily a driver issue, it's been around a long while, and TDR is a factor. My GPU is an EVGA 285GTX superclocked model installed in Feb along with an upgraded PSU and Nvidia 196.75's. In April installed 197.45's. No CTD's or BSOD's. Two weeks ago I installed the 257.21's. Again no problems until this past Weds when the error occurred. For that flight I decided to fly with TrackIR5 (hadn't used it for awhile). Before take-off TrackIR was not responding properly and corrupting the VC display, so I closed it. The flight from KSEA to KSFO was uneventful until approach to KSFO when the error occurred. I've since been able to induce the error on the ground by frequently and intentionally switching between outside and inside views with lots of zooming.Taking your suggestions thought I'd do the following: 1) Re-install the 257.21 drivers after uninstalling them through the Win7 control panel. 2) Set the GPU card fan at 100% and trying the same flight to possibly eliminate heat as a major issue. 3) Setting the TDR values you suggested (not to disable), but do have a question. The TDR parameters do not appear to be in the Win7 registry. There is a suggestion that they can be added to the HKLM key. Do you agree? 4) If this doesn't work, then I'm going to reinstall the 197.45 drivers and consider next steps.Claude

Bob,Your post succinctly summarizes what I was finding on the web. The error ain't necessarily a driver issue, it's been around a long while, and TDR is a factor. My GPU is an EVGA 285GTX superclocked model installed in Feb along with an upgraded PSU and Nvidia 196.75's. In April installed 197.45's. No CTD's or BSOD's. Two weeks ago I installed the 257.21's. Again no problems until this past Weds when the error occurred. For that flight I decided to fly with TrackIR5 (hadn't used it for awhile). Before take-off TrackIR was not responding properly and corrupting the VC display, so I closed it. The flight from KSEA to KSFO was uneventful until approach to KSFO when the error occurred. I've since been able to induce the error on the ground by frequently and intentionally switching between outside and inside views with lots of zooming.Taking your suggestions thought I'd do the following: 1) Re-install the 257.21 drivers after uninstalling them through the Win7 control panel. 2) Set the GPU card fan at 100% and trying the same flight to possibly eliminate heat as a major issue. 3) Setting the TDR values you suggested (not to disable), but do have a question. The TDR parameters do not appear to be in the Win7 registry. There is a suggestion that they can be added to the HKLM key. Do you agree? 4) If this doesn't work, then I'm going to reinstall the 197.45 drivers and consider next steps.Claude

Claude; The TDR params are not there by default in either Vista or W7. So yes, they should be added to the HKLM hive. Generally speaking, looks like a good plan to me.CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO