Hello,

I am running FSX (disk edition) on W10 64bit. When flying the PMDG JS41 (i don't think my problem is related to this aircraft), FSX crashes suddenly in midair ans FSX restarts thereafter. I noticed that this happens always after too many clicks (view-change in FSX, etc...).

The problem happens despite having installed UIAutomationCore.dll (Version 16386)

fsx.exe

10.0.61637.0

46fadb14

uiautomationcore.dll

6.0.5840.16386

45398e5f

c0000005

0001dd8d

cb0

01d4441882857744

 

Do I need to install an older version of uiautomationcore.dll? And if so, which one and where can I find it?

Thanks in advance!

Welcome to the AVSIM forums.  I have moved your post into the CTD forum.  This would be a good starting place to explore the options to fix your problem.  Supposedly this is the Vista version of that .dll.   http://www.search-dll.com/dll-files/download/uiautomationcore.dll.html

 

I do not recommend installing the uiautomationcore.dll in the main folder of FSX but, if you really want to do it, then the version you placed in your FSX directory is the best one.  The uiautomationcore.dll is not the holy grail of fixing crashes in FSX but it might help in certain circumstances.  I went several years without it installed in my main FSX directory but had some issues after I upgraded to Windows 10.  The uiautomationcore.dll is part of Microsoft.net packages.  If you get a crash at startup, this means you might need the uiautomationcore.dll.  If it starts up to the scenerio and you take off and go flying and the sim crashes, then it is something else that is causing your issue.  

The error message you received above indicates you have an add-on that is not compatible with FSX.  I would suggest renaming your FSX.cfg to FSX.off, your dll.xml to dll.off, and scenery.cfg to scenery.off.  One of the components in those three files is causing your crashes.  The fsx.cfg and scenery.cfg will be rebuilt to the default.  The dll.xml will not be rebuilt but you probably don't need any of those modules it is loading anyway.  You can also just rename the FSX.cfg first, go fly and see if this fixes the problem.  If not, then rename the dll.xml and go fly and see if this fixes the problem.  If not, then rename the scenery.cfg and see if this fixes the problem (it should).  If the issue is with the scenery.cfg, then you will have to disable 2-3 sceneries at a time until the corrupted scenery causing the problem is found.  The AVSIM CTD Guide, page 10 shows you how to do this and the folders to go to to disable these files.