Well mine ain't broke so I guess I don't have to fix it then :Thinking:Makes sense that older progs like FSX don't profit a lot from these updates.Stay right where I am today, using the inspector as advised by Ryan, together with the internal frame limiter.Thanks everybody!Ype Reitsma

Thanks for the tip on the shader issue; I think that issue did present itself when I had fsx rebuild the cfg, but it was screwed up before (the opening screen was black instead of showing a 360 of aircraft, as was the whole screen if I tried to to fly). I'm already in the process of reinstalling, defragging, etc. My fsx install always showed an error msg when I exited anyway, which I suspect was related to something I did in FSPS frame booster, so I will stick to Bojote's tool instead. Ah, the folly over the obsession of squeezing out just a few more fps - I feel like the blonde archeologist in "Indiana Jones and the Last Crusade," reaching for the Grail, just a few more inches, I can get it...and then falling into the abyss.

I'm running an older system (4 years old) with the newest part being a GTS450 video card. The 290.53 driver has always been a little twitchy on my system. The 295.73 has been much more stable. My machine is setup using Inspector and Ryan's instructions. I will be upgrading my system when Ivy Bridge is released in a couple of months. :smile:Bill Bridges

Hi,This driver does not work for me. Here is the extract of my post on the nVidia forums.Hi,I have just upgraded from driver version 285.62 to 295.73 and I get the following error when running FSX. The error occurs as soon as the chosen situation has finnished loading the simulation data.Problem signature:Problem Event Name: APPCRASHApplication Name: fsx.exeApplication Version: 10.0.61637.0Application Timestamp: 46fadb14Fault Module Name: nvd3dum.dllFault Module Version: 8.17.12.9573Fault Module Timestamp: 4f34782eException Code: c0000005Exception Offset: 0050e0d8OS Version: 6.1.7601.2.1.0.256.1Locale ID: 2057Additional Information 1: 0a9eAdditional Information 2: 0a9e372d3b4ad19135b953a78882e789Additional Information 3: 0a9eAdditional Information 4: 0a9e372d3b4ad19135b953a78882e789Here is the System Information from the nVidia Control Panel - I am using 2 x Zotac GTX 580 AMP Edition cards configured for SLI surround gaming.[Display]Operating System: Windows 7 Ultimate, 64-bit (Service Pack 1)DirectX version: 11.0GPU processor: GeForce GTX 580Driver version: 285.62DirectX support: 11CUDA Cores: 512Core clock: 815 MHzShader clock: 1630 MHzMemory clock: 2050 MHz (4100 MHz data rate)Memory interface: 384-bitTotal available graphics memory: 4095 MBDedicated video memory: 1536 MB GDDR5System video memory: 0 MBShared system memory: 2559 MBVideo BIOS version: 70.10.17.00.01IRQ: 24Bus: PCI Express x16 Gen2GPU processor: GeForce GTX 580Driver version: 285.62DirectX support: 11CUDA Cores: 512Core clock: 815 MHzShader clock: 1630 MHzMemory clock: 2050 MHz (4100 MHz data rate)Memory interface: 384-bitTotal available graphics memory: 4095 MBDedicated video memory: 1536 MB GDDR5System video memory: 0 MBShared system memory: 2559 MBVideo BIOS version: 70.10.17.00.01IRQ: 30Bus: PCI Express x16 Gen2I have rolled my drivers back to 285.62 and FSX is running fine again but I would appreciate if anyone could assist with why I am getting the APPCRASH using 295.73.Regards,Ted.

Ted,Try this:1. Download and install Driver Sweeper:http://phyxion.net/i...er-sweeper.html2. Uninstall everything Nvidia related in your control panel (PhysX, 3D Vision, Nvidia Update etc - uninstall the actual driver last) You may need to reboot several times during this - let it do that, but cancel out of any attempt to install a default driver after the reboots.3. After the final uninstall has finished, reboot the computer in Safe Mode. (hit F8 right as Windows starts loading to get the menu that lets you do this)4. Once in Safe Mode, run Driver Sweeper. Select the Nvidia Display and Nvidia PhysX filters and press Clean. Reboot after it finishes.5. Install 295.73 again and this time do a custom/advanced install - uncheck all the extra bloatware garbage (3D Vision, PhysX, HD audio etc) that the driver tries to install by default unless you actually use one of these things (most people do not) and check the "Clean install" box. You want to install just the driver itself.6. Reboot after it finishes and use my stickied guide to set the driver up using Nvidia Inspector.If that doesn't work you've got something else corrupt going on in Windows or FSX.

Hmm

This driver runs well. Improved performance on all graphics hungry games. The FSX in particular improved by a couple of FPS + better graphics (played more with the Inspector).I jumped up from driver version 280.xx, so for me it is more obvious I guess.

Hi Ryan,Thank you for your assistance. I will try your recommendations when I get home from work.Regards,Ted.

Hi Ryan,Just tried again and it still crashes. X-Plane 10 works fine but MS Flight also errors as you can see here.Problem signature: Problem Event Name: APPCRASH Application Name: Flight.exe Application Version: 1.0.0.30016 Application Timestamp: 4f28a36a Fault Module Name: nvd3dum.dll Fault Module Version: 8.17.12.9573 Fault Module Timestamp: 4f34782e Exception Code: c0000005 Exception Offset: 0050e0d8 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 2057 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789It must be Windows then I guess. Way too much to rebuild, so I will stick with 285.62, as everything works with that.Thank you very much for trying to help me.Regards,Ted.

Ted,Very strange - not sure what to tell you there. Something with Windows or maybe the card itself then...

New drivers do basically nothing for FSX unless a new AA mode or something was added. Trust me, the video card companies aren't putting in optimizations for a 6 year old game...

Well said. If you're mainly running FSX or a bunch of older games, trying out new drivers isn't worth the hassle.The 295.73 release notes even state a known bug:"Flight Simulator X–pressing Alt+Tab to switch to the desktop does not work. [293729]"They seem to at least fire up FSX and try some basic things.

Edited March 5, 201214 yr by bpcw001

That's been in the release notes forever - it's an FSX problem that was never fixed by MS.

I tried the 295.73 set from release day until now and found I was getting random BSOD's in FSX. Before then I never had any BSOD's and since them it's been solid as well.

Allways use ALT/ENTER. Never ALT/TAB.

I had the black screen problem but a second run of the installer seems to have fixed it. Incidentally, with these drivers, I no longer get the "hang" or black screen when trying to switch from fullscreen to windowed mode. It switched back and forth just fine.I updated because I broke down and bought ME3 today... I'm putting down my paintbrush for a few days to save Earth.