FSX:SE couatl.exe error **SOLVED**

[Kaiii3]

Hey,

i had to reinstal my FSX:SE yesterday and since then there have ben a problem with the coutl.exe. It starts with the FSX but then stops working. I already tried updating/reinstaling with the SA Addon Manager 3.0.0.3

Cuatl.err

Code: [Select]

couatl v2.0 (build 2378)
panic log started on Wed Apr 01 16:04:10 2015

problem raised by engine or unspecified addonExecutable integrity compromised
Windows Error Log

Code: [Select]

Name der fehlerhaften Anwendung: couatl.exe, Version: 2.0.0.2378, Zeitstempel: 0x54bec650
Name des fehlerhaften Moduls: couatl.exe, Version: 2.0.0.2378, Zeitstempel: 0x54bec650
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0041e000
ID des fehlerhaften Prozesses: 0x1574
Startzeit der fehlerhaften Anwendung: 0x01d06c84138c11e3
Pfad der fehlerhaften Anwendung: F:\Steam\steamapps\common\FSX\fsdreamteam\couatl\couatl.exe
Pfad des fehlerhaften Moduls: F:\Steam\steamapps\common\FSX\fsdreamteam\couatl\couatl.exe
Berichtskennung: 521cce34-d877-11e4-b35f-d4b6ef5d091e
I hope you can help me.

[virtuali]

Code: [Select]

[quote]problem raised by engine or unspecified addonExecutable integrity compromised
This message has been discussed many times on the forum, and it's caused by ANOTHER executable that is trying to attach to every running executable in your system. These are the known causes of that error message:

- If you have the ATI Tray Tools utility installed, you must disable the "Automatic Overclock" feature.

- If you have the Radeon Pro utility installed, you must disable "API monitoring" or use the setting "disable API monitoring for programs not listed in my profiles list"

- The Lenovo One Key Theater and Power management software

- The Trillian instant messenger.

- The Mumble VOIP program.

- The krakensysaudiolauncher.exe from the Razer Kraken headset drivers.

- The ASUS Game First III Application

If you are sure you are not running any of the above programs, then you might simply using another software that is behaving in a similar (invasive) way as those listed above, that we never heard before. Try to close all your running processes, until you find the offending one.

[Kaiii3]

thx for the help, it was Nvidia ShadowPlay, after turning it off everthing was ok again.