glw Posted August 3, 2016 Share Posted August 3, 2016 This event is constantly happening. I am attaching the event viewer for info. Dell XPS 8700 Core i5-4460 3.2GHz MEM 8.0GB Windows 7 pro Nvidia GeForce GT720 Link to comment Share on other sites More sharing options...
JSkorna Posted August 3, 2016 Share Posted August 3, 2016 We need you to click on the Details Tab and show us that. http://www.air-source.us/images/sigs/000219_195_jimskorna.png Link to comment Share on other sites More sharing options...
mrzippy Posted August 3, 2016 Share Posted August 3, 2016 You actually need to get a Faulting Module to show! Control Panel-> Administrative Tools-> Event Viewer, select Custom Views-> Administrative Events. One of the listed events will be for your CTD. The "Faulting Module" should point to the problem area. Tell us what the Faulting Module is! That will point us in the direction of the proper error, aiding in troubleshooting. BELOW IS A SAMPLE OF WHAT YOU MIGHT SEE! General Tab: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: This is what we need to Know! Exception code: 0xc0000005 Fault offset: 0x0000ee3a Faulting process id: 0x748 Faulting application start time: 0x01ce0253dc4b69d4 Faulting application path: R:\FSX\fsx.exe Faulting module path: R:\FSX\window.dll Report Id: 9caf77b4-6e50-11e2-8570-3085a99825d1 If there is not one listed: Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000, you will need to do as previously noted No Faulting Module? -> Remove all of the add-ons, and test the sim. If it works OK, then reinstall them one at a time and test. Be sure to test each thoroughly before moving on to the next Still thinking about a new flightsim only computer! Link to comment Share on other sites More sharing options...
glw Posted August 5, 2016 Author Share Posted August 5, 2016 Tried to go to KMEM twice, CTD both times. First was an Embraer 170 second was the standard Beech King Air. Got this same error twice. seems to be pointing to NTDLL.dll Please let me know if this helps. - - 1000 2 100 0x80000000000000 51938 Application Garry-PC - couatl.exe 3.1.0.3532 579a06cf ntdll.dll 6.1.7601.23418 5708a73e c0000374 000ce843 1d24 01d1ef3bf32beb7d C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsdreamteam\couatl\couatl.exe C:\Windows\SysWOW64\ntdll.dll 6398e3e4-5b2f-11e6-9ed5-acd1b8cc8142 couatl.exe 3.1.0.3532 579a06cf ntdll.dll 6.1.7601.23418 5708a73e c0000374 000ce843 1d24 01d1ef3bf32beb7d C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsdreamteam\couatl\couatl.exe C:\Windows\SysWOW64\ntdll.dll 6398e3e4-5b2f-11e6-9ed5-acd1b8cc8142 Link to comment Share on other sites More sharing options...
mrzippy Posted August 5, 2016 Share Posted August 5, 2016 NTDLL.DLL errrors are an indication that you need to start lowering some sliders. I would start with AI aircraft. Lower the airliners to around 35% and GA around 25%. See if that helps. Lower water slider to low 2s if it's not there already. Still thinking about a new flightsim only computer! Link to comment Share on other sites More sharing options...
mallcott Posted August 5, 2016 Share Posted August 5, 2016 The error is in the couatl module added by FSdreamteam. THAT is where the fault should be investigated. Link to comment Share on other sites More sharing options...
glw Posted August 6, 2016 Author Share Posted August 6, 2016 Thanks, I'll pass that along to them and see what they say. Link to comment Share on other sites More sharing options...
glw Posted August 6, 2016 Author Share Posted August 6, 2016 Thanks Link to comment Share on other sites More sharing options...
glw Posted August 6, 2016 Author Share Posted August 6, 2016 OK, moved all sliders, loaded KMEM with no problem. warped to different gates, no problem. All went well until I changed aircraft, CTD! This time is was the g2d issue again. After three different CTDs, two were couatl and one was g2d. I think this airport is just haunted! No matter what the settings are it seems to be hit or miss. Link to comment Share on other sites More sharing options...
mrzippy Posted August 6, 2016 Share Posted August 6, 2016 OK, moved all sliders, loaded KMEM with no problem. warped to different gates, no problem. All went well until I changed aircraft, CTD! This time is was the g2d issue again. After three different CTDs, two were couatl and one was g2d. I think this airport is just haunted! No matter what the settings are it seems to be hit or miss. Is KMEM an addon airport or default? Still thinking about a new flightsim only computer! Link to comment Share on other sites More sharing options...
PhantomTweak Posted August 6, 2016 Share Posted August 6, 2016 Just FYI, Zip, I am betting he's using the FSDT payware KMEM they came out with recently. GLW: I strongly suggest checking FSDT's forums. I've seen a number of similar problems there. Virtuali seems to usually have a good answer. Just as a note, I've read more than a few threads demonstrating that Vrituali has the patience of a Saint. Just sayin'... Good luck! I don't (can't, actually) buy payware, so I can't say much else, other than go there and read :) 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...
il88pp Posted August 8, 2016 Share Posted August 8, 2016 Problem could be the airport. Sente the addon, then do tests at the default version of that airport. Crashes gone? Then you at least know the cause and can start the search to solve it. [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.