About 20 Minutes after takeoff, being away about 150nM FSX crashes CTD with the Appcrash Stackhash error. The same story when i am getting close to about 200 to 100 nM, the same problem.
This clearly proves that the airports are not the cause. The loading of our airports is entirely managed by the Addon Manager and Couatl programs, and there's a range (which is 16NM for both KLAX and KDFW), if your are outside of this range, NOTHING is loaded for the airports, and both programs are sitting idle doing nothing. They start doing things only after you are inside that range.
Before that I had g3d.dll and ntdll crashes when using the 4096-texture command in my FSX. Since I use 1024 again, everything is fine.
This seems to indicate you are low on memory, because you add-ons are probably using too much of it.
Then I can load the FSUIPC-saved file and continue. With coatl loading, the reloaded flight would crash again.
That's not an indication that Couatl is the cause. First, Couatl CANNOT crash FSX by itself, by definition. An external .EXE doesn't have any access to FSX memory, so it cannot crash it.
What you are seeing is, instead, a side effect on the low memory problem you already have regardless. Although FSUIPC tries to detect and delay the crash that will happen sooner or later, enough to warn you with the beeping sound and allow you to Save and Continue, this might not be enough to save the internal memory in FSX to have issues which might lock up Simconnect communications between add-ons.
This might affect either the Addon Manager or Couatl, that might end up stuck waiting to talk with Simconnect and FSX and getting no reply, because of the low memory problems so, they are not the cause of the problem, but the victims.
You must find ways to reduce your memory usage, since FSX is a 32 bit app, and can't use more thna 4GB, regardless how much RAM you have. Under DX9, the issue is even worse because, video drivers under DX9 will duplicate the memory used by the video card (used for textures and objects) on the main RAM, taking even more space.
As discussed many other times here and on other forums, your options to reduce memory are:
- Use DirectX 10
- Reduce your settings, especially the Scenery Radius, Scenery Complexity and Autogen Density
- Don't use ultra-high resolution liveries and VC textures in your airplanes.
- Use less add-ons in a specific area.
Use the free ProcessExplorer program to check how much memory your FSX is using. If you are well over 3GB, you are going to have troubles sooner or later, even if the theoretical limit is 4GB, the real usable limit is about 3.5 GB.
