...UIAutomationcore.dll v6.0.5840.16386 is now back in my FSX+A folder and no more CTDs - hehe.

59 minutes ago, Jim Young said:

We host his official support forum here at AVSIM.

Glad a solution was found!  The DX10 forum has info on setting up multiple monitors for DX10.

 

Sorry Steve but I have a major problem with your explanation.  The Internet clearly states someone found the "holy grail" for fixing CTD's for FSX and that was a version of the uiautomationcore.dll.  The uiautomationcore.dll is part of the many different versions of the Microsoft.net packages.  Microsoft.net packages are used to make sure a program runs properly.  From my research, the two versions that many used for FSX, boxed version, were from earlier versions of Microsoft.net prior to the one originally installed with FSX in 2006 (Microsoft.net 1.1).  I know there is a problem with tooltips in the boxed version but the Microsoft.net versions placed in the main folder of FSX, boxed, supposedly had only one CTD fix - if someone right clicked on the panel and clicked on the menu at least 19 times, it would stop FSX from crashing (which I still cannot replicate).  I do not see how a uiautomationcore.dll coming from a completely different program than the FSX engine can fix FSX's tooltips.  I think Dovetail simply installed a slightly modified placebo...  It's strange Lockheed Martin P3D techs did not have to install this "placebo" in P3D (which is based on the FSX engine just like FSX-SE).  Lockheed just fixed the code.

Best regards,

Jim

 

So here's the error from Admin Evewnts:

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: uiautomationcore.dll, version: 7.2.14393.479, time stamp: 0x5825700e

Exception code: 0xc0000005

Fault offset: 0x00056ca7

Faulting process ID: 0x3020

Faulting application start time: 0x01d2be292ba19d49

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\WINDOWS\SYSTEM32\uiautomationcore.dll

Report ID: 6526711f-a76a-49ca-883b-888b2eeb3b34

Faulting package full name:

Faulting package-relative application ID:

 

 

So we can see from the log the faulting app and module is:

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\WINDOWS\SYSTEM32\uiautomationcore.dll

 

The upshot is that if we do not have the correcting dll in the FSX/FSX:SE folder we may get the CTD because it will utilise theC:\WINDOWS\SYSTEM32 version, which as I said FSX is not strictly compatible with. So we place the compatible dll into the FSX folder because FSX will find it first in its own folder. This only prevents this type of CTD Jim, it's not a fix all. But without this fix you could get the CTD at any time. Reason not all are affected is because not everyone does the same thing in the sim when they fly, some don't even use the mouse or screen for gauges or VC and so on.

13 hours ago, SteveW said:

The upshot is that if we do not have the correcting dll in the FSX/FSX:SE folder we may get the CTD because it will utilise theC:\WINDOWS\SYSTEM32 version, which as I said FSX is not strictly compatible with. So we place the compatible dll into the FSX folder because FSX will find it first in its own folder. This only prevents this type of CTD Jim, it's not a fix all. But without this fix you could get the CTD at any time. Reason not all are affected is because not everyone does the same thing in the sim when they fly, some don't even use the mouse or screen for gauges or VC and so on.

Respectfully, that version of the uiautomationcore.dll comes from Windows 10 and probably from KB3201845 Windows 10 Build 14393.479 released on December 16th, 2016.  It's probably telling you there is an add-on app that is not compatible with FSX.  Users of FSX or FSX-SE like to throw on those old addons they had for products developed for FS9 or FS2002.  FSX just happened to be the app running when the crash occurred.  It could even have been an outdated fsuipc.dll that would trigger the error.  Even a permissions issue would trigger the error. 

I find it interesting where the following topic was started on 31 Dec 2016 soon after the release of Windows 10 Build 14393.479.  A connections?

Best regards,

Jim

Edited April 26, 20179 yr by Jim Young
Forgot to add link

I've explained the problem clearly several times Jim for several years, and it's not a Win10 issue, http://www.codelegend.com/forums/viewtopic.php?f=2&t=588

8 minutes ago, SteveW said:

I've explained the problem clearly several times Jim for several years, and it's not a Win10 issue, http://www.codelegend.com/forums/viewtopic.php?f=2&t=588

Never said it was a Windows 10 issue.  Just might be a connection as Windows 10 had just been updated on 16 Dec and members were getting crashes with the uiautomationcore.dll, published with the update, as the faulting module.  You have to examine why you are getting uiautomationcore.dll errors with the Windows 10 version shown as the faulting module.  Placing the old versions in your main fsx folder certainly did not stop the crash(es) and you need to investigate which module, which fs add-on caused fsx to crash and throw the uiautomationcore.dll error.  It has nothing to do with any 2D panel.

Best regards,

Jim

Look more carefully at the logs for which version of UiAutomationcore.dll is reported in errors. Look at my error log I posted above shows it is the system version and not the compatible version caused the error. Huge confusion continues to dominate the UiAutomationcore/FSX issue. I've not seen the compatible versions of the dll showing up in any error reports.

Sory to repeat; by placing a compatible version of the UiAutomationcore.dll into the FSX folder does not stop any kind of CTD Jim. It only prevents the CTD from the menu/tooltip as I described earlier. Anyone can check that within a few minutes and confirmed on any Win7, 8 or 10 PC. If we don't put that dll in the FSX folder we are simply subject to the possibility of those CTDs depending on how we use the sim. The compatible version of the dll does not in itself contribute to any CTDs so it is always safe to use it, in fact it's a necessity and as such DTG place one in their FSX:SE folder so that FSX:SE avoids calling the system version. Any type of CTD can drop any current module in the drink, doesn't mean it's faulty, that can include UiAutomationcore.dll, ntdll.dll, and many others, can appear in an error log at any time when utilised incorrectly doesn't mean they are buggy. Even the incompatible UiAutomationcore.dll is not "buggy" it's just that the way some functions FSX calls of it changed in later versions of the dll, but FSX still operates in the way of the original FSX even DTG FSX.

There are many versions of the uiautomationcore.dll on your system, including the latest one that is part of Windows 10, that is shown as the faulting module.  The UI Automation Core API was introduced with Windows Vista (FSX was developed with Windows Vista) and Microsoft.net 3.0.  When FSX crashes (because of a configuration issue), Windows will throw the latest version of Microsoft.net as the faulting version.  Basically, it means you have a problem with your application.  May not be FSX.  Could be another add-on that is not compatible with FSX.  Microsoft Visual C++ modules (such as the MSVCR120.dll) will also throw an error on occasion when an application is incompatible or was not installed properly.  The recommendation of throwing in one of those older versions into your main FSX folder is not valid or substaniated by proof beyond doubt it stops an error from occurring.  

I have never had the old versions of the uiautomationcore.dll knowingly in the main folder of my fsx installation.  I did find that FSDT accidently placed an old version in the main FSX folder during the installation of their airports but the developer apologized and said he thought he had removed the module from the installation of his products.  He subsequently removed the uiautomationcore.dll module.  Since then I have never had a crash with FSX that could be fixed with placing an older version of the module in the main fsx folder.  I have tried unsuccessfully to replicate the menu crashes but have been unsuccessful.  Plain and simple, the old versions are placebo's and could create a conflict with the latest versions in the System32 and in the SysWoW64 folders.

When I see members posting CTD issues here at AVSIM, I see issues where they were flying and suddenly FSX crashed or froze.  They were not messing with the menu you get when you right click your mouse in FSX.

When you get a uiautomationcore.dll error, it means something in your application is not compatible.  That's how Microsoft set it up.  If there is a Microsoft.net error, it throws the uiautomationcore.dll error.  If it is a Microsoft Visual issue, it will throw the MSVCR***.dll error.  It all is used by developers to let them know whether they coded their product properly or not.  So one needs to find the incompatibility and that is done via the instructions I provided on Page 10, AVSIM CTD Guide, How to Fix Most CTD's/Freezes in FSX.

Best regards,

Jim

OK Jim, before I give up with you on this, can you at least try the test I showed you how to do?

 

...the test"rename the UiAutomationCore.dll you placed in the FSX folder to UiAutomationCore.dll.OK

Start a flight in DX10 choose a new time of day in the Alt menu, go to 2D panels view and start hovering the mouse to invoke the tooltip."

 

Should CTD in a few hovers over the tooltip areas. That's just one way to do it. "They were not messing with the menu you get when you right click your mouse in FSX." that's because they didn't need to be messing with the menu...

 

 

The tool tip error is a known issue with FSX and everyone was told to disable it or go into Windowed Mode.  I was looking at your test and you indicate I must have DX10 Preview on and go into the 2D panel (which I never use) while Tooltips is enabled.  I never got a crash.  No uiautomationcore.dll in my main fsx folder.

Jim

8 minutes ago, SteveW said:

go to 2D panels view

Who would be flying in DX10 Mode with the 2D Panel?  In addition, I was told by people like Kosta, a former member here and supposedly a computer guru, that it takes 19 times of opening the menu in the VC.  As I recall, he was never able to replicate it too.

In full screen there is the tooltip bug as you correctly mention, we are not discussing that. Instead you need to put your sim in windowed mode and hover over the tooltip areas after changing the time of day. Does not matter to the investigation if not many use the 2D panel since it's in use here as a good example of a way get the CTD in short time...

There are other ways for FSX to obtain a compatible dll if there are addons installing it. So failing that test it would be a good idea tohave a look at the modules loaded, see that it is "C:\WINDOWS\SYSTEM32\uiautomationcore.dll".

For example: Fredde shows his log with the correct configuration for uiautomationcore and so I would not look into that line of enquiry any further... "LoadedModule[147]=F:\Steam\steamapps\common\FSX\uiautomationcore.dll"