A CTD

[zmak 331]

Log Name:      Application

Source:        Application Error

Date:          19/08/14 10:31:01 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      bb-PC

Description:

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521ea8e7

Exception code: 0xc0000374

Fault offset: 0x000ce753

Faulting process id: 0x160c

Faulting application start time: 0x01cfbbac70d17c77

Faulting application path: E:\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\Windows\SysWOW64\ntdll.dll

Report Id: d2db9cbe-27b5-11e4-a8ff-c8600024690b

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2014-08-19T15:31:01.000000000Z" />

    <EventRecordID>784727</EventRecordID>

    <Channel>Application</Channel>

    <Computer>bb-PC</Computer>

    <Security />

  </System>

  <EventData>

    <Data>fsx.exe</Data>

    <Data>10.0.61637.0</Data>

    <Data>46fadb14</Data>

    <Data>ntdll.dll</Data>

    <Data>6.1.7601.18247</Data>

    <Data>521ea8e7</Data>

    <Data>c0000374</Data>

    <Data>000ce753</Data>

    <Data>160c</Data>

    <Data>01cfbbac70d17c77</Data>

    <Data>E:\Microsoft Flight Simulator X\fsx.exe</Data>

    <Data>C:\Windows\SysWOW64\ntdll.dll</Data>

    <Data>d2db9cbe-27b5-11e4-a8ff-c8600024690b</Data>

  </EventData>

</Event>

[Jim Young 2,356]

The ntdll.dll and the exception code 0xc0000374 indicated Memory Heap Corruption. Here's what the AVSIM CTD Guide located to the right of this forum under Hot Spots says:

 

"NTDLL.dll – Several possibilities as follows:

 

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."

 

"You might get an NTDLL.dll shown as the faulting module if you have MyTrafficX 5.4c installed. It is believed to be caused by an AI scheduling programming error. A fix was being worked on."

 

"An NTDLL.dll crash can also occur if your system overheats or you have wrong voltages set for your installed RAM or CPU but this is less likely as you will most likely get a BSOD instead of a CTD."

 

"Removing the UIAutomationcore.dll from the main FSX folder will also fix NTDLL.dll CTD’s for many."

 

"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." 

 

I personally have had a lot of ntdll.dll crashes but none recently.  I fixed one by resetting my overclock back to the optimal defaults.  Another by removing a duplicate PMDG entry found in my dll.xml, and another one by disabling MyTrafficX in the scenery library (I subsequently found there was a problem with the 5.4c version as one of the AI schedules had an issue.  I run 5.4b now and no problems).

 

Although it did not fix my ntdll.dll problems, I did increase my Heap Limitation.  The AVSIM CTD Guide provides information on how to do that and I quote it here for your convenience:

 

"Increase Heap Limitation – There is a problem sometimes with Windows 7 users when too many Windows are open. This may cause an out-of-memory (OOM) crash. It is caused because of the desktop heap limitation. Here is the link to the Microsoft Fix-It program that will increase your desktop heap limitation: http://support.microsoft.com/kb/947246 . This may or may not work with Windows 8.1 as it has not been tested. (Thanks to B247NG)"

 

Hope this helps.

 

Best regards,

[zmak 331]

Thanks Jim, terrific reply and plenty to work with but I think I know which one it is. You mention having to many windows open and I have up to 12 open nearly always because I use a short throw projector and it just seems natural due to  the huge screen

 

Anyhow will start with that and the windows tool

 

cheers