I tested it again now, with the latest MSFS 2024 SU4 Beta, using the inibuilds default A320 V2, started a flight on Gate A10, called GSX Pushback then taxied to Rwy 15L, stayed for 5 minutes on hold, than I took off and flew for 10-15 minutes in the area.
No CTDs.
I also opened the GSX menu a couple of times after take off (before reaching 10.000 ft after which GSX disables itself), and it showed all nearby airports as expected, indicating the Navdata has been read correctly.
Reading a couple of confirmation this happens also with KIAH not installed:
Further testing, I removed the FSDreamTeam‘s KIAH altogether and noticed I am still having the same issue unfortunately.
I also removed/disabled KIAH but still had the same crash.
Seems to indicate there's no issue with the airport, it's more something related to the KIAH area in general.
Now, since previous reports SEEMED to indicate this was caused by BATC, and BATC ALSO reads the Navdata using the Navdata API
just like GSX does, it's possible that BOTH GSX and BATC are
affected by the same problem with the Navdata in the KIAH area so, some users removing BATC and still getting a CTD, might be easily mislead "it wasn't BATC, so it must be GSX", but maybe the CTD might have happened just the same if you disabled GSX but kept BACT installed, because the cause is neither of the two apps: it's something in the Navdata in the KIAH area that would cause the sim to crash when queried.
As explained so many times, neither GSX nor BATC can cause the sim to crash
directly, because they are both running as external .EXE. However, if they use Simconnect to call the Navdata API, a problem with it (which can happen BOTH using the default Navdata but also with 3rd party Navdata) MIGHT crash the sim, if the sim is not able to deal with the Simconnect request in a graceful manner.
This already happened before: crashes in tha Navdata API has been reported in the past and were fixed by Asobo in some cases, and by Navigraph in other cases (even if the real cause was the sim crashing just because there was a duplicate item).
So, the next question is: all of you affected, are maybe using Navigraph or another 3rd party Navdata ?