Howdy all. I have frustrating issues with ntdll.dll crashes that have reared their ugly heads again. The only thing recently changed is the addition of a DLL file for a project I am working on. Failure time is anything from 10-30 min after sim launch, and it happens every time. Below is the data from the event viewer. Any help from the experts here would be welcomed. Thank you.

 

Latest crash

Faulting application name: Prepar3D.exe, version: 2.5.12945.0, time stamp: 0x55145f5e
Faulting module name: ntdll.dll, version: 6.3.9600.17936, time stamp: 0x55a68dd1
Exception code: 0xc0000374
Fault offset: 0x000e5904
Faulting process id: 0x7464
Faulting application start time: 0x01d129c81d085227
Faulting application path: F:\Prepar3D Install\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: ca801473-95be-11e5-82e5-448a5bd5f2c7
Faulting package full name:
Faulting package-relative application ID:

 

Another one

Faulting application name: Prepar3D.exe, version: 2.5.12945.0, time stamp: 0x55145f5e
Faulting module name: ntdll.dll, version: 6.3.9600.17936, time stamp: 0x55a68dd1
Exception code: 0xc0000374
Fault offset: 0x000e5904
Faulting process id: 0x7244
Faulting application start time: 0x01d129c4f3680624
Faulting application path: F:\Prepar3D Install\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 121aeeee-95bb-11e5-82e5-448a5bd5f2c7
Faulting package full name:
Faulting package-relative application ID:

The Exception Code indicates heap corruption.  According to the AVSIM CTD Guide (see link in my signature):

 

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.
• 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).

Hope this helps.

 

Best regards,

Having gone over this list step by step all to no avail. Is there a chance this could have anything to do with the new Nvidia drivers? This is the only other system change that has happened since this began occurring.

You may get ntdll.dll exceptions if your simconnect library is not complete. There should be at least four versions of simconnect on your P3D v2/3 system

 

microsoft.esp.simconnect: 1.0.20.0, Simconnect.dll: 1.0.195.0

microsoft.flightsimulator.simconnect: 10.0.60905.0, Simconnect.dll: 6.2.60905.0

microsoft.flightsimulator.simconnect: 10.0.61242.0, Simconnect.dll: 6.2.61355.0

microsoft.flightsimulator.simconnect: 10.0.61259.0, Simconnect.dll: 6.2.61637.0

 

To ensure these are installed, go to

C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\redist\Interface\FSX-RTM\retail\lib

C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\redist\Interface\FSX-SP1\retail\lib

C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\redist\Interface\FSX-SP2-XPACK\retail\lib

 

and in each case run: SimConnect.msi.

 

1.0.20.0 is installed by P3D and should not be un-installed.

Hi Steve,

 

Thanks.  I'll add this to the possible solutions in an upcoming update regarding the ntdll.dll. 

 

Best regards,

Cheers Jim. Nice to hear from you, keep well. Steve.