Sign in to follow this  
jeroenboxi11

FSX SE CTD on startup

Recommended Posts

I was operating a flight recently, when FSX decided to CTD. Ever since, I have not been able to startup FSX normally. The loading screen appears, I get a few errors about missing scenery (what I always have), and then I get a prompt telling me that FSX has stopped working. I have tried the following things:
- Reinstalling FSX in its entirety (also as an admin)
- Deleting the logbook
- Altering API.dll 
- Deleting all my addons (including aircraft, land textures and addon airports)
- Verifying the intergrity cache
- I have looked at my Scenery.cfg: only the default scenery is in there.....

Attached you will find the logs of me trying to startup FSX a few times!
I hope you can come up with a solution for this problem.......

With kind regards,

Jeroen

 

Link to logile:

http://puu.sh/o9u45/bf38a184d4.evtx

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

If you have a dll.xml and exe.xml (located in same folder as FSX-SE.cfg, move those files over to a temporary folder and restart FSX.  The dll.xml and exe.xml load at start of FSX/FSX-SE and, if a module is missing, corrupted, or the dll.xml is corrupt, the sim will not load.  Uninstalling scenery will not remove the dll.xml or exe.xml.  These files are not required by default.  They were added when you installed modules such as FSDT/Flightbeam airports and FSUIPC.

 

Best regards,

Share this post


Link to post
Share on other sites

If you are using Windows 10, then you might try searching for 'IgnoreFreeLibrary' entry in the registry as follows:

 

1) start regedit

2) goto key HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

3) delete the key "C:\\Games\\FSX\\fsx.exe"="$~ RUNASADMIN IgnoreFreeLibrary<dll name>"

4) if you would like to run FSX as an administrator you need to activate that again as you removed that in step 3

 

If it exists it means that freelibrary calls are ignored (calls used to unload a DLL, known as module in FSX). This probably means that one of those calls somehow failed once and the key was added by the MS compatibility 'service' as a service to you...

 

I found that when using Win10, if FSX has a CTD due to a DLL issue then a similar entry to above may have been written to the registry.

 

Stuart

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this