Guys - you can confirm that updating FSUIPC fixes a crash that actually names "PMDG_737NGX.dll" in the crash report?

For the occurances where an ipc.exit command is called in an LUA script, then yes it fixes it.

Wow ok - that's pretty strong evidence we're not actually at fault for this then and it explains why we could never trace/debug the source of it - it always showed our dll fully shutting down before the crash even occurred...

Guys - you can confirm that updating FSUIPC fixes a crash that actually names "PMDG_737NGX.dll" in the crash report?

100% here, yes it did

Ok, I just did a test flight KSLC-KLAS. Everything was fine, and then during descent, FSX became a slide show, which persisted until I ended the flight at the gate. FSX did not crash when I ended the flight, though. All 6 cores of my processor were being slammed at 100%...never had it do that before on this system. I will try another flight tomorrow and see if it does that again. If it does, I'll reinstall the 4.8 version and comment out the LUA exit routine, since it worked fine when I did my test flight yesterday. More to come....

Ok, I tried a flight from KBUR-KLAS, and FSX stopped responding several miles after DAG...had to use Task Manager to end FSX. I then went back to the 4.80 version of FSUIPC, and commented out the LUA exit routine again. Flew another flight KBUR-KLAS, and everything worked flawlessly - I ended the flight, exited FSX, and the GFDev program exited after FSX was closed, so that's how it's gonna stay. I will do a couple more flights tomorrow to test, and report back, but it looks like I've found the way to make everything work right on MY system....your results may vary! :(

Wow ok - that's pretty strong evidence we're not actually at fault for this then and it explains why we could never trace/debug the source of it - it always showed our dll fully shutting down before the crash even occurred...

Yeah certainly does Ryan. This is deffo not a PMDG issue, I think it is something to do with the exit option from leaving the sim to the main menu. The Aerosoft Airbus use to do it alot i think it's something to do withan XML file within FSX itself..

Guys - you can confirm that updating FSUIPC fixes a crash that actually names "PMDG_737NGX.dll" in the crash report?

FSUIPC fixed my CTD when i click "end of flight".

OK, as indicated above, I switched back to FSUIPC version 4.8 and commented out the LUA's exit routine. I have done three test flights so far, and ended the flights, closed FSX, and the GFDev app closed successfully for all of them. My solution certainly seems to work on my particular system.(I have had the strange problem of Steve's LUA script picking up the mouse cursor movement occasionally, but that's happened before the FSX crashing on exit problem....not a big deal, because button/switch functionality remains intact.)

The later version of FSUIPC fixes the ipc.exit bug which was called in the exit routines of the mcp script. If you use the later version, you can keep the the exit/cleanup routines.The mouse is moving because the mouse look command is sent by my script to stop the mouse cursor from staying on screen after commands have been set to the NGX. Thus if the mouse moves when you use the MCP the screen position will shift. It's not a problem when using track ir and ezdok. You can disable this feature in the user customisable section of the script.Best wishesSteve