The problem doesn't have anything to do with GSX. As explained so many times, GSX cannot possibly crash the sim, since it runs externally to it and doesn't have any access to its process, only a low-level app like a service or a driver can do that.
This if confirmed by the names of the modules that REALLY caused the crash, which are part of the nVidia video drivers.
You might be easily mislead thinking it's "caused" by GSX, because it happened when opening the menu but, that was likely a result because MSFS toolbar menus are HTML/JS pages that are then being converted by the simulator own internal CoherentGT engine into DirectX commands, hence ending up possibly exposing bugs of problems with video drivers at large but, on our own side, we are just an HTML page and JS part has no way to do dangerous things either.
So, whatever caused this, is video drivers and/or video drivers settings in combination with MSFS settings.
From your log, I can see you used GSX during that flight, which further confirms the problem is not GSX. If you checked the release notes for the recently released SU13 Beta:
https://forums.flightsimulator.com/t/sim-update-13-beta-release-notes-1-34-10-0-august-9-2023/604327This one looks important:
Requesting some data using the NavData API shouldn’t freeze the sim anymore
GSX surely needs to access the Navdata API so, it's possible this problem that might mislead you GSX is "crashing the sim", when in fact it was a Simconnect bug, might be fixed for the final SU13 update.
