fatal error "FSX has stopped working" CTD

[MAHLER]

My windows 7 fsx rig occasionally comes up with this error, particularly on a lengthy flight, and invariably  when I either right click

or use the alt bar, anyone experienced or solved this issue.

Many Thanks

Mike                                           Intel i7-6700 4GHZ, Nvidia  GTX 1060. 1TB SSD

[charliearon]

Check out the very handy AVSIM CTD guide.  Also check your Events log on your computer to see what the "Faulting Module" is causing your error.

 

[Jude Bradley]

Sounds like that old chessnut uiautomationcore.dll  fix is needed.

 

[Jim Young]

Over the past 7 years, the uiautomationcore.dll has had varying results with members.  It definitely has not resulted in fixing all crashes for everyone.  I call it a placebo because I had a crash with FSX recently with Windows10 installed and just for kicks threw in the uiautomationcore.dll for Vista and it solved my crashes!  But later on, a week or two later, with the uiautomationcore.dll in my FSX folder, it crashed again.  I removed the dll.xml and the crashes stopped.  I then narrowed the crashes down to the module installed by Carenado, the cmeteoxml.dll.  It supposedly has something to do with their weather radar and is in conflict with ActiveSky or other weather programs.

If you have FSX-SE, the uiautomationcore.dll is installed by Dovetail so do not try to throw another version into an FSX-SE installation.

[MAHLER]

Thank you for your comments, have just installed the uiautomationcore.dll into my FSX root folder.

Will monitor and report on results.

 

[SteveW]

The uiautomationcore.dll is responsible for user interface automation as the name suggests. It takes care of tasks such as reporting the rectangle that the mouse hovers over, things like that. It's done as a process on top of other things.

When later versions of Windows came out after WinXP the uiatomationcore.dll shipping with those newer operating systems is slightly incompatible with FSX in a very few circumstances,

Since the reporting of locations in the simulator change depending on the screen resolution and the aircraft loaded and the types of equipment in the views and so on represents a very large number of situations all differing all the time. So pretty obviously it's not coming up all the time, maybe when we add a plane or make an adjustment we start to see it.

If we don't have the compatible version with FSX and the O/S then we may hit an issue when hovering the mouse over menus and the screen areas where hints pop up. The sim will crash to desktop showing a uiautomationcore.dll error.

The problem with Windows error reporting is that this can happen even when it's not an error in uiautomationcore.dll just like we see ntdll.dll errors and other CTDs all coming out of perfect modules - simply because these were doing something when an error outside their control happens dropping them in it.

So we have the confusion of the error not always present but will get you if you don't have the compatible dll.

So yes @Jim - you might see problems in uiautomationcore.dll EVEN when you have the compatible version - that's not caused by the dll that's the other guy's software - put your compatible uiautomationcore.dll back where it belongs and get on with troubleshooting the dodgy stuff.