I wonder if anybody can help.First, upgraded the perfectly-working Nvidia 285 drivers to the latest WHQL 295 drivers when I spotted a post that it was released a few days ago. Immediately started having some weird issues with the just PMDG JS41 in VC of getting flashing across 4 quadrants of the monitor screen in Cockpit View. Then I had a BSOD with the above NVLDDMKM.sys error while going through the PMDG Tutorial at Coff's Harbour.So I uninstalled the 295 drivers and rolled back to the 285 drivers;that flashing ceased, same aircraft,same airport. Great I thought.Now, just when I least expected it, in the JS41 at VRMM(Male), just got to the engine starts, and all of a sudden, I get a BSOD with that error above.Event Log shows nothing.Has anyone else experienced issues with the 295 drivers or this NVLDDMKM.SYS causing a BSOD?

Possible solution here.Cheers,- jahman.

Possible solution here.Cheers,- jahman.

Thanks very much for that. Been checking on a 2nd comp while actually in the middle of a flight if anybody was able to come to my rescue. Oddly enough, just did a Windows 7 Update but did not take into account that it might have updated the Realtek drivers. So, your reply is appreciated.

You're welcome! Lets hope it fixes your CTD.Happy flying!Cheers,- jahman.

Don't quite know if these two are linked.Just purchased Warbird's P-51D Little Friends after reading the review here, as PC Aviator is offering it for today only at $17.97, which I reckon is a steal.In giving her a spin at the default Friday Harbor, have now had 2 BSOD with the previous NVLDDMKM.SYS error. Previously when I had this BSOD, I got rid of the 295 NVidia drivers and reverted to the 285, and everything, touch wood, has been running pretty ok, until this.Any ideas, anyone? Would be grateful. Not quite sure if it is Warbird linked or just a plain ole NVidia driver issue. Why on earth do these things plague WIndows7 and/or FSX? Makes one feel like jacking it all in and reverting to Train Simulator!

Since the newest driver is out, I am getting also odd NVLDDMKM driver crashes.The weirdest thing is, it neither crashes the game nor windows, it freezes the computer for about 30 seconds, then it comes back. And usually it never happens while gaming, but usually when in idle, like surfing or even not doing anything.My first though was something with power saving feature... only is happening since the last update of the GPU driver (two days ago), with the previous, haven't been seeing it for a long time, but I have been seeing it couple of months ago, with some other drivers. Seems like a nasty feature that is coming back again for some reason.

Thanks for your input,Srdan. I thought nobody was going to pick up on this.Weird thing is this actually all started after I'd installed the 295 drivers. All of sudden in no intense scenery, way out over an ocean at 36k, I get a BSOD. Fault is that NVLDDMKM.sys. So, I reverted to the 285 drivers. Flying any other aircraft, and I have been mainly flying the PMDG MD-11 of late, no problem. The minute I load the recently-bought Warbird's P-51D Mustang Little Friends, just to give it a spin around Friday Harbor just to check it out,wham, BSOD. Which is why I asked if there was any correlation between the two. Pity I did not retain the older but stable 275 driver. So, so frustrating to say the least.

Yeah, GPU driver issues can drive you crazy.I right now reverted to 295.73, which were working fine previously, so now we'll see.Sorry that I have virtually no solution for you.

Although the newer drivers are "supposed" to do a clean install - you might try getting a copy of the old 275.33 and do a complete uninstall followed by a driver cleaner in safe mode and then download and reinstall the 275.33's. JIC the new nvidia site is confusing, in the search box at the top of the page just put 275.33 and it will list the link.Vic

Ironically, tried that, just like Rick, and got the same lockup as with the new driver. It's like once you update to the new one, you can never revert. Argh.

Sorry that I have virtually no solution for you.

Thanks for your input, Srdan, Now, curiously, while looking elsewhere for a solution, and reading that it could could possibly be a Realtek LAN driver, that could be the cause of this BSOD, but not having a Realtek LAN, I searched further,and somebody suggested that maybe a GPU overclock could lead to this error. That got me thinking as I have indeed taken the core clock of my EVGA GTX 460 SE up to 800MHz, so I turned the wick down a bit, but as I have not tried it with that Warbird's P-51D Mustang 'Little Friends', I have no idea if this could be the solution.

Although the newer drivers are "supposed" to do a clean install - you might try getting a copy of the old 275.33 and do a complete uninstall followed by a driver cleaner in safe mode and then download and reinstall the 275.33's. JIC the new nvidia site is confusing, in the search box at the top of the page just put 275.33 and it will list the link.Vic

Thanks, Vic. Done precisely that, as you have recommended but with the 285 drivers. Don't have the 275.33 and don't know if I can get them retrospectively from NVidia

Rick - go to the NVidia site - upper right is a search box - put in 275.33 - you'll get the download link for them.Vic

Hmm, I just downclocked the card... and no more error. Let's wait couple of days.

Whoa, Srdan, that's two minds on the same track. As I'm right in the middle of a 737NGX flight from SBGR-SCEL, I will most probably give that Warbird's plane a spin tomorrow, and if no BSOD, then we're both on the right track. Fingers very much crossed.And thanks, Vic, for that HU re:275.33.

Update: again the lockup while waking my monitor, its set to 10min, my GF was just using it before I woke up. And it locked up for about 30 seconds, and then came the exclamation mark without any info, in Event Viewer:Display driver nvlddmkm stopped responding and has successfully recovered.The problem is not overclocking, as this was happening back when I still didn't OC the card, and was gone for the whole time as I did OC it, and now only after recent driver change it started happening again, now more often than before.