B52H Posted July 27, 2015 Share Posted July 27, 2015 Whenever I select an airport in the Southern Carribean area stretching from Panama City to Trinidad and Tobago, my FSX crashes. I have never had problems with FSX beforehand in this nature, and have not installed any addons. My PC can handle FSX very well. Here is the error message: Log Name: Application Source: Application Error Date: 7/27/2015 8:17:06 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: MyPC Description: Faulting application name: couatl.exe, version: 2.0.0.2364, time stamp: 0x53cfcbe7 Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54504ade Exception code: 0xe06d7363 Fault offset: 0x00014598 Faulting process id: 0x2568 Faulting application start time: 0x01d0c86e097cdb13 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsdreamteam\couatl\couatl.exe Faulting module path: C:\WINDOWS\SYSTEM32\KERNELBASE.dll Report Id: c6a191d4-3461-11e5-bf20-7845c42faf39 Faulting package full name: Faulting package-relative application ID: Event Xml: 1000 2 100 0x80000000000000 184474 Application MyPC couatl.exe 2.0.0.2364 53cfcbe7 KERNELBASE.dll 6.3.9600.17415 54504ade e06d7363 00014598 2568 01d0c86e097cdb13 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsdreamteam\couatl\couatl.exe C:\WINDOWS\SYSTEM32\KERNELBASE.dll c6a191d4-3461-11e5-bf20-7845c42faf39 Here is another error that just happened when I was taking off at PSP: Log Name: Application Source: Application Error Date: 7/27/2015 8:25:04 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: MyPC Description: Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x80808080 Faulting process id: 0x1ec8 Faulting application start time: 0x01d0c86e92689659 Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: unknown Report Id: e36ae641-3462-11e5-bf20-7845c42faf39 Faulting package full name: Faulting package-relative application ID: Event Xml: 1000 2 100 0x80000000000000 184478 Application MyPC fsx.exe 10.0.61472.0 475e17d3 unknown 0.0.0.0 00000000 c0000005 80808080 1ec8 01d0c86e92689659 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe unknown e36ae641-3462-11e5-bf20-7845c42faf39 Link to comment Share on other sites More sharing options...
mrzippy Posted July 27, 2015 Share Posted July 27, 2015 https://www.flightsim.com/vbfs/showthread.php?279968-Kernelbase-dll-crash/page4 Give this thread a read through! Still thinking about a new flightsim only computer! Link to comment Share on other sites More sharing options...
evm Posted July 27, 2015 Share Posted July 27, 2015 "...and have not installed any addons..." Err, couatl.exe is part of GSX. The sim crashing when you select an airport in a certain area could be either GSX or the FSDT AddonManager having a problem. Link to comment Share on other sites More sharing options...
B52H Posted July 27, 2015 Author Share Posted July 27, 2015 I have not installed any addons in the past few days. I installed GSX a few years ago. Link to comment Share on other sites More sharing options...
evm Posted July 28, 2015 Share Posted July 28, 2015 GSX (and other addons) get updated from time to time. Still, if something else went wrong in there or even externally, for example if GSX was no longer able to access its files, or .Net got corrupted or whatever, you would be in trouble. So - you obviously have addons installed, and as GSX is mentioned in your first post, you should cover all bases and look/ask around the FSDT forums too. I seem to recall I had a similar problem once, and an update for the stand alone addon manager from FSDT (which does not update automatically) solved it. But don't count on it. The thing is, when there are addons in there, no matter for how long they have been, the fault scenario and solving strategy are in a wholly different ballpark that with vanilla FSX. That is why this information is important and "...have installed no addons..." is a little misleading (to me, that is). Link to comment Share on other sites More sharing options...
PhantomTweak Posted July 28, 2015 Share Posted July 28, 2015 Couatl was recently upgraded. You might consider, if you have not done so already, making certain you have the very latest version. It may be found at this location on the FSDT site. Perhaps this will help a little? Pat☺ [sIGPIC][/sIGPIC] Had a thought...then there was the smell of something burning, and sparks, and then a big fire, and then the lights went out! I guess I better not do that again! Sgt, USMC, 10 years proud service, Inactive reserve now :D Link to comment Share on other sites More sharing options...
B52H Posted July 29, 2015 Author Share Posted July 29, 2015 https://www.flightsim.com/vbfs/showthread.php?279968-Kernelbase-dll-crash/page4 Give this thread a read through! I'm not sure what caused this error (I never OCed my PC; or I'm not aware of it)... now I tried to load up one of the airports while already flying and I got stuck "loading terrain data." This is definitely a CPU issue or something is wrong with my scenery in that region. Link to comment Share on other sites More sharing options...
B52H Posted July 29, 2015 Author Share Posted July 29, 2015 Couatl was recently upgraded. You might consider, if you have not done so already, making certain you have the very latest version. It may be found at this location on the FSDT site. Perhaps this will help a little? Pat☺ This didn't work. Link to comment Share on other sites More sharing options...
B52H Posted July 29, 2015 Author Share Posted July 29, 2015 GSX (and other addons) get updated from time to time. Still, if something else went wrong in there or even externally, for example if GSX was no longer able to access its files, or .Net got corrupted or whatever, you would be in trouble. So - you obviously have addons installed, and as GSX is mentioned in your first post, you should cover all bases and look/ask around the FSDT forums too. I seem to recall I had a similar problem once, and an update for the stand alone addon manager from FSDT (which does not update automatically) solved it. But don't count on it. The thing is, when there are addons in there, no matter for how long they have been, the fault scenario and solving strategy are in a wholly different ballpark that with vanilla FSX. That is why this information is important and "...have installed no addons..." is a little misleading (to me, that is). I have no scenery for the Southern Carribean. The closest scenery I have is LatinVFR KMIA V2. I did install a few AFCADs to attempt to solve the issue, but that didn't work. Link to comment Share on other sites More sharing options...
evm Posted July 29, 2015 Share Posted July 29, 2015 I have no scenery for the Southern Carribean. The closest scenery I have is LatinVFR KMIA V2. I did install a few AFCADs to attempt to solve the issue, but that didn't work. Hi, there is no "near" or "far" in FSX. You can have addon scenery installed for the moon and it can cause an error. Every information about which addons you have is important, not just those you think that pertain to the area in question. I have a payware scenery for a place in Switzerland that causes a 10 mile high tower to appear near Bologna, 500 miles away. Things like GSX are even worse, as they influence everything. You could try and disable all the addon programs/dlls you have, to make sure none of them causes issues. You decativate them in exe.xml and dll.xml one after the other and always check if your issue is still there. To speed this up, you could disable all of them in one go, and check if the problem is gone. After checking those you need to disable your addon scenery one by one and check again. If at the end you arrive at vanilla FSX condition and your problem is still there - then either your FSX installation is corrupted (Configuration error? HDD error?) or you have a general system incompatibility (updated (display) drivers?) Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.