# P3D 3.4.18.19475 NTDLL Crash

## Recommended Posts

Dear all,

I have a crash related to the NTDLL on my P3D during my flight from Hong Kong to Amsterdam. I've had this crash before during my flights from Hong Kong to Europe but it was fixed a while ago by using driver booster to update the drivers. It is now happening again and I have:

1. Ensured I have all the latest drivers

2. Reinstalled my display driver

3. Updated my BIOS.

Here is the event viewer log.

Faulting application name: Prepar3D.exe, version: 3.4.18.19475, time stamp: 0x5851bfd2
Faulting module name: ntdll.dll, version: 10.0.14393.479, time stamp: 0x58256ca0
Exception code: 0xc0000374
Fault offset: 0x000d9d11
Faulting process id: 0x1b24
Faulting application start time: 0x01d266fdd46ec959
Faulting application path: E:\Prepar3D v3\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 1a087aae-4a19-4e9f-8e20-bb9b323332e2
Faulting package full name:
Faulting package-relative application ID:


Here is the crashview.

﻿Version=1
EventType=APPCRASH
EventTime=131280651160223233
ReportType=2
Consent=1
ReportIdentifier=bfdb06a9-d301-11e6-9991-8ba746ebe9e5
IntegratorReportIdentifier=1a087aae-4a19-4e9f-8e20-bb9b323332e2
WOW64=1
NsAppName=Prepar3D.exe
AppSessionGuid=00001b24-0003-0033-59c9-6ed4fd66d201
TargetAppId=W:0000da39a3ee5e6b4b0d3255bfef95601890afd80709!0000da39a3ee5e6b4b0d3255bfef95601890afd80709!Prepar3D.exe
TargetAppVer=2016//12//14:21:55:30!752db!Prepar3D.exe
BootId=4294967295
Response.BucketId=51d6cca909c546bfc6a9f537c922678a
Response.BucketTable=1
Response.LegacyBucketId=108643154478
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=3.4.18.19475
Sig[2].Name=Application Timestamp
Sig[2].Value=5851bfd2
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_ae77
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.14393.479
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=58256ca0
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
Sig[7].Value=PCH_E4_FROM_ntdll+0x0006EB8C
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.14393.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Value=ae77
DynamicSig[23].Value=ae77539f15c6852208019c600e73c756
DynamicSig[24].Value=652d
DynamicSig[25].Value=652d6fb4ac0f3d2207fd4b55e196a2cb
UI[2]=E:\Prepar3D v3\Prepar3D.exe
UI[3]=Prepar3D exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Prepar3D exe
AppPath=E:\Prepar3D v3\Prepar3D.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=BD1B235EF8985E2E807C0FA0D29F95EA


I am running the sim on a ASUS Zenbook Pro UX501VW, here are the specs

Core i7 6700HQ

GTX960M

240G SSD

1T HDD

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

Hello, not shure but maybe it helps:

Since i have deinstalled ALL Programs wich shows moving maps, i have not got any nt.dll or terrain.dll -error while flying.

im using now the ASN16 map alone. its not google or Avliasoft or quality of gemini, but it runs whitout this errors.

##### Share on other sites

Hello, not shure but maybe it helps:

Since i have deinstalled ALL Programs wich shows moving maps, i have not got any nt.dll or terrain.dll -error while flying.

im using now the ASN16 map alone. its not google or Avliasoft or quality of gemini, but it runs whitout this errors.

Don't think I got those, the addons I used include:

1. PMDG 777

2. OpusFSI

3. IVAP

4. Ezdok (Not 2.0)

5. Multiple airport scenery, with Orbx Global, Orbx Vector and OpenLC Europe

##### Share on other sites

The AVSIM CTD Guide, page 33 (see link to guide in my signature), provides probable fixes for the ntdll.dll and stackhash.  It's something you have to investigate.  I have had several of them.  If I have my system overclocked and getting these faulting modules, I'll go to the optimal default overclock in the BIOS and this fixes it most of the time.  Too high or too low CPU voltage and these faulting modules will suddenly appear.

To investigate, I would recommend checking out page 10 of the guide, How to Fix most CTD's and Freezes.  Start at renaming or deleting your p3d.cfg and restarting P3D and see if this fixes the problem.  If not, rename or delete the scenery.cfg and restart P3D and see if this fixes the problem.  If not, rename (do not delete) the dll.xml (there are two - one in the same folder as the P3D.cfg and one in the same folder as the scenery.cfg).  In P3D, the dll.xml will be rebuilt to the default dll.xml and it will be in the scenery.cfg folder.  Restart P3D and see if this fixes the problem.  If not, then if is a computer system problem or you have an incompatible addon or your display driver settings are set too high.

Best regards,

Jim

• 1

##### Share on other sites

The AVSIM CTD Guide, page 33 (see link to guide in my signature), provides probable fixes for the ntdll.dll and stackhash.  It's something you have to investigate.  I have had several of them.  If I have my system overclocked and getting these faulting modules, I'll go to the optimal default overclock in the BIOS and this fixes it most of the time.  Too high or too low CPU voltage and these faulting modules will suddenly appear.

To investigate, I would recommend checking out page 10 of the guide, How to Fix most CTD's and Freezes.  Start at renaming or deleting your p3d.cfg and restarting P3D and see if this fixes the problem.  If not, rename or delete the scenery.cfg and restart P3D and see if this fixes the problem.  If not, rename (do not delete) the dll.xml (there are two - one in the same folder as the P3D.cfg and one in the same folder as the scenery.cfg).  In P3D, the dll.xml will be rebuilt to the default dll.xml and it will be in the scenery.cfg folder.  Restart P3D and see if this fixes the problem.  If not, then if is a computer system problem or you have an incompatible addon or your display driver settings are set too high.

Best regards,

Jim

Thanks Jim, I'll try lowering my sim settings as I don't seem to have such problem with trans-Atlantic or trans pacific flights. If that doesn't work I'll let the sim rebuild the dll.xml and exe.xml. Last resort would be complete reinstall of P3D. Thanks!

##### Share on other sites

I would never recommend a complete reinstall of P3D.  If you rename the p3d.cfg, scenery.cfg, dll.xml and exe.xml, your sim is pretty much back to the default.  Your settings are at the default, no addon scenery is loading, and no modules are loading.  Some computer experts have said this is better than reinstalling or repairing the sim application.  If this fixes the problem, then you need to bring back the old scenery.cfg, run P3D and see if the problem is fixed.  If so, then the dll.xml and exe.xml.  If you start getting a crash or freeze again, it is one of the modules loading in the dll.xml.  The AVSIM CTD Guide shows you how to disable individual modules.

Best regards,

Jim

## Create an account

Register a new account

• Tom Allensworth,
Founder of AVSIM Online

• ### Hot Spots

• Flight Simulation's Premier Resource!

AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

$20,145.00 of$36,000.00 goal reached.