Hi all,Any idea what happened here? FSX fatal-error just after the middle marker after a 4,5 hour flight :-(Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: PMDG_MD11.DLL, version: 10.0.61355.62, time stamp: 0x49b7c81dException code: 0xc0000005Fault offset: 0x000b4901Faulting process id: 0xbf8Faulting application start time: 0x01cb84e7e1fa7b00Faulting application path: D:\Program FIles (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exeFaulting module path: D:\Program FIles (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_MD11.DLLReport Id: 7dce7270-f0db-11df-8a1f-00044b194b82I have no clue how to decipher this... any help would be appreciated!Thanks!

FSX was shut down due to an error that occurred in the PMDG_MD11 module loaded from the FSX/Gauges directory.Either there was an error in the PMDG_MD11 code itself (a bug), or more likely given FSX was running a for a long time befor CTDing, the PMDG_MD11 or another module within FSX (or potentially another entirely different module, program or service) has a memory leak (continues to request memory from the operating system without releasing memory it no longer needs) thus causing memory exhaustion, such that when the PMDG_MD11 module makes a memory request of it's own, the operating system can't fulfill that request and shuts down FSX. Recall that FSX is a 32-bit app, so it exhausts available memory when total FSX and system memory reaches 4 GBy, even though your PC may have far more than 4 GBy installed memory.Candidates for memory leaks are other Add-Ons such as AI Traffic engines, weather engines, or even non-simming programs or services running at the same time as FSX.Another tack if you are running FSX under the 64-bit version of Win 7 and the crash happened exactly as you pulled-down the top menu bar or right-clicked on the screen: That would be the UIAUTOMATIONCORE.DLL bug (there is a tutorial available on this forum).That's as far as my knowledge goes (should know more by now given the number of crashes I'm having! ;-). Hope others can chime in and expand.Cheers,. jahman.

Hi Jahman,Thanks for the reply.. I am running Win 7/64 with 8Gb of RAM. I wouldn't know what to do to prevent memory from leaking.. I am running REX2 and UT2, so those could be adding to the problem. I will wait and see if anyone else responds and see what they can come up with. Otherwise I will uninstall UT2 and see what happens then.

> Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Crash in FSX Acceleration> Faulting module name: PMDG_MD11.DLL, version: 10.0.61355.62, time stamp: 0x49b7c81dCrash occured while executing code inside PMDG_MD11.DLL> Exception code: 0xc0000005Access violation (usually trying to read/write data from/to a memory location where no memory is allocated for FSX)> Fault offset: 0x000b4901The instruction at offset 0xb4901 in the DLL caused the access violationI know, that doesn't help.Like the other poster said, while the crash happened in the pmdg dll, eventually it was FSX who was calling that dll, so it could be that FSX was passing along wrong data/memory pointers to the DLL. There is not much you can do about that, but it indeed could be caused by a memory/resource problem. Are you use the 'HIGHMEMFIX' ?Daniel

"Standard technique" to identify the ofending add-on is to either uninstall one add-on at a time and track when you no longer get the CTD, or uninstall all add-ons and re-install one at a time and again note the point at which the CTD recurs. Of course the more predictable/repeatable the point in your flight at which the CTD occurs, the easier it will be for you to figure out which add-on is responsible.Sometimes with FSX and the many add-ons the choice seems to be whether to spend your time flying or debugging your system :-) In your case, given what seems to be a sporadic CTD after 4.5 hours of flight, my sugggestion would be to reload the flight from the last auto-saved point (I use FSUIPC) and continue flying and get the most sim hours you can enjoy until the release of MS Flight :-DIf you do decide to go the long route and identify the faulty add-on, please report back with your findings (Kind souls willing to set-up a database of faulty add-on versions and bug reported, please take note! When experiencing CTDs, it would be of great benefit to the FS community to quickly be able to check installed add-ons against the list of reported add-ons with bugs.)Cheers,- jahman.

I'm only using UT2, REX Ultimate and the PMDG MD-11. Oh and a few airports.. but that's all.Its pretty much a clean install. I have reduced the AI aircraft in UT2 from 100 to 15 percent and will test (when I have some time). If that seems to do the trick I will screw up slowly and test and stop at around 30 percent (100 was way too irritating to deal with anyways).Thanks again for the help. Will keep you informed.

I'm at wits end.. I've adjusted UT2 all the way down to 10%, airports are completely empty and there is the occasional radio transmission to AI traffic from ATC. Programmed a flight from KORD to KJFK and again within 20 minutes after take-off a full system freeze. This time the computer just became totally unresponsive, the picture didn't distort or anything, just froze in place. The last thing I did was press shift+z to see what the frame rates were doing and that was it... I don't know what to do anymore, any advise would be welcome.Last thing I can think of is to uninstall everything and start from scratch. If I do, should I also reinstall windows?

Before reinstalling Windows and FSXm try uninstalling UT2.If you still get the crash, try flying the FSX B-737.My bet is once you uninstall either or both these add-ons,you will no longer get the CTD.Provided, of course, you are not experiencing theUIAUTOMATIONCORE CTD.Cheers,- jahman.

Hi again Jahman,I'll uninstall UT2, back to stock AI, not such a big deal I guess.And try flying stock 737 as opposed to PMDG's MD-11 in case it CTD (or whatever error, or system crash) occurs again? Is that what you meant?I'll give it a shot. Let you know!Thanks!

Complex aircraft like the PMDG MD-11 are a lot of fun to fly, but they also stress FSX in terms of processor and memory requirements.The trick is to remove add-ons to reduce FSX workload, than add them back again one at a time and see which one causes FSX to CTD.But I mention again the UIAUTOMATIONCORE bug, in case you are runing Windows 7 (64 bits), as it is a predictable source of CTDs after twenty or so times you pull-down the menu bar or right-click on the screen. If this is the case, you wouldn't need to uninstall your add-ons...Cheer,- jahman.

I've done it!Ultimate Traffic 2 was the culprit! I uninstalled it last night and started a flight in the MD-11 from LSZH to TNCM. Pause at top of decent. Went to bed and when I woke up this morning FSX was still running, pauzed as requested and ready to land. Made a nice landing at TNCM and am now refueling for the flight back. I am staying in the same session to test if it will hold out for another 9 or 10 hours of flying.Thanks again for your tips, I'll report back when I'm back in Zurich.

Complex aircraft like the PMDG MD-11 are a lot of fun to fly, but they also stress FSX in terms of processor and memory requirements.The trick is to remove add-ons to reduce FSX workload, than add them back again one at a time and see which one causes FSX to CTD.But I mention again the UIAUTOMATIONCORE bug, in case you are runing Windows 7 (64 bits), as it is a predictable source of CTDs after twenty or so times you pull-down the menu bar or right-click on the screen. If this is the case, you wouldn't need to uninstall your add-ons...Cheer,- jahman.

I had to fly twice from RJAA to KLAX due to a fatal error on approach to LAX because I had did multiple menu pull downs and right clicks on this long flight. :( I know it has been discussed often, but can someone refresh my memory, what is the UIAUTOMAT IONCORE bug? :( I flew last night/today the same RJAA to KLAX flight and only did a couple right clicks/menu pull downs and had no CTD's. Does anyone know how many of these you can do without getting a fatal error. I was scared to death to do just a couple :(

:( I spoke too soon... Firstly, I was overweight for the short runway at TNCM and I crashed at the end of the runway... I splashed.. Stupid mistake, but I can live with that. So after that I decided to skip the TNCM - LSZH run and started a new flight KLAX - EGLL. A little after Las Vegas the system froze again. I read a few posts here that when FSX freezes people are still able to get into the task manager and kill the process, but even that is impossible for me. The picture just freezes, no sound either and the entire computer becomes unresponsive. This is rather frustrating because in such cases there are no error reports either. I have to do a hard reboot.Uninstalling UT2 didn't solve my problems. I will next uninstall REX2 and see if that solves it. If not I will proceed to uninstall everything and start reinstalling one by one. Start with FSX, do a long haul in one of the stock planes (I hate doing that because they are so shabby, but it needs to be tested). If succesful I will install the MD-11 and test again. Etc..Will post back if I figure it out.

I had to fly twice from RJAA to KLAX due to a fatal error on approach to LAX because I had did multiple menu pull downs and right clicks on this long flight. :( I know it has been discussed often, but can someone refresh my memory, what is the UIAUTOMATIONCORE bug? :(

UIAUTOMATIONCORE bug details.

I flew last night/today the same RJAA to KLAX flight and only did a couple right clicks/menu pull downs and had no CTD's. Does anyone know how many of these you can do without getting a fatal error. I was scared to death to do just a couple :(

About 20 clicks and you're history! :-)Cheers,- jahman.

Hello.I had the same issue yesterday after 3 hrs flying but I did not use pull down menu and did not right click on the screen. I use PMDG B747, Active Sky Evolution and FSInn. That's about it. I was chatting a lot via FSInn and had to open several screen on FSInn. May have FSInn caused CDTs?Thanks.Windows 7 (64) Quad