So like the title says , everytime now that I'm on final after a flight. be it a long or short haul as soon as I disengage the The autothrottle, FSX freezes up and end ups having a Fatal error. has anybody else encountered this before? It really frustrating after you spend 5 hours flying...I'm running Vista 64-bit if it helps to knowTrystan Verf

Everytime you disengage autothrottle it crashes? Are you using a keyboard command (set in the pmdg options) or a mouse to click the ATS disengage on the top of the middle throttle? Are you using VC or 2D at the time. What if you disengage the autothrottle early in the flight, does it happen then or only at a certain point in the flight?If this is as reproduceable as it sounds, how about a screen shot just before it crashes and tell us exactly what you did before it crashes.Strange problem, usually an addon scenery problem but in this case I don't know.

Everytime you disengage autothrottle it crashes? Are you using a keyboard command (set in the pmdg options) or a mouse to click the ATS disengage on the top of the middle throttle? Are you using VC or 2D at the time. What if you disengage the autothrottle early in the flight, does it happen then or only at a certain point in the flight?If this is as reproduceable as it sounds, how about a screen shot just before it crashes and tell us exactly what you did before it crashes.Strange problem, usually an addon scenery problem but in this case I don't know.

Ok well seems its not only the MD11, the 747 does the same thing.As for the ATS disengage, in the MD-11 its set to a key and in the 747 I clicked the toggle and it crashed the game.I tried several scenerios and FSX didn't crash when I tried disabling the ATS, only seems to do it when I'm on final after a long flight...I also didn't have any custom scenery installed, I changed my PC recently and that when the trouble started as I never had these problems with my old system.Might its be a VISTA issue, as I was running XP on my old machineTrystan Verf

Ok well seems its not only the MD11, the 747 does the same thing.As for the ATS disengage, in the MD-11 its set to a key and in the 747 I clicked the toggle and it crashed the game.I tried several scenerios and FSX didn't crash when I tried disabling the ATS, only seems to do it when I'm on final after a long flight...I also didn't have any custom scenery installed, I changed my PC recently and that when the trouble started as I never had these problems with my old system.Might its be a VISTA issue, as I was running XP on my old machineTrystan Verf

I also tried it out at an airfield with custom scenery and the bug didn't occur either, I have no clue, I just find it very frustrating, considering the amount of Money I paid for these planes to have such bugs

Understand your frustration, but believe me the bug isn't in the airplane or in Vista.It is hard to understand how ATS disable with crash but only on long flights. Have you had long flights crash without doing the ATS disengage? There is nothiing wrong disengaging autothrottle, but for testing purposes you might try letting the FMS manage the speed for you, which the MD11 does very well.Are you using Vista 32b or 64b?What does the message say when it tells you you had a fatal error and the application must close?

Understand your frustration, but believe me the bug isn't in the airplane or in Vista.It is hard to understand how ATS disable with crash but only on long flights. Have you had long flights crash without doing the ATS disengage? There is nothiing wrong disengaging autothrottle, but for testing purposes you might try letting the FMS manage the speed for you, which the MD11 does very well.Are you using Vista 32b or 64b?What does the message say when it tells you you had a fatal error and the application must close?

I run Vista 64bit, the reason I think that its something with the plane, is that I don't have this problem with other planes.I usually let the fms handle the speed all the way down to short final (+/-) 500 feet, then is when it crashes I have no idea why. I don't know what else to do, One thing I think might be interesting to know, is that everytime It CTD, I was in the virtual cockpit, might this be of any help? the only thing it says when I get the CTD is that a fatal error occured

I run Vista 64bit, the reason I think that its something with the plane, is that I don't have this problem with other planes.I usually let the fms handle the speed all the way down to short final (+/-) 500 feet, then is when it crashes I have no idea why. I don't know what else to do, One thing I think might be interesting to know, is that everytime It CTD, I was in the virtual cockpit, might this be of any help? the only thing it says when I get the CTD is that a fatal error occured

Ok, after testing somemore I noticed its not actually the ATS, the CTD occurs when I get around less then 5 nm from the thresholdTrystan Verf

So like the title says , everytime now that I'm on final after a flight. be it a long or short haul as soon as I disengage the The autothrottle, FSX freezes up and end ups having a Fatal error. has anybody else encountered this before? It really frustrating after you spend 5 hours flying...I'm running Vista 64-bit if it helps to knowTrystan Verf

TrystanTwo suggestions for you:1. Is your PC overclocked? If so, do you get the same problem when you reset ALL your hardware settings to their default values? The landing phase seems to be the "schwerpunkt" of the PMDG models presumably because proximity with the ground makes lots of systems start to kick in, so it will expose any underlying hardware instabilities in your PC like almost nothing else. 2. Did you use time acceleration at any stage during the flight which preceded the CTD? If so, do you get the same problem without using time acceleration? Or using only upto 4x acceleration? Or confining your use of acceleration to the cruise phase of flight?Tim

Does the "5NM from threshold" crash occur when you use an FSX default plane as well?Andreas

I run Vista 64bit, the reason I think that its something with the plane, is that I don't have this problem with other planes.

This is a common assumption, but the logic is faulty. If there were not thousands of copies of this plane being used without complaint the logic might be consistent.So far we've gone from disabling ATS always causing a crash to it only happening on long sessions to now not having anything to do with ATS. It is actually very hard to track a problem down, as revealed by your experience. The old adage that the difference between a problem and the solution is people understand the solution applies here. Keep trying to isolate the circumstances.Look seriously at anything you modified (system performance, video drivers or middle ware settings, cfg files, etc) and eliminate these as potential sources.

.

There's no issue with Vista 64b or XP or W7 for that matter. 32b systems have memory problems, especially at the end of a long flight caused by "leakage" but you should be immune to that. I assume you have not modified the virtual memory allocation (system advanced settings).The system will usually provide a description of the error, although it is not immediately visible you have to click on a link on the fatal error dialog box to reveal it. Make a record of what that says next time it bites you.Good idea trying to run a flight single player. Too bad these only happen after long flights, sure makes the problem isolation more difficult.I only have one request, and that is will you please share with us the solution once it is found. Maybe in a month or eighteen months, it will help someone else.

There's no issue with Vista 64b or XP or W7 for that matter. 32b systems have memory problems, especially at the end of a long flight caused by "leakage" but you should be immune to that. I assume you have not modified the virtual memory allocation (system advanced settings).The system will usually provide a description of the error, although it is not immediately visible you have to click on a link on the fatal error dialog box to reveal it. Make a record of what that says next time it bites you.Good idea trying to run a flight single player. Too bad these only happen after long flights, sure makes the problem isolation more difficult.I only have one request, and that is will you please share with us the solution once it is found. Maybe in a month or eighteen months, it will help someone else.

This is a common assumption, but the logic is faulty. If there were not thousands of copies of this plane being used without complaint the logic might be consistent.So far we've gone from disabling ATS always causing a crash to it only happening on long sessions to now not having anything to do with ATS. It is actually very hard to track a problem down, as revealed by your experience. The old adage that the difference between a problem and the solution is people understand the solution applies here. Keep trying to isolate the circumstances.Look seriously at anything you modified (system performance, video drivers or middle ware settings, cfg files, etc) and eliminate these as potential sources.

Somebody suggested I check my event viewer to see what caused the crashes and this what I found for the crashes

Log Name:      ApplicationSource:        Application ErrorDate:          17/08/2009 2:19:34 AMEvent ID:      1000Task Category: (100)Level:         ErrorKeywords:      ClassicUser:          N/AComputer:      Trystan-PCDescription:Faulting application fsx.exe, version 10.0.61637.0, time stamp 0x46fadb14, faulting module TCAS2v7.dll, version 1.1.6.0, time stamp 0x4633aecd, exception code 0xc0000005, fault offset 0x00006186, process id 0x100c, application start time 0x01ca1ee21b2a1d5c.Event 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="2009-08-17T06:19:34.000Z" />    <EventRecordID>2647</EventRecordID>    <Channel>Application</Channel>    <Computer>Trystan-PC</Computer>    <Security />  </System>  <EventData>    <Data>fsx.exe</Data>    <Data>10.0.61637.0</Data>    <Data>46fadb14</Data>    <Data>TCAS2v7.dll</Data>    <Data>1.1.6.0</Data>    <Data>4633aecd</Data>    <Data>c0000005</Data>    <Data>00006186</Data>    <Data>100c</Data>    <Data>01ca1ee21b2a1d5c</Data>  </EventData></Event>

Also

Log Name:      ApplicationSource:        Application ErrorDate:          17/08/2009 8:29:55 PMEvent ID:      1000Task Category: (100)Level:         ErrorKeywords:      ClassicUser:          N/AComputer:      Trystan-PCDescription:Faulting application fsx.exe, version 10.0.61637.0, time stamp 0x46fadb14, faulting module PMDG_747400_Main.DLL, version 10.0.61355.40, time stamp 0x483af60e, exception code 0xc0000409, fault offset 0x0007a848, process id 0x1158, application start time 0x01ca1f9a3922323c.Event 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="2009-08-18T00:29:55.000Z" />    <EventRecordID>2711</EventRecordID>    <Channel>Application</Channel>    <Computer>Trystan-PC</Computer>    <Security />  </System>  <EventData>    <Data>fsx.exe</Data>    <Data>10.0.61637.0</Data>    <Data>46fadb14</Data>    <Data>PMDG_747400_Main.DLL</Data>    <Data>10.0.61355.40</Data>    <Data>483af60e</Data>    <Data>c0000409</Data>    <Data>0007a848</Data>    <Data>1158</Data>    <Data>01ca1f9a3922323c</Data>  </EventData></Event>

hope this might be of use, the most common error is whith the TCAS module

The TCAS dll is correct version, that eliminates one CTD reason that used to happen but we don't see much anymore. Have you run a flight without using VATSIM?

The TCAS dll is correct version, that eliminates one CTD reason that used to happen but we don't see much anymore. Have you run a flight without using VATSIM?

Okay, I just did the flight again online, after finding something on the VATSIM forums, this Flight I turned the TCAS off and also disabled peer to peer in the FSinn menu, so one of these things seems to have done the trick cause it didn't CTD