There is a funny little pest that has been causing problems for some FSX users and I thought it was time to write about it and how to repair the issues it creates. I’m going to go on the record here and say like many other FSX tweaks you (the user) shouldn’t really mess around with system files unless you absolutely have to. Being a veteran of FSX I have built/rebuilt and flown many simulators and there are times where I’ve not needed to make any tweaks and then there are times where I have.
A few year ago when I rebuilt my simulator with an AMD AM3+ I found that I didn’t have to touch the UIAutomationCore.dll which, default is installed in the C:\WINDOWS\System32 or C:\WINDOWS\SysWOW64 directories for 32 and64 bit respectfully by default no matter where you install the FSX program, it will always be installed in that location Why? It’s not a core FSX file, it’s a Windows OS Core File.
Before we go any further let me try to explain (how I understand) the issues surrounding this pesky file, each time FSX crashes in relation to UIAutomationCore.dll they unfortunately mean different things to different people. I appreciate that’s a vague statement to make, but it’s a fact. Some people seem to suffer the crashes when clicking on various menus (common), and for others, It’s just other related issues. Unfortunately as I mentioned in a previous posting, FSX was released way before it was finished, which causes plenty of other CTD scenarios…
However if you do happen to be one of the unlucky ones to suffer from UIAutomationCore problems, then you are in fact lucky… I’d bet that mostly it happens when you click on a FSX menu. To overcome this particular demon you have a couple of options of solution to try:
Option 1 – Download one of the many replacement UIAutomationCore.dll files and place it directly into the FSX root, a quick google search should help you find the appropriate file.
Option 2 – This is one I’ve seen posted on various forums around the internet but I can’t work this out – anyway here goes. Basically the general idea of UIAutomationCore.dll files are evil and uneccessary and shouldn’t even be on the system – in fact they have been said to of been a throwback from Windows Vista and Server 2008 as part of the MSAA framework. Apparently FSX does not require the file and shouldn’t be there.
Option 3 – Download a specific UIAutomationCore.dll for a 64bit system and place it into the FSX root directory, incidentally I’ve never heard of a 64bit version of UIAutomationCore.dll
Generally anytime FSX crashes, and it often does following re-setup or installations. The best advice I can give is to firstly take note of the time and then head to the Event Viewer (found in Administrative Tools in the control panel in windows 7) or click ‘start’ and type ‘Event Viewer’ and then click on the Windows logs and then Application group, there will be a lot of entries (which is wh I said take note of the time of the crash) and also look at for a red circle with a white exclamation mark with the word ‘ERROR’ below is an example of the error log.
Problem Event Name: APPCRASH
Application Name: fsx.exe
Application Version: 10.0.61472.0
Application Timestamp: 475e17d3
Fault Module Name: uiautomationcore.dll
Fault Module Version: 126.96.36.199
Fault Module Timestamp: 4a5bdb1d
Exception Code: c0000005
Exception Offset: 0000e52a
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Not all crashes and errors are created equal
The golden rule in troubleshooting on such a diverse operating system as Windows, no error or crashes are the same, just because a solution worked for one person doesn’t mean it will work for you. So my advice is to back up BEFORE you make any changes to ANY file system. And research, remember you may have to try a few ‘fixes’ before you find or indeed stumble on the right one for you… Also it’s worth a shot to remember (especially on older systems) that crashes can be a result of ‘overstretched’ hardware or failing components. Keep a listen out to Hard Drives especially as the noises they make can very often mean the difference between a failing drive with chance of retrieving the data or total loss..