I doesn't use FSinn... :-(

I want to ask everyone the nex question, sorry my english is not to good.For the people who has windows 7 64 bit did you have change youre uiautomationcore.dll.To change this and write all rights to this it will solve many problems to freese to desktop expesely when you arive to the airport.Maybe this also resolve this problems because my friends online flying whit this 737 and whitout problems.Me and also they have change the uiautomationcore.dll.

Same problem here crash after shutdown everytime.

I have changed the UIcore about 2 months ago, soo this is not the fix.

A lot of noise about this and I'm not sure exactly why if I'm honest. Your sim runs OK?Your NGX works OK? So when you want the sim to stop working ie. closing it, it crashes and stops working. I just find the angst about it strange. FSLabs Conc will always crash the sim on exit with a "controls.dll" messaage, FSInn is a regular suspect with "stackhash", it happens. I'm running a pretty new i52500k at 4.5Ghz, GTX570 1.2Gb, 8Gb RAM, Win7 64bit and still get the odd one. But as I say, I'm trying to close the sim anyway.....

Count me in. I'm another one who always crashes on exit every time I chose the NGX to fly.It doesn't matter if I fly anyway. Simply positioning the NGX at any airport (addon or standard FSX) and exiting FSX afterwards leads to a crash.I think I had this as well with the J4100 but I'm don't remember what was the culprit. It went away with the J4100 so I hope there'll be a solution to the NGX as well. No other plane is affectet - and I have different aircrafts in use.My machine is a i920@4G, 1TB HDD, FSX on drive D, 6GB RAM, Nividia GTX275 Lightning; I don't use anti virus software on my FSX rig; and yes, I use the ENB modCheersChristian

Good morning Same issue here, but after fsx.cfg inputs as introduction. Before the exits were normal. Regards Marcel

Actually i get this error when i choose ESC->End flight.

Yes, exactly the same for me. No CTD if exiting FSX by menu.

I removed all my Wilco software, cleaned up the xml.dll and it fixed the problem for me.Just something for you to try if it applies to your setup. Win7X64

How do you clean up the xml.dll file ?Thanks

Any thing new.

If you Alt+F4 or Ctrl+C it just short cut ends fsx. Like above its when you press Exit to end flight and return to fsx main screen, crash every time. This is not a show stopper as it does not crash at any other time but it is a bug we share and is annoying.

After I copied the new aircraft.cfg files yesterday I was able to make a clean exit. But, I hadn't successfully started the engines as yet, I was having trouble getting the APU Started, APU button went out of commission (rather not clickable) not sure what happened.

I can't exit a flight in any way. Not by menu nor Esc, Alt-F4 or Ctrl C. I get CTD every time. This happens only in the NGX, and allways in the NGX.System is Core i7 2600k, 12GB RAM, Radeon 5770,I use ENB series, UT2, ASE and my fsx.cfg is controlled by FSX-booster. Disabling any of these hasn't helped. I find it very, very annoying! Especially because I have no idea, what's causing this.But I'm so exited about flying this great plane, that I don't use the time on debugging. And besides spending time on waiting for FSX to reopen I fly instead :-) Cheers. Lasse

I get a memory write violation error when I close FSX after running the 737, depeding on what I do with the 737.Unfortunatly, not a lot more is reported in the error. Typical default Microsoft error reporting (sigh).Not figure out yet exactly what I have to do, to cause the error on shutdown.Somewhat like looking for a needle in a haystack. System XP Pro, 32 Bit. 3 Gig switch (on or off) and no other addons.AV disabled. ( No Wilco products have seen my hard Drive !! ) NEVER happens on this system, if I do not load the 737. Seems others with Windows 7 64 bit are also having similar shutdown issues, so not just an XP issue. Might try this evening tracking it down to a 100% reproducable test, or better.While somewhat annoying, and wrong, it does not seem to be having any lasting effect.ie When I restart FSX next, all seems ok, (till I shut down again, where it may, or may not error) Not losing any sleep over this one :) Geoff

I get a memory write violation error when I close FSX after running the 737, depeding on what I do with the 737.Unfortunatly, not a lot more is reported in the error. Typical default Microsoft error reporting (sigh).Not figure out yet exactly what I have to do, to cause the error on shutdown.Somewhat like looking for a needle in a haystack. System XP Pro, 32 Bit. 3 Gig switch (on or off) and no other addons.AV disabled. ( No Wilco products have seen my hard Drive !! ) NEVER happens on this system, if I do not load the 737. Seems others with Windows 7 64 bit are also having similar shutdown issues, so not just an XP issue. Might try this evening tracking it down to a 100% reproducable test, or better.While somewhat annoying, and wrong, it does not seem to be having any lasting effect.ie When I restart FSX next, all seems ok, (till I shut down again, where it may, or may not error) Not losing any sleep over this one :) Geoff

I had/have this issue. The fix that works for me is to exit FSX by the main window exit (top right red "X") and NOT using "esc" to move ot the Free Flight window. On my particular system, which has been rock rock stable for a long time, and flies the NGX most beautifully, it is only the NGX aircraft which spawns this probelm. I am sure that eventually it will be fixed. At the moment, PMDG have other more urgent matters. Hope this helps.

Same problem here..Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61472.0 Application Timestamp: 475e17d3 Fault Module Name: PMDG_737NGX.DLL Fault Module Version: 1.0.0.0 Fault Module Timestamp: 4e3afb98 Exception Code: c0000005 Exception Offset: 00108a43 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1053