I spoke too soon. The panel freeze on touchdown also happens with the initial download of the NGX and with the updated NGX download with the latest hotfix included. I made a video of it, which easy, because it happens all the timel: http://www.mediafire...denjj96216d8mct

Interesting, just watched your video and the symptoms are very similar to mine, but it didn't happen a second from touchdown for me. I was still at ~5,000+ feet, on autopilot, and a good few minutes from touchdown. The symptoms were otherwise basically identical, though (the only thing I didn't know to check was the missing FMC menu -- if it happens again I'll try and note if that's the case.)

the symptoms are very similar to mine, but it didn't happen a second from touchdown for me. I was still at ~5,000+ feet, on autopilot, and a good few minutes from touchdown. The symptoms were otherwise basically identical, though (the only thing I didn't know to check was the missing FMC menu

Yeah, the freeze can also happen during other stages of flight when I excessively switch between FMC pages and between the MAP/PLAN views of the PFD. It happens like clock work during manual landings, though. Autolanding works fine by the way. No freeze there. p.s.: the Support Desk seems to be overloaded again. I'm trying to submit a ticket with the video, but the website is taking forever after pressing the "submit ticket" button.

Seems this is a reproducible issue. I really wish pmdg would weigh in with their thoughts on this....

Can anyone that posted in this thread advise if you have been able to solve or at least figure out for sure what is causing this behavior?

No solution yet, but the freeze seems to be caused by the FMC, either by using it too much (random freeze) or because the flight plan ends (freeze at the very moment of "End of Route"/"VNAV disconnected message")

No solution yet, but the freeze seems to be caused by the FMC, either by using it too much (random freeze) or because the flight plan ends (freeze at the very moment of "End of Route"/"VNAV disconnected message")

You know what? I've only just realized, that was the case for me too. I'd made a flight plan to my intended destination, but was also using FSX's built-in ATC, so it would give me a landing slot in between AI traffic. Since ATC was vectoring me in, I hadn't set up an approach in the FMC. As I think back on it, I distinctly remember seeing an end-of-route message right before everything went haywire.

No solution yet, but the freeze seems to be caused by the FMC, either by using it too much (random freeze) or because the flight plan ends (freeze at the very moment of "End of Route"/"VNAV disconnected message")

I'm curious what would happen on your installation if you perform an ILS approach to a runway which has a defined missed approach procedure in the FMS nav database. I believe, in that situation, that the FMS will not display the "end of route" message on touchdown - (whether it is flown as a full autoland, or hand flown) as there are additional waypoints beyond the landing runway. In a successful landing, those additional waypoints will never be used, but I think they do remain on the "legs" page even after landing - at least until after exiting the runway. If, on the other hand, the landing runway is the last waypoint in your flight plan, (and the last waypoint displayed on the "legs" page), perhaps this is where the problem arises. If your freeze happens at the moment "end of route" is displayed, it almost sounds like a memory access violation in the FMS coding - (a buffer overflow) - as if the FMS was trying to access additional waypoints after the landing runway - when in fact no more waypoints exist in the flight plan. Perhaps that's not the problem at all, but it is the sort of thing that could cause a freeze or CTD, even if the system overall memory useage is otherwise well within limits.

Guys guys..... this "End of Route" thing might actually be it! It makes sense as it only happens to me just after turning off the high speed. That would likely be the time the End of Route msg would be displayed. PMDG team...please would you guys look at this as the culprit and at least let us know that your looking at it? I am going to re-do the route but just add some misc waypoint as say the next waypoint past the runway leg to see if I still get it because technically the FMC will not see it as the end of route.

I'm curious what would happen on your installation if you perform an ILS approach to a runway which has a defined missed approach procedure in the FMS nav database. I believe, in that situation, that the FMS will not display the "end of route" message on touchdown - (whether it is flown as a full autoland, or hand flown) as there are additional waypoints beyond the landing runway

Now that you mention it: I did a successful manual landing on a test flight from Edwards AFB to KLAs (10L), and the STAR I used had a go around procedure. I think you are onto something.

It happen when I took a flight From PAFA to KDCA when getting ready for landing to the airport it stop freez and stay there until it fatal error crash restart fsx I did fine for the first clean install now even I did hotfix 1 still the same even when I did some thing wrong with the FMC and it freeze on that too so there is a problem with FMC wrong input and freeze and crash restart hope they update it I fly PMDG 747-400 with out any problem only happen with NGX and MD11:( I did a real time flight take about 6 hour and 30 mins to KDCA from PAFA my system spec is Windows 7 UL i72600K OC @ 4.40GHZ ram is 16GB and GPU GTX 580 DDR5 with 3GB on board using GiGabyte GA-P67A-UD4-B3 and GPU is Zotac Saitek Pro Flight Yoke system been flying seen Friday Aug 5 2011 with out any problem done like 5 or 7 flight after my last flight was Fairbanks Intl Airport PAFA from Des Moines International Airport KDSM I've Done every thing from reinstalling and using hotfix1 still problem and gonna try re download it from PMDG in my account see is the problem still there wow I wish they give this a couple of month of releasing so they will be no problem see u guys in the sky's:) Happy Landing Ryan:)

Interesting!Machine: i980X processor, Nivida GTX480 2GB...MOBO with 12GB...two monitors....737-900ngx... NO add-on scenery, I have attempted to use REX2 ON and OFF...FScommander 8.xx running in the background on the left monitor...Plane on the right...Windows7 professional 64byte...This is a very expensive computer...Computer built has a gaming computer by techs...I am using a modified fsx.cfg file written by ******* for the I7 processor which uses 12 cores... Most flights have been without any problems...I have been very careful about settings...Like I said most flights ok, but weird things start to happen which I can't put my figure on YET! some of the problems stated above like screen freezes I have experienced..Most come at the end of a flight just before landing...It appears on level straight flights everything runs ok, but sometimes on decending, the plane will go crazy and also turn to the left, I know I have all the instruments set up for landing procedures on autopilot....The best landing on autopilot so far has been around -132 FPM.. I will report back later with more documentation...I think there needs to be one forum that just list problems to look for and how to solve them...I never had this type of problems with the 747-400 and 8I and the MD-11...The MD-11 is probably one of the best for autoland in bad weather, especially flying into lax under fog...

I think I have experienced my first panel freeze today ... I have flown the route at least 50-75 times (EDDS-EDDF) and never had that problem before ...Maybe I was just unlucky this time ... aircraft freezes with panel from 76 AGL and no input worked, but else game was running fine like instant replay and other things.Hotfix #3

Adding to the list, I am facing FSX freeze with the 737 NGX only. Requires task manager FSX shut-down. Other complex aircraft (e.g. 767 CpatainSim) run without a problem, even with cursors maxed out and add-ons like REX and ORBX running in parallel. It happnes after 15 or so minutes of flight, when preparing to land (flaps, landing gear, ILS capture). I don´t think it is lack of resources from the computer. Total allocated memory is around 4GB and there is plenty left to be used. Sometimes the computer crashes and requires a reset but this may be related to overclocking, eventhough it doesn´t happen with other add-ons (aircraft). If PMDG can tell us a solution is coming I can sleep again since this is a wonderful aircraft but could not have a full flight yet.

Adding to the list, I am facing FSX freeze with the 737 NGX only. Requires task manager FSX shut-down. Other complex aircraft (e.g. 767 CpatainSim) run without a problem, even with cursors maxed out and add-ons like REX and ORBX running in parallel. It happnes after 15 or so minutes of flight, when preparing to land (flaps, landing gear, ILS capture). I don´t think it is lack of resources from the computer. Total allocated memory is around 4GB and there is plenty left to be used. Sometimes the computer crashes and requires a reset but this may be related to overclocking, eventhough it doesn´t happen with other add-ons (aircraft). If PMDG can tell us a solution is coming I can sleep again since this is a wonderful aircraft but could not have a full flight yet.

If FSX itself is freezing, I think you're likely talking about a different problem than the rest of us, where the controls, plus most of the displays and instruments freeze, but FSX continues to simulate your (now doomed) aircraft. You might want to browse for another thread discussing FSX lockups with this model (if there is one), or start a thread of your own (if there isn't).

And it happened again, after I reduced all the cockpit textures to 50%. The whole flight went fine without a hitch, I disengaged the autopilot and autothrottle and flew the final approach manually without a problem. The very second I touched down: controls frozen, panels frozen, FMC entry disappeared from the CDU... the usual. FSX keeps running like a charm. This is most definitely not a ressource problem but a software problem with the NGX, aka "bug".

Hello Patrick, I have exactly the same issue like described in this thread: panels and controllers freeze after touchdown. However for me it happens only (and always) when I disconnect both AP and autothrottle. It means I can land manually with AP disconnected but with autothrottle on and I don't get any freeze. But when I disconnect on final both AP and A/T, I always get the freeze after touchdown. So it is autothrottle issue for me. Can you confirm that? Maybe then we can move several steps towards the solution. I will try to create the ticket as well just in case PMDG won't read this. Regards