Good day,

 

I have been having the dreaded 'FSX Fatal Error' problem for the past few weeks, I have spent hours searching the internet, reinstalling, testing and raging trying to fix this.

 

What I am running:

FSX + FSX Acceleration

FSInn + FSCopilot (though even with/without it running, the game crashes)

FTX Australia + YMML (even with it disabled, I get crashes)

 

What I have done so far:

-Installed FSX to location other than Programs (x86)

-Tried uiautomationcore.dll fixes in FSX directory

-Taken ownership of uiautomationcore.dll 's in windows directories

-Disabled UAC

-Tried many FSX.cfg tweak programs, as well as deleting it and letting FSX re-create it.

-Ran FSX in incompatibility mode for Win7, Win XP SP3

 

None of these have fixed the problem.

 

My System Specs:

Win 7 Pro 64bit

ATI HD 5850 G-card (with updated drivers)

Intel Core i7 930

4gb of DDR3 RAM

 

As well as CH Pro Pedals and a Saitek Pro Flight Yoke

 

Help would be VERY much appreciated, I have been pulling my hair out over this problem!

 

Thanks,

Mitchell W

Could you give us more information on the crash itself?

Is there an error report when you get the CTD?

We need that information to help you further.

Best of luck

Welcome to the club. Worst program ever designed for a computer, fsx that is. Spend $3000 and it still sucks. I have just spent 2 hrs myself trying to fly and the controls were screwed up. I am so f***ing p*ssed right now. All I want is to practice piloting and no other program simulates this as well as fsx, but it is such a pain in the butt. :angry: :angry: :angry: :angry: :angry:

Log Name:	 Application
Source:	 Application Error
Date:		 24/11/2012 12:08:28 PM
Event ID:	 1000
Task Category: (100)
Level:		 Error
Keywords:	 Classic
User:		 N/A
Computer:	 *****-PC
Description:
Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x1f5c
Faulting application start time: 0x01cdc9db8c7327fa
Faulting application path: G:\Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: unknown
Report Id: 73fe08aa-35d3-11e2-bbdc-005056c00008

 

This time, I managed to get into a short flight without a crash, I swapped aircraft and joined VATSIM using FSinn and crashed shortly after when accessing the right click menu to change views.

Very little info to go on there unfortunately seems as if it’s a access violation code. Could be form .cab or .dll files I’m not sure

 

This may seem bizarre question but do a search on your pc and see do you have an application called “go sync” I believe its either an apple or yahoo programme which may be a problem even though it has nothing to do with FSX.It caused trouble for me before

The search resulted in nothing, damn, why did Microsoft make it such a pain in the &@($* :(

You may want to try this and if it doesn't work it won't hurt anything. The information "Exception code: 0xc0000005" means there is a memory error(out of memory) of some type. I used the Fixit help rather than messing with my registry (It's just easier) at the following Microsoft url and it worked for me but no guarantee this will solve it for you. The link is http://support.microsoft.com/kb/947246.

 

This is link to where I had the same problem with respect to the error. http://forum.avsim.net/topic/387438-ctd-help-please-four-crashes/#entry2489031

 

Good luck

My guess is that it is FSInn and/or CoPilot causing your problems. They are not always compatible and this is a known issue. You need to go to the FSInn and/or CoPilot and read a 'sticky' in the forums on the proper installation of these programs to avoid crashes.

 

Best regards,

Jim

I am at my wits end with this error. No matter what plane, location, addons running or anything the error still comes up.

 

Default 737-800 - Fatal Error about half way through flight

Default 737-800 - Used menu ALOT, fatal error before taxiing.

 

I installed FSUIPC, did the memfix, as well as everything else in the original post.

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: uiautomationcore.dll, version: 6.0.6001.18000, time stamp: 0x4791a76f
Exception code: 0xc0000005
Fault offset: 0x0001dd8f
Faulting process id: 0x1b84
Faulting application start time: 0x01cdda58ee22a675
Faulting application path: G:\Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: G:\Games\Microsoft Flight Simulator X\uiautomationcore.dll
Report Id: 049c1856-4650-11e2-8f42-00241dce5617

I am at my wits end with this error. No matter what plane, location, addons running or anything the error still comes up.

 

Default 737-800 - Fatal Error about half way through flight

Default 737-800 - Used menu ALOT, fatal error before taxiing.

 

I installed FSUIPC, did the memfix, as well as everything else in the original post.

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: uiautomationcore.dll, version: 6.0.6001.18000, time stamp: 0x4791a76f
Exception code: 0xc0000005
Fault offset: 0x0001dd8f
Faulting process id: 0x1b84
Faulting application start time: 0x01cdda58ee22a675
Faulting application path: G:\Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: G:\Games\Microsoft Flight Simulator X\uiautomationcore.dll
Report Id: 049c1856-4650-11e2-8f42-00241dce5617

 

You have wrong version of uiautomationcore.dll, go and download 6.0.5840.16386 here: http://api.viglink.com/api/click?format=go&key=cdee124b11d6baacda6c3e29b12e23dc&loc=http%3A%2F%2F#####.wordpress.com%2Ffsx-software-and-hardware-guide%2F&v=1&libid=1355534511721&out=https%3A%2F%2Fdl.dropbox.com%2Fu%2F31158446%2FBlog%2FUIAutomationCore.rar&title=FSX%2FP3D%20Software%20and%20Hardware%20Guide%20%7C%20Kosta's%20Flight%20Simulation%20World&txt=Link%20to%20the%20file&jsonp=vglnk_jsonp_13555346002048

Didn't help, back to this error when using a menu after ~20 times:

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x198
Faulting application start time: 0x01cdda636d189081
Faulting application path: G:\Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: unknown
Report Id: 9be279b2-4658-11e2-8f42-00241dce5617

 

Error Report: http://dl.dropbox.com/u/27424880/Report.txt

Remove the uiautomationcore.dll. It is not working for you. Your problem is with FSInn and CoPilot. There's a setting in FSInn you have to make to make them compatible. Check with the developers. This is a common crash.

 

Best regards,

Jim

Is there a link anyone could point me towards or tell me which setting I have to change?

 

Thanks

Same issues here. Read some older posts regarding this. Is it as simple as removing "uiautomationcore.dll"?

Same issues here. Read some older posts regarding this. Is it as simple as removing "uiautomationcore.dll"?

 

So, you are still receiving a ctd even with uiautomationcore.dll installed in the main FSX directory? If you are, then the dll is not working for you or fixing your problem so you should remove it. Do you have fsinn/fscopilot installed? There have been some known issues with this software combination but a lot of those problems have been fixed or the software appears to be more compatible now with FSX. Another common problem is the proper installation of simconnect. What happens when an issue with simconnect occurs? FSX will freeze up momentarily or crash and there will usually be no faulting module indicated in the crash report. If you have AS2012 installed, then you need to check and make sure simconnect is properly set up for FSX. Same goes with REX, OPUS, or any other weather program that has to communicate with the Internet. Simconnect may work w/o any problems with programs like PMDG or the default weather program but that does not mean it is properly configured to work with other weather programs or software. You should provide us with a copy of your crash report by downloading AppCrash - http://www.nirsoft.net/utils/app_crash_view.html and pasting the crash report to this post. This is something that wasn't done for the OP and we might have solved his CTD (but since he did not respond to my last post, maybe the problem was fixed).

 

Best regards,

Jim