I recently upgraded to a new computer thinking that I have a rig that can avoid the FSX "Fatal Error" notification. Unfortunately I was wrong. Here's my general specs on my new rig, a Dell Alienware Aurora:3.20 gigahertz Intel Core i7 96032 kilobyte primary memory cache1024 kilobyte secondary memory cache8192 kilobyte tertiary memory cache64-bit ready12280 Megabytes Usable Installed Memory - ATI Radeon HD 5800 Series [Display adapter] (2x)I thought it's a fairly acceptable rig for handling and running FSX. Whenever running some more than standard addon planes such as Eaglesoft's Citation X or the Citation Mustang, I encounter receiving the fatal error message, usually when switching views or adjusting the FMS in either plane. The fatal error doesn't show early in the flight, it usually occurs after flying over an hour or after 500+ miles, I'm usually flying at the normal simulation rate. My other standard addons when flying are MyTraffic, ASA, FSDiscover, FS Real Time, and some addon Airport Scenery. Is there anything that I can do to minimize the "fatal error" or have the gods yet to build a computer that can run FSX with addons such as mine without crashing?

I recently upgraded to a new computer thinking that I have a rig that can avoid the FSX "Fatal Error" notification. Unfortunately I was wrong. Here's my general specs on my new rig, a Dell Alienware Aurora:3.20 gigahertz Intel Core i7 96032 kilobyte primary memory cache1024 kilobyte secondary memory cache8192 kilobyte tertiary memory cache64-bit ready12280 Megabytes Usable Installed Memory - ATI Radeon HD 5800 Series [Display adapter] (2x)I thought it's a fairly acceptable rig for handling and running FSX. Whenever running some more than standard addon planes such as Eaglesoft's Citation X or the Citation Mustang, I encounter receiving the fatal error message, usually when switching views or adjusting the FMS in either plane. The fatal error doesn't show early in the flight, it usually occurs after flying over an hour or after 500+ miles, I'm usually flying at the normal simulation rate. My other standard addons when flying are MyTraffic, ASA, FSDiscover, FS Real Time, and some addon Airport Scenery. Is there anything that I can do to minimize the "fatal error" or have the gods yet to build a computer that can run FSX with addons such as mine without crashing?

It would be useful next time you get the "FSX fatal crash" to write down in which module (dll) this happened.Unless there is some hardware reliability issue, your rig should handle the load. OK, it will probably struggle to deliver nice frame rates everywhere, but "fatal error" as a result of "hardware not powerful enough" is not something you should accept.

Hello Tony:To answer your question, yes, there are countless "computer systems.....that can avoid FSX "Fatal Error". I would suspect that yours can avoid these crashes as well.I am not much of a Dell or current ATI fan, but I doubt seriously that your crashes are due to Dell or hardware at all. I would imagine that it is far more probable that it is a software or setup problem rather than hardware. The fact that you can fly the MSFS aircraft with no problem would be evidence of such a glitch. Up to date and stable drivers are another possibility, but being that you have no problem with the default aircraft I doubt that this is the problem.Forgive my ignorance, but a couple of questions:1. What and how much physical memory is installed?2. What do you mean by "64-bit ready? Is your operating system a 64bit version and if so which one? I personally still implement the Windows XP Pro 64 bit Operating System for FS. Assuming your computer is a new delivery I imagine it has one of the newer OS's. Possibly someone else will have suggestions relative to what to disable or enable in the system you have that may negate your problem. However, again I would think that the problem is elsewhere and related to an addon if you can fly defaults with no problem.My first suggestion would be to remove one of your addons, and try a flight where you have seen the problem. Do this one by one until hopefully you by a process of elimination can find the culprit and move on from there.IF, and I do mean if you have to reinstall, I would also make the following recommendation: After my initial default installation of any MSFS version, including any patches by Microsoft, I immediately make a backup and rename that installation without any modifications or addons. This has proven to be a lifesaver for trouble shooting where you can temporarily replace files or folders with the defaults to isolate and find a trouble spot.Good luck. I know how frustrated you must be, but hang in there. I would think that your computer would run FS quite well. RTH

I recently upgraded to a new computer thinking that I have a rig that can avoid the FSX "Fatal Error" notification. Unfortunately I was wrong. Here's my general specs on my new rig, a Dell Alienware Aurora:3.20 gigahertz Intel Core i7 96032 kilobyte primary memory cache1024 kilobyte secondary memory cache8192 kilobyte tertiary memory cache64-bit ready12280 Megabytes Usable Installed Memory - ATI Radeon HD 5800 Series [Display adapter] (2x)I thought it's a fairly acceptable rig for handling and running FSX. Whenever running some more than standard addon planes such as Eaglesoft's Citation X or the Citation Mustang, I encounter receiving the fatal error message, usually when switching views or adjusting the FMS in either plane. The fatal error doesn't show early in the flight, it usually occurs after flying over an hour or after 500+ miles, I'm usually flying at the normal simulation rate. My other standard addons when flying are MyTraffic, ASA, FSDiscover, FS Real Time, and some addon Airport Scenery. Is there anything that I can do to minimize the "fatal error" or have the gods yet to build a computer that can run FSX with addons such as mine without crashing?

Guys, thanks for the responses. To further clarify my system, it's a 64-bit Win7 OS. my total RAM is 12Gig, Belarc as it detailed as: 12280 Megabytes Usable Installed MemorySlot 'DIMM0' has 2048 MB (serial number AF7B182B)Slot 'DIMM1' has 2048 MB (serial number 357A182B)Slot 'DIMM2' has 2048 MB (serial number BE7B182B)Slot 'DIMM3' has 2048 MB (serial number CE7B182B)Slot 'DIMM4' has 2048 MB (serial number 907B182B)Slot 'DIMM5' has 2048 MB (serial number AC7B182B)Speedbird (or others), after the fatal error, were do I look to find in which module (dll) this happened? And if I find it, do I uninstall and reinstall the module?

Well, I finally solved my "Fatal Errors" after reading some posts on this forum and some other forums. The key was finding what was causing the fatal error. I've got a Win7 64 bit computer as identified in the early posts in this thread. The key is opening a Windows [i]Event Viewer[/i] which logs and identifies the application & module that is causing the fatal error. In my situation it was the Uiautomationcore.dll. Googgling that DLL I found a post that said in Windows7 64-bit, the DLL exists in the Windows\SysWOW64 folder and it does what it generally needs to do. FSX was developed in a 32 bit environment, when FSX loads it looks for the Uiautomationcore.dll and finds it in the WOW64 folder. However that DLL is the 64 bit version which works to a point and then gets overwhelmed because it's not the 32-bit Uiautomationcore.dll that FSX prefers. The post said do not touch the 64-bit DLL in the Windows\SysWOW64 folder as it may run other applications that you may have. I was instructed to download the 32-bit Uiautomationcore.dll which is something like 156KB, the 64-bit DLL is something like 750KB, and copy the 32-bit DLL into the Folder where FSX.exe resides. Now when FSX loads, it first looks in the FSX folder and finds the 32-bit Uiautomationcore.dll and is happy, it doesn't look further in the WOW64 folder.It works for me, the Uiautomationcore.dll was causing my problem. I recently flew from Darwin to Melbourne in excess of 1,700 miles in a CLS 767, with MyTraffic, FSDiscover, HiFi ASE, FS Real Time, FS WidgetsEFBSFX all running. In the past I may have gotten about 200miles before getting the dreaded "Fatal Error. Now, no fatal error and a completed flight.The fatal error for me was the Uiautomationcore.dll, if you have a Windows7 64-bit system, check the Event Viewer by entering that name in the bottom box (the start menu button on the far-left bottom of your computer). Find-out whats causing your fatal error. If it's not the Uiautomationcore.dll, what is it? The event viewer will tell you which module is causing the error, google-it and proceed to finding a solution if it's something other that the problem that I had.Tony