After reinstalling FSX and a few add-ons, i did get this CTD immediately after FSX had started. Via Google i found the hint to run a reg cleaner, but that doesn't make really sense and it didn't help in my case. New drivers and a fresh FSX.cfg didn't help either.Then i did deactivate the preloading of scenery via the FSX.cfg ((DisablePreload=1). After that, FSX wasn't crashing immediately after its start.Now FSX did crash when i loaded a flight, so it was obvious that scenery files or textures caused the problem.I have a backup of a virgin FSX+XPack installation and i did copy the origianl FSX\texture folder in my new installation and that did solve my problem.I'm not sure if the textures had become corrupt or if it was a permission related problem because i had used textures from my previous FSX installation which i had saved before i made the reinstallation. I hope this helps other people who experience the same problem, even if the source might be different (different textures or scenery files).

After reinstalling FSX and a few add-ons, i did get this CTD immediately after FSX had started. Via Google i found the hint to run a reg cleaner, but that doesn't make really sense and it didn't help in my case. New drivers and a fresh FSX.cfg didn't help either.Then i did deactivate the preloading of scenery via the FSX.cfg ((DisablePreload=1). After that, FSX wasn't crashing immediately after its start.Now FSX did crash when i loaded a flight, so it was obvious that scenery files or textures caused the problem.I have a backup of a virgin FSX+XPack installation and i did copy the origianl FSX\texture folder in my new installation and that did solve my problem.I'm not sure if the textures had become corrupt or if it was a permission related problem because i had used textures from my previous FSX installation which i had saved before i made the reinstallation. I hope this helps other people who experience the same problem, even if the source might be different (different textures or scenery files).

Unfortunately, not many people backup a "virgin FSX+XPack" installation. It's strange to me that you reinstalled FSX and immediately had the CTD yet, when you copied the virgin files over, FSX worked. VisualFX.dll was upgraded in SP1 or SP2/Acceleration. It's possible you still had the old visualfx.dll installed and it wasn't upgraded when you installed XPack for some reason. When you copied the virgin FSX/XPack files over, you probably upgraded the file and now it's working. I think another issue that causes bad installations is the fact that the latest MS Visual C++ Redistributables are not installed or were not updated to the latest. NickN recommends this in his article on setting up FSX and tuning it. The DOTNET program (Version 4 for Windows 7) has to be installed too but that is included in Windows 7 installs and updated regularly through the Windows Update program (Vista and XP users will have to download and install it). Software makers, including Microsoft and addon developers for FSX, use these programs to make sure their programs/executables are properly installed.Thanks for the info. I hope it solves a problem for other FSX users.Best regards,Jim

Hi Jim, i didn't replace the visualfx.dll and the clean installation did run fine.I only made what i wrote. Nothing more. I always make a backup copy from a clean installation to be able to replace single files.A simple way to not lose all customizations, if a single file is replaced by an older or corrupted file. This happens quite frequently, when you install add-ons via installers.

Hi Jim, i didn't replace the visualfx.dll and the clean installation did run fine.I only made what i wrote. Nothing more. I always make a backup copy from a clean installation to be able to replace single files.A simple way to not lose all customizations, if a single file is replaced by an older or corrupted file. This happens quite frequently, when you install add-ons via installers.

I do exactly what you do, backup a clean install. It has saved me a couple of times from having to do a repair or reinstall FSX. If you have the space it's a great idea!Best regards,Jim