Sign in to follow this  
Dreamflight767

What do these ctd mean?

Recommended Posts

-Problem signature:
Problem Event Name: APPCRASH
Application Name: fsx.exe
Application Version: 10.0.62613.0
Application Timestamp: 551a6ac5
Fault Module Name: StackHash_2264
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 1a93802a
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 2264
Additional Information 2: 2264db07e74365624c50317d7b856ae9
Additional Information 3: 875f
Additional Information 4: 875fa2ef9d2bdca96466e8af55d1ae6e

or

Problem signature:
Problem Event Name: APPCRASH
Application Name: fsx.exe
Application Version: 10.0.62613.0
Application Timestamp: 551a6ac5
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18839
Fault Module Timestamp: 553e8808
Exception Code: c0000005
Exception Offset: 000398b8
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Problem signature:
Problem Event Name: APPCRASH
Application Name: fsx.exe
Application Version: 10.0.62613.0
Application Timestamp: 551a6ac5
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18839
Fault Module Timestamp: 553e8808
Exception Code: c0000029
Exception Offset: 00090b0a
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: e8ad
Additional Information 2: e8adce1c2b9e7be834b4063ac3c53863
Additional Information 3: e8ad
Additional Information 4: e8adce1c2b9e7be834b4063ac3c53863

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

The AVSIM CTD Guide provides explanations.  The crashes are common.  A stackhash is memory related.  Usually, when you get a Stackhash, you get an ntdll.dll error next.  Then another Stackhash, then an ntdll.dll.  Since the AVSIM CTD Guide may be temporarily unavailable, here's what the guide says about both and possible solutions:

 

StackHash – See also BEX and NTDLL.dll above. There is no module on your computer system named StackHash so no need to look for it. If the StackHash is shown as the faulting module, it will have four characters next to it like StackHash_0a9e.  That represents the memory address of where the fault occurred. Do not try to look for it.  You will not find it. There is no known solution (except one) to BEX/StackHash errors other than reinstalling Windows and FSX but some have accidently fixed their problem by lowering fsx/display driver settings, rebuilding the FSX.cfg, changing voltages/overclocking settings in the BIOS, disabling all scenery add-ons in the Scenery Library, and/or shutting down FSX only in Windowed Mode and starting up in Windowed Mode but never in Full Screen. One known solution is disabling MyTrafficX 5.4c in your Scenery Library.  An AI schedule might be causing this crash as the schedule may be looking for a flight and it cannot be found.  There are also AFCAD’s that come with MTX and some of those may contain objects.  If disabling the program in the Scenery Library works, then you should reinstall the product and use the default schedules. Disabling DEP has worked for some but it is not the recommended solution.  FSX/P3D will not allow you to disable DEP.  It can only be done by a freeware program that you can download from the Internet (search Google).  It has not worked for many others.  

 

NTDLL.dll – Several possibilities as follows:

  • Quote from Microsoft Techs – “Heap metadata can become corrupted and it has been identified by Microsoft as one of the most common causes of application failures.  When an application crash shows the faulting module as ntdll.dll along with the Memory Access Violation (0xc0000005), then Windows places the application on a watch list and, if the application crashes at least four times or more in an hour, the fault tolerant heap service will configure the application to use the fault tolerant heap service in the future” (Source - Chapter 10, Memory Management, Windows Internals, Part 2: Covering Windows Server 2008 R2 and Windows 7 by Mark E. Russinovich, David A Solomon, and Alex Ionescu).  The service is part of the Security Center service so you need to make sure this service is turned on.  If the ntdll.dll is placed on the watch list, this information will be shown in the Event Viewer (Admin Events).  See also Increase Heap Limitation in the Actions to Take to Prevent Crashes section of this guide.
  • MyTrafficX version 5.4c is installed. It is believed to be caused by an AI scheduling programming error. Go back to the 5.4b version or make sure no external AI program schedule is activated (i.e., the 2012 or 2013 Schedules on the developers website).  The default schedule appears to be okay for most. Check the developers support forums for updated information and possible bug fixes.
  • System overheats or you have wrong timings/voltages set for your installed RAM or CPU voltage. You might be able to fix by returning your BIOS to Optimized Defaults or lowering your overclock by one point from say, 4.4GHz to 4.3GHz.
  • Remove the UIAutomationcore.dll from the main FSX folder, if installed.
  • Check your dll.xml for duplicate entries or any corruption.  Some have fixed the NTDLL.dll CTD by removing duplicate entries and/or old software entries where the software is no longer on your system.
  • Disable User Access Controls (UAC) (see the section above for more information).
  • Update hardware drivers for your computer (especially on new computer systems) (see Driver Update information in this guide).

Best regards,

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this