Happends with all aircraft.,

p3d 4.3

gtx 1080ti

i7-8700k oc to 4.7

all orbx stuff gsx active sky ect..

same spot every time

its a NTDLL.DLL Error

Please help..

http://prntscr.com/kpskmr

 exactly this topic but it isnt got a solotion... only turning off coatl but now i cannot fly to fsdt airports

I use to get a crash at the exact same location when flying from KORD to KSTL.  An NTDLL.dll error.  Then I set up Process Monitor to monitor only FS and FS addons during a flight as described on Page 17, AVSIM CTD Guide.  At the time of the crash, I wrote down the time, saved the Process Monitor log and then looked for the time of the crash in the log.  Of course, thousands of things were happening but my AI program was the only thing loading during that minute of the crash.  I then disabled my AI program and the crash at the exact location did not occur again.  My understanding at the time was that the simulator had run into an AI that was for compatible.  Textures could have come from FS9.  In order for a sim to crash, it needs to be loading something in the area of the crash.  It could be an object on the ground from an add-on scenery or an AI from an AI program.  Of course it could be a couatl object too but you need to see what object(s) were loading in that minute of the crash (it is difficult to pinpoint the exact time and second of the crash but, if you can get it within a minute, it will help. 

Other than that, have you tried to rename your P3D.cfg to P3D.off, your two dll.xml's to dll.off, and move all of the addon scenery you have in the Documents/Prepar3Dv4 Add-ons/ to a temporary directory such as C:\Temp?  Then load your aircraft and scenario and see if the crash occurs again?  It probably will not crash when you do this as you just have P3D running (you can load a PMDG 737, etc., if you want).  What bothers me about it being the fault of Couatl is the fact you have no FSDT airports in the area so, why would they be loading objects.  The process monitor might show FSDT airports being loaded and, if so, you need to let the experts at FSDT know that.  If none were loading, including GSX, then do not see how Couatl can be blamed.  As I understand it from that long thread you posted, not everyone who has FSDT stuff installed gets a crash at this location.  Some do not get this crash and they have FSDT/Orbx/and other stuff installed.

Maybe it is one of those AI-Ships of the popular AI-package? Maybe you haven't installed the P3Dv4 update or maybe there is one "old" ship left that wants to load there?

After updating gsx with the update making gsx disabled over 10k. The crash dosent happen. Thanks