Anyone have this?Problem signature: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: PMDG_MD11.DLL Fault Module Version: 10.0.61355.62 Fault Module Timestamp: 49b7c81d Exception Code: c0000005 Exception Offset: 00118301 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033Additional information about the problem: LCID: 1033

What were you doing before the crash?

hi Dirk, I was climbing out of 7L VHHH with just a vhhh/vhhh flightplan, with an ILS 7L entered into the MCDU.I have Imagine sim VHHH and Fly Tampa VHHX.

Huh, I have no idea. The MD does throw that crash when the NEW DEST function is used sometimes, but I have no idea. Sorry. It's Darrol by the way, the username is DLRK in lowercase

Hello,i have the same Problem:Protokollname: ApplicationQuelle: Application ErrorDatum: 02.03.2011 19:37:19Ereignis-ID: 1000Aufgabenkategorie:(100)Ebene: FehlerSchlüsselwörter:KlassischBenutzer: Nicht zutreffendComputer: Herbie-PCBeschreibung:Name der fehlerhaften Anwendung: fsx.exe, Version: 10.0.61637.0, Zeitstempel: 0x46fadb14Name des fehlerhaften Moduls: PMDG_MD11.DLL, Version: 10.0.61355.62, Zeitstempel: 0x49b7c81dAusnahmecode: 0xc0000005Fehleroffset: 0x00118301ID des fehlerhaften Prozesses: 0xa60Startzeit der fehlerhaften Anwendung: 0x01cbd905031afd1bPfad der fehlerhaften Anwendung: E:\fsx\fsx.exePfad des fehlerhaften Moduls: E:\fsx\GAUGES\PMDG_MD11.DLLBerichtskennung: 1a5093a8-44fc-11e0-bc2e-bcaec58dcf32Ereignis-XML:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-03-02T18:37:19.000000000Z" /> <EventRecordID>1874</EventRecordID> <Channel>Application</Channel> <Computer>Herbie-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>PMDG_MD11.DLL</Data> <Data>10.0.61355.62</Data> <Data>49b7c81d</Data> <Data>c0000005</Data> <Data>00118301</Data> <Data>a60</Data> <Data>01cbd905031afd1b</Data> <Data>E:\fsx\fsx.exe</Data> <Data>E:\fsx\GAUGES\PMDG_MD11.DLL</Data> <Data>1a5093a8-44fc-11e0-bc2e-bcaec58dcf32</Data> </EventData></Event>

Hi, this is because the cruise segement is missing. Everytime you go from Climb directly to Desc the FMS will crash. So just make sure you transfer the FMS to CRZ before entering an ILS or go direct to a waypoint that belongs to the DES Phase and you are still in Climb Phase. Jan-Paul

Just recieved this one out of the new KSFO,right on climbout.Also with net framework error.

After all the CTDs that I had (last one yesterday; due to the lack of SIDSTAR data for VHHX I used VHHH in the flight plan instead, and right during the takeoff roll I got a CTD) I must say that the FMS code is very unflexible and extremely picky regarding waypoint stringing. There must be sufficient trip lenght to allow the FMS code to properly calculate TOC and TOD waypoints, and the sensing logic must be able to transition between the flight phases. If there's anything that prevents the FMS code to do what it wants, it gets confused and crashes the sim. It's quite easy to get a crash: Try to do a traffic pattern without a waypoint in between...I cannot say that I'd expect such a behaviour from "cleanly programmed" code... Anyway, the code is "fault intolerant" and chooses the "hard way" to end any troubles it runs into. I can only hope that one day, we'll se a final service pack for the MD-11, and that the programmers look over the FMS code once more.The risk of getting a CTD are the cause that I don't longer use the MD-11 for flights that I can easily do with other airliners. I don't like FSX to forcibly get closed in the middle of a flight because the FMS code crashes the sim. Traffic patterns are a dangerous thing, let alone doing short hops or such... To be honest: I'm anxiously awaiting a CTD each time I do one of my short flights, and often the MD-11 doesn't disappoint me...The permanent CTDs were the reason I installed Win7 and FSX from scratch (since a couple of weeks I'm installing one package after another), but the CTD yesterday showed that the CTDs aren't really related to an "aged" system installation status...Andreas

Wow, you had me worried for a minute... I thought another MD-11 had crashed in the real world...Hope you find a solution to your appcrash...Andrew

After all the CTDs that I had (last one yesterday; due to the lack of SIDSTAR data for VHHX I used VHHH in the flight plan instead, and right during the takeoff roll I got a CTD) I must say that the FMS code is very unflexible and extremely picky regarding waypoint stringing. There must be sufficient trip lenght to allow the FMS code to properly calculate TOC and TOD waypoints, and the sensing logic must be able to transition between the flight phases. If there's anything that prevents the FMS code to do what it wants, it gets confused and crashes the sim. It's quite easy to get a crash: Try to do a traffic pattern without a waypoint in between...I cannot say that I'd expect such a behaviour from "cleanly programmed" code... Anyway, the code is "fault intolerant" and chooses the "hard way" to end any troubles it runs into. I can only hope that one day, we'll se a final service pack for the MD-11, and that the programmers look over the FMS code once more.The risk of getting a CTD are the cause that I don't longer use the MD-11 for flights that I can easily do with other airliners. I don't like FSX to forcibly get closed in the middle of a flight because the FMS code crashes the sim. Traffic patterns are a dangerous thing, let alone doing short hops or such... To be honest: I'm anxiously awaiting a CTD each time I do one of my short flights, and often the MD-11 doesn't disappoint me...The permanent CTDs were the reason I installed Win7 and FSX from scratch (since a couple of weeks I'm installing one package after another), but the CTD yesterday showed that the CTDs aren't really related to an "aged" system installation status...Andreas

That is pretty strong. Since I have never had a CTD with the MD-11 except when deliberatly provoked, I am curious to know what is so different between how I fly and the way you do? Obviously, I am not going to try and fly into or out of VHHX unless I have already set up the scenery and navdata as appropriate since this airport closed over a decade ago. And I do plenty of short hops, circuits and failures excercises at various airports, but knowing that a minor problem exists, I always set up a planned 'cruise' waypoint, even if I have no intention of reaching it. I recognise that the FMC requires a start, a middle and an end and I have no problem with that.