CTD during initial loading (before main menu), ntdll.dll

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

no

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

yes

Brief description of the issue:

when I try to start the Sim, it crashes back to the desktop before reaching the main menu.

Provide Screenshot(s)/video(s) of the issue encountered:

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.35.21.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.19041.3636, Zeitstempel: 0x9b64aa6f
Ausnahmecode: 0xc0000374
Fehleroffset: 0x00000000000ff349
ID des fehlerhaften Prozesses: 0x954
Startzeit der fehlerhaften Anwendung: 0x01da3f4799cc0a1a
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll
Berichtskennung: 5cdda4a8-4f3f-4883-9d35-91d6863d2511
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

Detailed steps to reproduce the issue encountered:

start the sim and wait

Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version (Learn how to find your current graphics card driver version):

AMD 7900 XTX, Driver 23.12.1

PC specs and peripheral set up:

5800X3D, 7900XTX, 32 GB RAM, TCA Airbus Captains Pack, Pimax Crystal

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

2059586767072100496

Build Version # when you first started experiencing this issue:

[1.35.21.0]

What I tried so far (according to the guide on How to troubleshoot faulting module ntdll.dll crashes)

  • Update all drivers
  • Empited community folder, uninstalled all addons (GSX etc.)
  • Disabled every possible side application
  • run sfc /scannow; everything is ok
  • multiple reboots and checking for windows update

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

We’ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template is required in order to provide valuable information, feedback, and replication steps to our test team.

If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.

If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.

All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.

Does the sim crash before or after you click “Fly” from the world Planner

it crashed before, I couldn’t even make it to the main menu.

But interesting turn of events: It turned out my sim starts up allright, when I have the Pimax Client software open. When the Pimax Client software is not running, the sim crashes with the ntdll.dll error message as described.
I also was able to start a flight like normal.

1 Like

That would make sense.
If the sim is looking for that software and it isn’t running, it could easily crash the sim.

Well that depends; IMHO it should also start for a 2D flight without the VR software being required to run. Be that as it may, I can work with that…

1 Like

Update: I just tried with the headset disconnected but the PimaxClient software running. Same behaviour. I think that should not be the case…

Anyone else having this problem? Or any clues on how to approach it?

Error messages seem to mention FSDT LSZH even though i disabled this one in the FSDT Installer…

Blockquote
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.35.21.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.19041.3636, Zeitstempel: 0x9b64aa6f
Ausnahmecode: 0xc0000374
Fehleroffset: 0x00000000000ff349
ID des fehlerhaften Prozesses: 0x4c68
Startzeit der fehlerhaften Anwendung: 0x01da40a1ae3a1c90
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll
Berichtskennung: 4d73d3c8-414a-43b3-95f1-7129325237da
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

Blockquote
Name der fehlerhaften Anwendung: couatl64_MSFS.exe, Version: 4.8.0.5341, Zeitstempel: 0x657c4daa
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.19041.3636, Zeitstempel: 0x9b64aa6f
Ausnahmecode: 0xc0000374
Fehleroffset: 0x00000000000ff349
ID des fehlerhaften Prozesses: 0xe64
Startzeit der fehlerhaften Anwendung: 0x01da40a1dc50d582
Pfad der fehlerhaften Anwendung: G:\MSFS\LSZH\Addon Manager\couatl64\couatl64_MSFS.exe
Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll
Berichtskennung: 8b312390-cd51-47cb-97cf-690b26d7bc06
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

I somehow still have the crash. I am now on SU15 beta but the CDT on start up of the sim was there before, so I assume it is not related. I still cant even get to the main menu, when I do not have the VR headset attached (Pimax Crystal, does not matter if I have the software running or not).
What I tried to far:

  • SFC /scannow
  • Delete rolling cache
  • Empty community folder
  • Uninstalled GSX Pro
  • System reboot and Windows Update (as described here Fix for ntdll.dll crashes on Windows)
  • Running the sim under admin privileges
  • Executed the “Check and Repair” Feature in Xbox PC client software

Error Message is still the same:

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.37.5.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.19041.3996, Zeitstempel: 0x39215800
Ausnahmecode: 0xc0000374
Fehleroffset: 0x00000000000ff349
ID des fehlerhaften Prozesses: 0x4e8
Startzeit der fehlerhaften Anwendung: 0x01da6a7eb3bbbbfc
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll
Berichtskennung: e5e35af5-629c-45a1-8d77-6416e0ef802f
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.37.5.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

The mentioning of couatl is not there anymore since I uninstalled GSX pro but was also not related before: MSFS CTD Couatl64_MSFS.exe

The CTD happens in safe mode and normal mode.

Any help?

EDIT: I just tried to reinstall MSFS completly, and even during the reinstallation I get the same CTD with the error message pointing to ntdll.dll…

I think I found the reason of my troubles.

I had to fix the OpenXR installation. If anyone else has this problem, going in to the “OpenXR-Tools for Windows” → Mixed Reality → under installation might be an error you can fix by clicking there. Seemed to help in my case, at least for now…

It seemed to be related to the PimaxXR implementation. In order to run the Pimax Crystal headset again I had to switch to PimaxXR in the PimaxXR Control Center.