P3D Crash

[fishbait32]

Hey Virtuali,

So I understand that there were the key programs that affected Couatl.exe. I closed those down, and P3D worked fine until randomly it Crashed to Desktop, which I've never seen before. Now I understand what other P3D users are saying about CTD, and why they uninstalled Couatl.

Here is my Windows Event Viewer from when the crash happened:

Faulting application name: couatl.exe, version: 2.0.0.2378, time stamp: 0x54bec650
Faulting module name: couatl.exe, version: 2.0.0.2378, time stamp: 0x54bec650
Exception code: 0xc0000005
Fault offset: 0x000028f6
Faulting process id: 0x1f2c
Faulting application start time: 0x01d05bbf61dcbe06
Faulting application path: H:\Games\Prepar3D\fsdreamteam\couatl\couatl.exe
Faulting module path: H:\Games\Prepar3D\fsdreamteam\couatl\couatl.exe
Report Id: 46f06fc3-c7bb-11e4-821a-001fbc08db1e


I was in my PMDG 737NGX on approach into KLAX when it randomly Crashed.


16 seconds later this log file was created by Event Viewer:


Fault bucket 804593422, type 17
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: couatl.exe
P2: 2.0.0.2378
P3: 54bec650
P4: couatl.exe
P5: 2.0.0.2378
P6: 54bec650
P7: c0000005
P8: 000028f6
P9:
P10:

Attached files:
C:\Users\Brandon\AppData\Local\Temp\WER81E.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Brandon\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_couatl.exe_b82a589fef8a65ff31c19b4e57d37a9e64969_1f004627

Analysis symbol:
Rechecking for solution: 0
Report Id: 46f06fc3-c7bb-11e4-821a-001fbc08db1e
Report Status: 0


I went to the above directory and opened up the following below

Version=1
EventType=APPCRASH
EventTime=130705303901371676
ReportType=2
Consent=1
UploadTime=130705303902031714
ReportIdentifier=46f06fc4-c7bb-11e4-821a-001fbc08db1e
IntegratorReportIdentifier=46f06fc3-c7bb-11e4-821a-001fbc08db1e
WOW64=1
Response.BucketId=804593422
Response.BucketTable=17
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=couatl.exe
Sig[1].Name=Application Version
Sig[1].Value=2.0.0.2378
Sig[2].Name=Application Timestamp
Sig[2].Value=54bec650
Sig[3].Name=Fault Module Name
Sig[3].Value=couatl.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=2.0.0.2378
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=54bec650
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000028f6
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=H:\Games\Prepar3D\fsdreamteam\couatl\couatl.exe
UI[3]=Couatl™ Scripting Engine for FSX//ESP has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=H:\Games\Prepar3D\fsdreamteam\couatl\couatl.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\syswow64\user32.dll
LoadedModule[5]=C:\Windows\syswow64\GDI32.dll
LoadedModule[6]=C:\Windows\syswow64\LPK.dll
LoadedModule[7]=C:\Windows\syswow64\USP10.dll
LoadedModule[8]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\syswow64\oleaut32.dll
LoadedModule[15]=C:\Windows\syswow64\ole32.dll
LoadedModule[16]=C:\Windows\syswow64\shell32.dll
LoadedModule[17]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[18]=C:\Windows\system32\version.dll
LoadedModule[19]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[20]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[21]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[22]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[23]=C:\Windows\syswow64\NSI.dll
LoadedModule[24]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[25]=C:\Windows\syswow64\WININET.dll
LoadedModule[26]=C:\Windows\syswow64\urlmon.dll
LoadedModule[27]=C:\Windows\syswow64\XmlLite.dll
LoadedModule[28]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[29]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[30]=C:\Windows\syswow64\iertutil.dll
LoadedModule[31]=H:\Games\Prepar3D\fsdreamteam\couatl\python25.dll
LoadedModule[32]=H:\Games\Prepar3D\fsdreamteam\couatl\OpenAL32.dll
LoadedModule[33]=C:\Windows\system32\WINMM.dll
LoadedModule[34]=H:\Games\Prepar3D\fsdreamteam\couatl\alut.dll
LoadedModule[35]=C:\Windows\system32\IMM32.DLL
LoadedModule[36]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[37]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\comctl32.dll
LoadedModule[38]=C:\Windows\system32\uxtheme.dll
LoadedModule[39]=C:\Windows\system32\profapi.dll
LoadedModule[40]=H:\Games\Prepar3D\fsdreamteam\couatl\wx\_core_.pyd
LoadedModule[41]=H:\Games\Prepar3D\fsdreamteam\couatl\wx\wxmsw28uh_vc.dll
LoadedModule[42]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\gdiplus.dll
LoadedModule[43]=C:\Windows\syswow64\comdlg32.dll
LoadedModule[44]=C:\Windows\system32\WSOCK32.dll
LoadedModule[45]=H:\Games\Prepar3D\fsdreamteam\couatl\wx\_gdi_.pyd
LoadedModule[46]=H:\Games\Prepar3D\fsdreamteam\couatl\wx\_windows_.pyd
LoadedModule[47]=H:\Games\Prepar3D\fsdreamteam\couatl\wx\_controls_.pyd
LoadedModule[48]=H:\Games\Prepar3D\fsdreamteam\couatl\wx\_misc_.pyd
LoadedModule[49]=C:\Windows\system32\dwmapi.dll
LoadedModule[50]=H:\Games\Prepar3D\fsdreamteam\couatl\wx\_xrc.pyd
LoadedModule[51]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[52]=C:\Windows\system32\rsaenh.dll
LoadedModule[53]=C:\Windows\system32\MMDevAPI.DLL
LoadedModule[54]=C:\Windows\system32\PROPSYS.dll
LoadedModule[55]=C:\Windows\system32\wdmaud.drv
LoadedModule[56]=C:\Windows\system32\ksuser.dll
LoadedModule[57]=C:\Windows\system32\AVRT.dll
LoadedModule[58]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[59]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[60]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[61]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[62]=C:\Windows\system32\msacm32.drv
LoadedModule[63]=C:\Windows\system32\MSACM32.dll
LoadedModule[64]=C:\Windows\system32\midimap.dll
LoadedModule[65]=C:\Windows\system32\dsound.dll
LoadedModule[66]=C:\Windows\system32\POWRPROF.dll
LoadedModule[67]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[68]=H:\Games\Prepar3D\fsdreamteam\couatl\wrap_oal.dll
LoadedModule[69]=H:\Games\Prepar3D\fsdreamteam\couatl\wx\_html.pyd
LoadedModule[70]=H:\Games\Prepar3D\fsdreamteam\couatl\_libastro.pyd
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=804593422/nBucketTable=17/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Couatl™ Scripting Engine for FSX//ESP
AppPath=H:\Games\Prepar3D\fsdreamteam\couatl\couatl.exe

[virtuali]

So I understand that there were the key programs that affected Couatl.exe. I closed those down, and P3D worked fine until randomly it Crashed to Desktop, which I've never seen before. Now I understand what other P3D users are saying about CTD, and why they uninstalled Couatl.

Your error report only shows that Couatl has crashed, not that Couatl CAUSED P3D to crash.

In fact, it's exactly the opposite, your P3D crashed, and IT caused Couatl to crash. As explained many times already on the forum, Couatl.exe CANNOT CRASH THE SIM.

It might crash on its own, sure, but the worse it can happen, is that will disappear from the Addons menu bar, since there's no way for an external .exe loaded from the EXE.XML file to crash the sim.

The Couatl.exe crash is the result of your P3D CTD, not the cause.

The most likely reason for P3D crashing at KLAX when using the PMDG, it's likely always the same: memory exhaustion caused by:

- Too high settings

- Too many addons loaded at the same time

Now that PMDG is available under P3D, will likely result in many similar reports, because one of the most memory hungry airplanes out there (1st place goes to the 777) can be used now so, if P3D 2.5 + KLAX ran fine before, but there wasn't as much free VAS as in FSX ( P3D takes MORE VAS than FSX ), if you add the PMDG, you are going to risk more crashes.

Now I understand what other P3D users are saying about CTD, and why they uninstalled Couatl.

No you don't, and neither them. If you or anybody else has uninstalled Couatl, and are mislead thinking you "solved" this issue, just because the sim doesn't crash anymore, that's doesn't mean the program was the cause, but that's not the case.

If the problem was memory exhaustion, if you "uninstall Couatl", you'll also LOSE THE SCENERY so, removing a large scenery like KLAX would obviously SAVE MEMORY, that's why you or anybody else would be easily mislead into thinking the cause of the crash was Couatl, but the crash stopped only because, by removing the scenery (it won't load without Couatl, of course), you saved quite a bit of VAS memory.

A very easy test would be:

Does P3D crashes too, with a DEFAULT AIRPLANE ?

[fishbait32]

Thanks for the info.

So what settings should I lower to accommodate for these memory intensive add-ons, and are you saying more ram would reduce the crashes? (actually I just remembered FSX and P3D are 32bit applications and can't use more than 4gb of Ram if I remember correctly, so I'm at the limit then...) I'm currently at 8GB of ram. So basically I can either chose to reduce the texture detail of the jet, or the airports? So basically pull up the settings under the Add-ons tab and change the resolution to a lower setting?

[virtuali]

So what settings should I lower to accommodate for these memory intensive add-ons, and are you saying more ram would reduce the crashes? (actually I just remembered FSX and P3D are 32bit applications and can't use more than 4gb of Ram if I remember correctly, so I'm at the limit then...) I'm currently at 8GB of ram.

Unfortunately, as long as the sim is 32 bit, more RAM wouldn't help with crashes. However, with 16GB or more your system will probably run smoother overall, because the extra RAM will be used by other running application and the OS itself.

So basically I can either chose to reduce the texture detail of the jet, or the airports? So basically pull up the settings under the Add-ons tab and change the resolution to a lower setting?

Texture resolution might help a bit, but not really under P3D, which is DX11 so, the size of textures will affect VRAM consumption more than RAM. In FSX, under DX9 only, lowering the texture resolution would result in saving system RAM too, but not in DX10 or DX11, so you can try, but don't expect big savings.

The things you should lower to save memory are Scenery Complexity, Autogen Density and Level of Detail Radius.