Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

CTD on long haul at same location with ntdll.dll error

Featured Replies

Hey guys, 

I just have same CTD problem on a flight from KDEN to LFPG with PMDG777-300ER. P3D V4.2. Two attempts for same flight, CTD at same location. With Captain PFD popout disabled, and Ultimate Traffic Live, ORBX NA installed. All drivers are up to date. The crash site is not in an airport range, just somewhere over Northeast Canada. 

There's also a windows error reporting, log has been attached. It seems that something wrong with WERAF.

Anyone who has the same issue?

i7-6700K CPU @ 4.00GHz, GTX980Ti (6GB), 16GB DDR4 3200MHz, Samsung 950Pro SSD 512GB

---------------------------------------------------------------------------------------------------------------------------------------

Log Name:      Application
Source:        Application Error
Date:          2/21/2018 12:18:05 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-96DMGP6
Description:
Faulting application name: Prepar3D.exe, version: 4.2.21.24048, time stamp: 0x5a7c832c
Faulting module name: ntdll.dll, version: 10.0.16299.192, time stamp: 0x6dead514
Exception code: 0xc0000374
Fault offset: 0x00000000000f87cb
Faulting process id: 0x9a4
Faulting application start time: 0x01d3ab24b568feee
Faulting application path: D:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 7f913745-2ee3-4467-8eac-e9c8eb90eeb2
Faulting package full name: 
Faulting package-relative application ID: 
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="2018-02-21T18:18:05.404542900Z" />
    <EventRecordID>6901</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-96DMGP6</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.2.21.24048</Data>
    <Data>5a7c832c</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.16299.192</Data>
    <Data>6dead514</Data>
    <Data>c0000374</Data>
    <Data>00000000000f87cb</Data>
    <Data>9a4</Data>
    <Data>01d3ab24b568feee</Data>
    <Data>D:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data>
    <Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
    <Data>7f913745-2ee3-4467-8eac-e9c8eb90eeb2</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

----------------------------------------------------------------------------------------------------------------

Log Name:      Application
Source:        Windows Error Reporting
Date:          2/21/2018 4:52:16 AM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-96DMGP6
Description:
Fault bucket 2060777842059202619, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 4.2.21.24048
P3: 5a7c832c
P4: StackHash_f04d
P5: 10.0.16299.192
P6: 6dead514
P7: c0000374
P8: PCH_DA_FROM_ntdll+0x00000000000A09C4
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA3D3.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAF8D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAF8B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAF9C.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_4a4ce71d3908c1fc9bcf972adb77cafcfd5e0ba_00292455_0897b539

Analysis symbol: 
Rechecking for solution: 0
Report Id: fb271621-e993-40e5-9b24-a0e79688b4b8
Report Status: 268435456
Hashed bucket: c4f82eaf660ddbdb9c995a8764ef503b
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-02-21T10:52:16.849685900Z" />
    <EventRecordID>6891</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-96DMGP6</Computer>
    <Security />
  </System>
  <EventData>
    <Data>2060777842059202619</Data>
    <Data>4</Data>
    <Data>APPCRASH</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>Prepar3D.exe</Data>
    <Data>4.2.21.24048</Data>
    <Data>5a7c832c</Data>
    <Data>StackHash_f04d</Data>
    <Data>10.0.16299.192</Data>
    <Data>6dead514</Data>
    <Data>c0000374</Data>
    <Data>PCH_DA_FROM_ntdll+0x00000000000A09C4</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA3D3.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAF8D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAF8B.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAF9C.tmp.txt</Data>
    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_4a4ce71d3908c1fc9bcf972adb77cafcfd5e0ba_00292455_0897b539</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>fb271621-e993-40e5-9b24-a0e79688b4b8</Data>
    <Data>268435456</Data>
    <Data>c4f82eaf660ddbdb9c995a8764ef503b</Data>
  </EventData>
</Event>

-------------------------------------------------------------------------------------------------------------------------------------------

Log Name:      Application
Source:        Application Error
Date:          2/21/2018 4:52:12 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-96DMGP6
Description:
Faulting application name: Prepar3D.exe, version: 4.2.21.24048, time stamp: 0x5a7c832c
Faulting module name: ntdll.dll, version: 10.0.16299.192, time stamp: 0x6dead514
Exception code: 0xc0000374
Fault offset: 0x00000000000f87cb
Faulting process id: 0xaa8
Faulting application start time: 0x01d3aae5bb760265
Faulting application path: D:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: fb271621-e993-40e5-9b24-a0e79688b4b8
Faulting package full name: 
Faulting package-relative application ID: 
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="2018-02-21T10:52:12.272219700Z" />
    <EventRecordID>6890</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-96DMGP6</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.2.21.24048</Data>
    <Data>5a7c832c</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.16299.192</Data>
    <Data>6dead514</Data>
    <Data>c0000374</Data>
    <Data>00000000000f87cb</Data>
    <Data>aa8</Data>
    <Data>01d3aae5bb760265</Data>
    <Data>D:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data>
    <Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
    <Data>fb271621-e993-40e5-9b24-a0e79688b4b8</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

This issue is currently being discussed at length in the P3D Forum:

There is no solution other than mine.... see if the crash occurs with default p3d.cfg settings, disabling the two dll.xml's, and disabling all of your Add-On scenery.  Details in the AVSIM CTD Guide, page 10.  PMDG 777 does not need the module in the dll.xml to run.

Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

  • Author
On 2/21/2018 at 6:32 PM, Jim Young said:

This issue is currently being discussed at length in the P3D Forum:

There is no solution other than mine.... see if the crash occurs with default p3d.cfg settings, disabling the two dll.xml's, and disabling all of your Add-On scenery.  Details in the AVSIM CTD Guide, page 10.  PMDG 777 does not need the module in the dll.xml to run.

Hey Jim,

Thanks for feedback. I tried to check my windows update, and installed an update package, then I disable all my PMDG captain side PFD pop-out function, no more crash on 5 long haul flights so far. Don't know if this will help others ntdll.dll crash.

Thanks for posting YOUR solution.  That's the 846th fix for the ntdll.dll error.  Didn't realize you had your PFD pop-out functions enabled.  That's a lot of resources for sure and may be a PMDG bug!  Not too many fly with their PFD windows opened.

Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.