April 10, 201313 yr So I bought FSDT Vancouver and Dallas Fort Worth, and well, both install, and work fine, but I am having problems with the Coatl thingy. It keeps crashing and saying the script engine fails. I have tried everything, everything reccomended by FSDT, like turning off the antivirus, excluding the files, installing the latest version of Addon Manager/couatl, deactivating Lenovo's Power Managment Software, and nothing works! I am not happy as there goes a fair amount of money. The error file states this. couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:08:26 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:08:59 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:09:33 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:10:07 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:10:41 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:11:15 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:11:50 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:12:24 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:12:59 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:13:34 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:14:09 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:14:44 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:15:19 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:15:53 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:16:28 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:17:03 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:17:38 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:18:13 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:18:47 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:19:22 2013 Executable integrity compromised couatl v2.0 (build 2348) panic log started on Wed Apr 10 23:30:47 2013 Executable integrity compromised I really hope someone could be kind enough to please help. Has anyone else had the same problem, and how did you fix it?
April 10, 201313 yr Contact FSDT's support. Umberto is pretty good about support. Jacek G. Ryzen 5800X3D | Asus RTX4090 OC | 64gb DDR4 3600 | Asus ROG Strix X570E | HX1000w | Fractal Design Torrent RGB | AOC AGON 49' Curved QHD |
April 10, 201313 yr Commercial Member Apart for the correct suggestion to always come to our forum for support, because posting elsewhere will only delay the response time, to reply to your question: That problem is caused by another software, that attaches to each and every executable in your system, which is a very questionable behavior and potentially very dangerous. As of today, the products that are known to cause this are: - The free ATI Tray Tools tweaker, when "automatic overclocking" is enabled - The Lenovo Power management software OR the Lenovo One Key Theatre software. - The Trillian Internet Chat Client You should first check these, which are the programs known to be causing this issue, if you are not using any of them, it's possible you found a new one. In this case, use the MSCONFIG utility to exclude all your startup programs, one by one, then enable then, one by one, to find which is the culprit. Umberto Colapicchioni http://www.fsdreamteam.com FSDT on Facebook
April 10, 201313 yr Author Well I disabled and removed all the Lenovo software(One Key, You Came, Power Management) and voila, it works, thank you for your response, I never guessed it could be other Lenovo software.
Create an account or sign in to comment