Couatl.exe crash at kclt

[Sstefanatz]

when P3D V4 released i purchased kclt to go with the rest of my fsdt sceneries. last night i finally found the time to load a flight from kclt, the sim went through its loading then just after the scenery loaded and gsx started its rebuild of airport info that it rebuild when i install a new scenery, the sim stops responding (freezes). nothing works and i have to end p3d process to crash it out.
I changed to klax and everything worked fine. went to kjfk v2 and everything works, same with kiah, kmem, and phnl. same goes for the flightbeam airports aswell.
but at kclt i get this freeze

my error log:
Faulting application name: Couatl.exe, version: 3.2.0.3827, time stamp: 0x5935442e
Faulting module name: ucrtbase.dll, version: 10.0.15063.0, time stamp: 0xe880f7dc
Exception code: 0xc0000409
Fault offset: 0x000a543b
Faulting process id: 0x32d8
Faulting application start time: 0x01d2deb0b7f7a816
Faulting application path: D:\Programs\Addon Manager\Couatl\Couatl.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 58a58369-6f7b-419b-ad0b-da9c694eb3d0
Faulting package full name:
Faulting package-relative application ID:

my system
Windows 10 Pro
Version 1703
Build 15063.296
Core I7 7700K
Ram 32gb
2x nvidia gtx 1070's sli
GPU driver 22.21.13.8233 clean install

thanks for any help
Scott Stefanatz

[virtuali]

Try to force a cache rebuild, by removing this folder:

%PROGRAMDATA%\Virtuali\Couatl\prepar3dv4

[Sstefanatz]

ive tried but no change just after the scenery loads the sim freezes with the same error in event viewer

Faulting application name: Couatl.exe, version: 3.2.0.3827, time stamp: 0x5935442e
Faulting module name: ucrtbase.dll, version: 10.0.15063.0, time stamp: 0xe880f7dc
Exception code: 0xc0000409
Fault offset: 0x000a543b
Faulting process id: 0x3258
Faulting application start time: 0x01d2dfc4f79aa7e4
Faulting application path: D:\Programs\Addon Manager\Couatl\Couatl.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: c3d11650-47d3-4491-a082-1981a6225a3e
Faulting package full name:
Faulting package-relative application ID:

Thx
Scott Stefanatz

[virtuali]

I'm sorry, but I cannot reproduce the error, and you are the only one that reported it so far. You can enable logging without being able to access the GSX interface, this way:

open the Notepad and type the following on a new blank file:

logFile=couatl.log

(please note logFile is written beginning with a lower case l and a capital F )

Save the file as couatl.ini in the %APPDATA%\Virtuali folder, run FSX and then exit after it finished loading. Check your %APPDATA%\Virtuali folder and if there's a Couatl.LOG file there, post its content.

[Sstefanatz]

this crash only seems to be happening at gate d12, i loaded into e12 and the sim ran fine. but crashes when i load into d12. and for clarification this is on p3dv4. i read my opening msg and realized i hadnt specified which sim Im using

attached is the log file as a .doc

[virtuali]

this crash only seems to be happening at gate d12, i loaded into e12 and the sim ran fine. but crashes when i load into d12.

I tried it now, and I don't have any crashes at D12. Could you please try to post a log after you go to D12 ? And please, try not to post it as a Word file. Leave it as it is, and ZIP it to attach it.

[Sstefanatz]

i dont want to jinx it but its working for the moment... when/if it starts acting up again ill try again to figure out whats wrong
i feel like that proverbial guy with car trouble, car acts up, take it to the mechanic and it works just fine for him, get it home and the trouble starts all over again.
thx

[Mejjo]

I'm getting this problem too... THe Couatl error saying it needs to be restarted. The scenery vanishes even after restarting it. The only way to repair it is to restart the sim.

[virtuali]

As I've said already, I tried it now, and I don't have any crashes at KCLT.

THe Couatl error saying it needs to be restarted

The error log didn't said just that, it should have asked you to open the log, to see what the error was. If you didn't do that, you should find an error log here:

%APPDATA%\Virtuali\Coautl.ERR

or HERE.

%APPDATA%\Virtuali\Coautl.LOG if you have Logging enabled. But the Coautl.LOG gets rewritten at each start, so it only makes sense to check it (assuming you have one, because you have logging enabled in the GSX settings), immediately after the error happens, BEFORE restarting.