Pretty persistent, and pretty frustrating. From event log:

 

***

 

Faulting application name: Prepar3D.exe, version: 3.2.3.16769, time stamp: 0x56df48ce

Faulting module name: ntdll.dll, version: 10.0.10586.122, time stamp: 0x56cc16f5

Exception code: 0xc0000374

Fault offset: 0x000dc7a9

Faulting process id: 0x11b0

Faulting application start time: 0x01d1936687320c86

Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe

Faulting module path: C:\windows\SYSTEM32\ntdll.dll

Report Id: e41f0677-a392-4873-87c3-94109462e08d

Faulting package full name:

Faulting package-relative application ID:

 

***

 

677k. Already returned to default BIOS. No buffer pools. ASN, MCE, MyTraffic 6, Flight1 GTN 750. At a bit of a loss.

 

I'm presuming Windows 10 repair or some such is the right path?

 

Many thanks for any help.

 

 

Pretty persistent, and pretty frustrating. From event log:

 

An extremely common error with no known solution that works for everyone.  Here's what the "new" AVSIM CTD Guide states:

 

NTDLL.dll – The following is a 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.

Several possibilities for the NTDLL.dll error are as follows:

• Most likely cause is outdated or corrupted hardware drivers.  Run a driver update program as discussed in previous section.
• Use the System File Checker (SFC \scannow) to look for corrupt or missing system files.  See previous section for details on running this program.
• Recently update video card drivers?  Reinstall or install the previous version.

• System overheating.  Check (not common but it can cause this crash).
• Wrong timings/voltages set for your installed RAM.  Use the utility, CPU-Z, to check or look inside the BIOS (NOTE:  With newer Mother Boards and Memory Simms, this issue is not as common as it was with earlier systems but it can still happen).
• CPU voltage too high or too low (only if you manually adjusted this in the BIOS). 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 (applies to FSX users only).  A known fix (could be the wrong version placed in the FSX folder).
• Check your dll.xml for duplicate entries or entries where the software was removed but the entry in the dll.xml still exists.  Fix.
• Disable User Access Controls (UAC) (see the section above for more information).
• Update hardware drivers for your computer (especially on new computer systems or if the Windows OS has been reinstalled or upgraded) (see Driver Update information in this guide).
• Disable MyTrafficX, v5.4c or MyTraffic6a in the Scenery Library to see if this program is the cause of the ntdll.dll error.  It is believed to be caused by an AI scheduling programming error. For MyTrafficX 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. For MyTraffic6, some have fixed it by renaming the MyTrafficmil.bgl to MyTrafficmil.orig. 
• Some have seen this error when changing to payware aircraft after using another payware or default aircraft. 

Best regards,

Thanks, Jim. I've traced a lot of those routes. MyTraffic 6a might be it. I'll also check BIOS / MOBO drivers. If those are current I'll probably do a full Windows reinstall and start from scratch. I hate not wondering if the thing is going to crash or not ...

Update: just made a quick flight with ASN and MultiCrew off, and after making the mil.bgl change to MyTraffic 6. No issues, and smooth as silk. Will add those back one by one and see what's what ...

Another update for anyone who is tracking: Running with My Traffic Six OFF seems to have fixed the problem. I need to do a few more flights with MCE to be sure it's not the culprit, but so far I think MT6 was throwing the error. Guess it may be Ultimate Traffic 2 for me ...

Did you download any of their updated schedules?  I think their 2013 schedule has a bug in one of the flight plans. 

 

Best regards,