Hi all,I'm in a bit of a pickle with what appears to be a repeateable CTD when only using the MD-11. I have noticed this now on both my old E8500 system and my newly built i7 920 system (specs below). My current test-flight involves departing the FSDreamTeam Las Vegas Intl (KLAS) and flying the eastward jet-routes to ImagineSim's Atlanta Intl (KATL). In each case, I've been using the ERLIN5.MEM approach route to ether 26R or 8L. Each time, during the descent phase, my FSX system will freeze and appear to lockup. Then, after pressing ctrl-alt-del -> Task Manager to get out of the frozen full-screen view, I can see the Windows error box indicating that FSX has CTD, with the 'Restart FSX?" checkbox.I can't figure out what's going as I don't experience this issue with other aircraft. My systems, both old and new, are Prime95 and OCCT stable for 24 hours and my gutt tells me this issue is aircraft and/or perhaps FMC specifc. Each flight involves using the VC with TrackIR5 with no issues noted throughout the entire flight, other than the CTD during the descent phase.Last night, I repeated the flight wondering if it was a duration/system issue, much as we used to experience on the 32-bit OS with OOM errors after a long flight with the PMDG 747. I sped up the cruize portion of the flight to 4x until 40nm before the TOD. Then, the same thing happened again during descent - this time producing a CTD after passing ERLIN, descending through 10,000, preparing to turn left towards the downwind-leg, towards a final onto 26R. The total flight was only about an hour so it doesn't appear to be a loading/duration issue. I should note, that LNAV and VNAV are used throughout almost the entire flight, including the problematic descent phase and is active when the CTDs are experienced.Approximate FP = KLAS -> COWBY.GUP -> J6 -J58 -> MEM.ERLIN5 -> KATLFSXsp2 on WinXPx64 with all Service Packs and updates (dedicated FSX rig). UTX, GEX, FSGenesis Mesh, FSDreamTeam KLAS, ImagineSim KATL, PMDG MD-11 (latest update) Delta Ribbons livery, FSUIPC with wind smoothing, TrackIR5, Autogen Dense, 7cm textures, Cars 11%, custom MRAI and WoAI (ACA2007 light = no errors noted with AI), NaviGraph PMDG NavData.FS Client = HiFI ASA (latest beta without DWC), FS Flight Keeper, Radar Contact 4, WideClient, SimConnect Client.I appreciate any thoughts you might have as to what to try next as I'm about to park the MD-11 in the hanger and let it collect dust for a while.

Al: Try the scenario with the add-on scenery disabled. Just a thought.

Hi ,be happy,most of my flights ends a minute after Takeoff with a freezing FSX and higher sounding engines. -fatal error occured!-i have never had this problems before the last updateand no update is in prospect, that is so hardregards J

Al: Try the scenario with the add-on scenery disabled. Just a thought.

Hi Dan,I would except for the fact that I can do the same flight with the Level-D without issue on both old and new systems. If I disable the scenery, then it only points to a loading issue in which the MD-11 is involved and not necessarly a specific scenery issue. I swear it seems like a FMC issue whereby the STAR and/or ILS modificaitons that I program near the end of the cruise portion of the flight, for the current runway in use, having something to do with it.This also happened on other descents into the likes of Charlotte (KCLT) and Nassau (MYNN), at some point, a CTD is experienced. But again, not with the Level-D.

Al, try my sidstar for KATL to rule out the default navigraph but usually problems in the procedure file only result in NONE appearing on the STAR/ARR page... have not run into a problem where the procedure file causes a CTD yet. It is more likely something that you are doing to the MCDU that is causing the problem if what you are doing is an unexpected process (ie., nothing should cause a CTD but we have only tested the majority of test case).Just based on what I've read in this forum, it is not unusual for the PMDG to be blamed for a CTD based on the fact that other add-ons do not cause the problem. This is logical conclusion but where solutions were found they were always in the users system, which for whatever reason the PMDG brought to light. I am not saying the MD11 is bug free, but there are thousands of installations without your specific problem... so now, the hard part is trying to figure out why this is happening to you. I recommend ruling out various things, such as scenery. Yes, I know the LDS works but still try this simple test. I don't really expect the scenery to be an issue but that is the only idea I come up with based on the info you have provided.

Hey Dan, thaks for the provoking thoughts. The other idea that just occured to me is to try the same flight with the 744X. Theoretically, it is more burdonsome on the system (older code) and it should use the exact same NavData files, correct? Wouldn't this tell me if it has something to do with a specific NavData file? At the moment, I honestly can't remember if your collection was installed earlier this month or not.

Well, I finally completed the flight using the MD-11 and FSP's last night, in it's entirety. Holy crap you should've seen all the AI buzzing over KATL; it looked like a swarm of lightening-bugs as I was coming in for approach at dusk. Friggin' cool :( I think the solution was to completely remove the 'BufferPools' tweak from the fsx.cfg file , which I carried over from the previous rig. I'm not ready to call it 'solved' but it didn't CTD on me either. A few more heavy scenery flights should reveal the true status.