so before you say its not couatl yes it is.
No, it's not. This has been explained so many times already and, in that same thread you linked on Avsim.
Couatl is NOT the "cause". Couatl, being an .exe file CANNOT CRASH THE SIM BY ITSELF, because it doesn't have any access to its memory space. This is really not something open to discussion, it's just the way Windows works.
Yes, I can see why you can be easily mislead thinking Couatl it's the cause "because it only happens when it's active" but that doesn't mean Couatl it's the cause, it's only the thing that makes that already-existing problem visible. The real source of the problem must be a problem in your navigation data, either airports or vor/nbd.
This because, when tracing the crash, the thing that crashes is the sim by itself in FACILITIES.DLL, because there must be a corrupted data in that area, otherwise you couldn't explain why it happens only THERE. If Couatl was the culprit (it's not, it simply cannot be, being an external .EXE), it should happen everywhere. Since it's happening only around that place, it's clear the problem is area-related. And if it's area-related, it can only be something in the scenery.
Again, you see it only with GSX installed, because GSX USED to check regularly airports nearby, to present a list of them in case you need to pre-select a gate while flying. So, GSX will ask the sim about nearby airports, and the sim crashed BY ITSELF, when checking its own database in the area.
So, the problem is the database, NOT Couatl which it's just asking to the sim to check for it. If the data is corrupted, any other utility that would try using it while flying, will crash just the same because, again, it's the SIM which is crash on its own, when data around there is queried.
HOWEVER, in the current GSX version (obtained through Live Update), GSX
doesn't query the navdata anymore, if you are flying over 10.000 feet and/faster than 250 kts, which you usually are in that area, unless you are approaching one of the airports there.
So, first be sure you have the current GSX version, by running the FSDT Live Update.
And, it would be useful to know if you have updated your navigation data from the default with 3rd party sceneries (airports, nbd/vor, magnetic variation data, etc.) because, of course, regardless how hard I tried, I couldn't replicate the problem with the default data.
please try to fix this...
We already made the only fix we could do.
Since the problem is clearly related to navigation data in that area, the only thing we could do, is stop reading it when cruising, assuming that most users would pass through that area only during a transatlantic flight.
But that's not a real solution. The real solution would be finding the reason for the data corruption, and fix THAT one instead, and we cannot possibly do that.
