Hello, since yesterday I have been getting this error after around 10 minutes of playing fsx, it's really annoying especially on long missions/flights.Error name:FSX Has encountered a fatal error and will now restart (Or somewhere around those lines)Error report: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: uiautomationcore.dll Fault Module Version: 7.0.0.0 Fault Module Timestamp: 4a5bdb1d Exception Code: c0000005 Exception Offset: 0000e52a OS Version: 6.1.7600.2.0.0.768.3 Locale ID: 2057I will really appreciate if I could have any help.- Badboi797

See here.Cheers,- jahman.

I've put the file in the FSX folder and it's working like a charm, thanks.

You're welcome!Cheers,- jahman.

"I've put the file in the FSX folder and it's working like a charm, thanks."Wow! I've never seen that 'fix' work. I doubt it will last for long. The uiautomationcore.dll is installed with the Microsoft.net program. Exception code c0000005 indicates the system had a memory exception error that occurred when uiautomationcore.dll was being called by the system. It will happen again. The OP should update his/her's MS Visual's from 2005 to 2010 and Microsoft.net. Glad you were able to get a temporary fix.Best regards,Jim

The uiautomationcore.dll is installed with the Microsoft.net program.

When loading a resource like a dll, Windows will first look in the directory the main executable was loaded from. If the resource is not found in that directory, Windows will look to the "path" environment variable and search those locations next.This means if you add UIAutamotionCore.dll to your FSX directory, then Windows will indeed use that dll rather than the version in the Windows system directories.Cheers,- jahman.

means if you add UIAutamotionCore.dll to your FSX directory, then Windows will indeed use that dll rather than the version in the Windows system directories.

Yes, jahman, understand that concept. In fact, sometime last year when I was getting those dreaded ntdll.dll errors, I dropped uiautomationcore.dll into my main fsx directory as it was supposedly fixing the problem for several others. Didn't fix anything. I still got the crashes. So, I went and adjusted my memory settings in the BIOS and the crashes stopped. Most of the crashes posted here are memory related. You'll see the Exception code: c0000005 or MEMORY_ACCESS_VIOLATION on nearly every crash report. It's a common problem throughout the computer world. The fault module or .dll that caused the crash is not the reason for the crash (unless it is corrupted). It just happened to be the file that was being loaded when the memory access violation occurred. Since uiautomationcore.dll is part of the Microsoft.net program and used by developers of FSX addons, FSX, and Acceleration for programming, it is imperative, that this software be installed correctly and is always kept up-to-date. MSV's 2005-2010 are also used by addon developers and they will install the appropriate MS Visual required for their addon. As you know, the Microsoft.net program also manages memory of the software programs developed for FSX and FSX. It could be something as simple as the individual has UAC turned on and the program is not allowing a module to be loaded and subsequently you get the MEMORY_ACCESS_VIOLATION. Or it could be more technical and the memory settings in the BIOS do not have the correct frequency or voltages for the installed memory. That's what happened to me. So, in the end, we both may be right but I wanted to be sure the OP was aware there could be other issues with his system.Best regards,Jim

"I've put the file in the FSX folder and it's working like a charm, thanks."Wow! I've never seen that 'fix' work. I doubt it will last for long. The uiautomationcore.dll is installed with the Microsoft.net program. Exception code c0000005 indicates the system had a memory exception error that occurred when uiautomationcore.dll was being called by the system. It will happen again. The OP should update his/her's MS Visual's from 2005 to 2010 and Microsoft.net. Glad you were able to get a temporary fix.Best regards,Jim

Jim,"MS Visual's from 2005 to 2010 and Microsoft.net"Where are these updates? I'm getting regular atc.dll crashes with the code c0000005.Thanks.

Where are these updates? I'm getting regular atc.dll crashes with the code c0000005.

Use Windows Update to make sure you have the latest installed. If you do not have MSV's from 2005 to 2010 installed (check your Add/Remove Program and look for Microsoft Visual's Redistributables) you can download the one(s) missing from the following site - http://www.microsoft.com/download/en/details.aspx?id=5555 (this is the the 2010 package but there are links to other packages). The ATC.dll is also dependent upon MSVCR80.dll which is part of Microsoft Visuals C++ 2005 - see here http://support.microsoft.com/kb/326922 so that indicates to me you're missing something from the 2005 or 2008 Redistributable. The ATC.dll is also dependent upon 3 other modules - user32.dll, kernel32.dll, and util.dll. Util.dll is part of the Microsoft.net Framework. If updating and/or making sure you have the MSV's from 2005-2010 does not fix the problem, then I would check your fsx sliders and reduce them or bring them back to the default and see if that fixes the problem. Lastly, if that doesn't work, then check the configuration of your memory in the system bios. Best regards,Jim

Use Windows Update to make sure you have the latest installed. If you do not have MSV's from 2005 to 2010 installed (check your Add/Remove Program and look for Microsoft Visual's Redistributables) you can download the one(s) missing from the following site - http://www.microsoft...ls.aspx?id=5555 (this is the the 2010 package but there are links to other packages). The ATC.dll is also dependent upon MSVCR80.dll which is part of Microsoft Visuals C++ 2005 - see here http://support.microsoft.com/kb/326922 so that indicates to me you're missing something from the 2005 or 2008 Redistributable. The ATC.dll is also dependent upon 3 other modules - user32.dll, kernel32.dll, and util.dll. Util.dll is part of the Microsoft.net Framework. If updating and/or making sure you have the MSV's from 2005-2010 does not fix the problem, then I would check your fsx sliders and reduce them or bring them back to the default and see if that fixes the problem. Lastly, if that doesn't work, then check the configuration of your memory in the system bios.Best regards,Jim

Thanks Jim.I misunderstood you. Both my ms visual c++ and net frasmework are all there and up to date.I've run both Prime95 and Intel Burn test test for long periods of time with no problem.With respect to my memory settings, I had them set to manufacturers specs (1600mhz and 8-8-8-24 for the timings), but someone in another forum told me that with Sandy Bridge you set all memory settings to auto, which result in 1333mzh and 9-9-9-24 for the timings. Didn't help by the way anymore than another's advice who thought my problem must be related to my clock which I've reduced from 4.4 to 4.0 with no improvement.A curious thing though is that CPUID shows my Dram frequency to be 668 mzh while the bios shows it at 1333mzh. Any ideas on this one.Thanks for your help. This is frustrating.Dan Cole

With respect to my memory settings, I had them set to manufacturers specs (1600mhz and 8-8-8-24 for the timings), but someone in another forum told me that with Sandy Bridge you set all memory settings to auto, which result in 1333mzh and 9-9-9-24 for the timings. Didn't help by the way anymore than another's advice who thought my problem must be related to my clock which I've reduced from 4.4 to 4.0 with no improvement.

With due respect to the someone from the other forum, setting the frequency to auto is not a very good idea as I read on an ASUS forum that ASUS motherboards have a very difficult time figuring out memory settings when they are set to auto. I had mine at auto and got a couple of crashes then discovered I needed to set them manually after reading about the ASUS problems. Your Dram frequency is at 668 because your have your frequency set at 1333 Mhz with a 9-9-9-24 primary timing settings (look at your BIOS Advanced Mode Ai TweakerDRAM Timing Control). That's a correct setting. However, you can go to a 1600 MHz frequency IF you set your Ai Overclock Tuner to X.M.P. Then you will have a profile of X.M.P. DDR3-1600-6-8-6-24 with a 1.65 voltage. You can only do this with the Overclock Tuner set to X.M.P. Look at your CPU-Z SPD Tab and you'll see what I'm talking about. Look at the far right column under Timing Table and it will show you the proper settings you should have set in the bios. So, in the BIOS, on the AI Tweaker page, you would have:Ai Overclock Tuner X.M.P.BCLK/PCIE Frequency 100.0Turbo Ratio By All CoresBy All Cores 44Internal PLL Overvoltage EnabledMemory Frequency DDR3-1600MHzEPU Power Saving Mode DisabledGoing down lower on the same page make sureCPU Voltage is set at Manual ModeCPU Manual Voltage 1.440DRAM Voltage 1.65000 (this is the voltage you'll see in the CPU-Z under the SPD tab for X.M.P 1600). If this is set higher you could have problems.Everything else on this page is set to Auto.I'm out of possible solutions to your problem. If changing your frequency to DDR3-1600 MHz does not work, then I'm at a loss. However ATC.dll is tied to other files that manage your memory so this is a good place to look at. Hope this helps.Best regards,Jim

With due respect to the someone from the other forum, setting the frequency to auto is not a very good idea as I read on an ASUS forum that ASUS motherboards have a very difficult time figuring out memory settings when they are set to auto. I had mine at auto and got a couple of crashes then discovered I needed to set them manually after reading about the ASUS problems. Your Dram frequency is at 668 because your have your frequency set at 1333 Mhz with a 9-9-9-24 primary timing settings (look at your BIOS Advanced Mode Ai TweakerDRAM Timing Control). That's a correct setting. However, you can go to a 1600 MHz frequency IF you set your Ai Overclock Tuner to X.M.P. Then you will have a profile of X.M.P. DDR3-1600-6-8-6-24 with a 1.65 voltage. You can only do this with the Overclock Tuner set to X.M.P. Look at your CPU-Z SPD Tab and you'll see what I'm talking about. Look at the far right column under Timing Table and it will show you the proper settings you should have set in the bios. So, in the BIOS, on the AI Tweaker page, you would have:Ai Overclock Tuner X.M.P.BCLK/PCIE Frequency 100.0Turbo Ratio By All CoresBy All Cores 44Internal PLL Overvoltage EnabledMemory Frequency DDR3-1600MHzEPU Power Saving Mode DisabledGoing down lower on the same page make sureCPU Voltage is set at Manual ModeCPU Manual Voltage 1.440DRAM Voltage 1.65000 (this is the voltage you'll see in the CPU-Z under the SPD tab for X.M.P 1600). If this is set higher you could have problems.Everything else on this page is set to Auto.I'm out of possible solutions to your problem. If changing your frequency to DDR3-1600 MHz does not work, then I'm at a loss. However ATC.dll is tied to other files that manage your memory so this is a good place to look at. Hope this helps.Best regards,Jim

Couldn't ask for more. Thanks Jim, BTW when I moved my FSX to a dedicated SSD (which is about the time the issue began), I didn't set the VM on that drive to system managed. I just did and it seems to help.Thanks for all.Dan

I didn't set the VM on that drive to system managed.

I have that setting too and frequently recommend a change to 'system managed size'. I never have had success with making my own VM settings and have had frequent crashes until I changed back to system managed. Hope this works for you too.Best regards,Jim