Constant CTD every flight now (ntdll.dll)

those who just want a flight with no issues, try switching online services off as @BritishAvgk has suggested

Have to make sacrifices but at least with static weather, offline scenery etc people seem to be having better results. vatsim still works it seems


It has been happening to everyone i know, not everyone goes to the forums. This thread by itself speaks for how widespread the issue is.


The thing is its quite random even for those of us who are having problems. Yesterday I let the AI pilot (gawd help me) fly from and to the airports I experienced at least two CTDs doing myself and it was fine. Same flight, same weather, exactly the same route and conditions. And this was in safe mode by the way, the same mode that CTD for me when I made the flight manually. Today I flew with all my addons enabled but some live services disabled and it too was fine.

My Sim crashes because of the ntdll.dll also :frowning:

It is getting unusually a lot of votes and comments for being up 1 day. Rarely do i ever see a thread get this much activity, it clearly indicates how many people are having this issue, even across sim versions.


This post merged into this topic.

:wave: Thank you 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?


Brief description of the issue:

Flight Simulator crashes on approach to Split Airport
Faulting application name: FlightSimulator.exe, version:, timestamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.19041.1806, timestamp: 0x1000a5b9
Exception code: 0xc0000374
Error offset: 0x00000000000ff609
Faulting process ID: 0x2378
Faulting application start time: 0x01d8b53ea851f2db
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: c527ab98-d86f-4f8c-83ad-767345fd7c5a
Faulting Package Full Name: Microsoft.FlightSimulator_1.27.16.0_x64__8wekyb3d8bbwe
Application ID relative to the faulting package: App

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

Detailed steps to reproduce the issue encountered:

PC specs and/or peripheral set up if relevant:

Intel(R) Core™ i7-9700K CPU @ 3.60GHz 3.60 GHz
RAM 32,0 GB
Nvidia RTX2080Ti

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

Are you using DX12?


Are you using DLSS?


: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:

Indeed, something is wrong - this CTD is different than the usual one with the sound lag, just unexpected ctd. Waiting for the investigation.

1 Like

yep, random… but It seems there is a pattern for affected users . As I here mentioned: when I restart the same route, I come each time a bit far away. That might mean that I each time I start the flight I fill up my cache a bit more till it crashs again.

Thus,… if you have a route which crashs for you, you can may be test that :slight_smile:

Getting down to basics, when a client requests, for example, the latest live weather data, i’m assuming that there is more than a single server computer that might respond and that which one is asked to respond will be based on some networking logic?

Let’s say there are 100 of these weather servers and one or two of them has a problem. Might that explain why the whole user-base isn’t getting the issue… yet at least?

Absolutely, it’s clear it’s widespread for some users. However, my point, and I think SeedyL was also alluding to this, is that this is still a small subset of users reporting the issue. I don’t know how many users use MSFS concurrently, but I would imagine it’s in the thousands.

This isn’t to diminish what people are experiencing, so please don’t take it that way.


To add more info on this strange CTDs, just before MSFS closes sounds disappeare. Never had something before and given I made ZERO changes to my hardware or my software, something happened server side. It’s evident.

1 Like

Yes I did so, same route (From ENGM to EKCH) crashed twice, both with add-ons working and in safe mode with no add-ons. The AI pilot did the same flight in safe mode (I did this so my peripheral controls could also be left switched off) and the flight was fine.

1 Like

same here indeed

The raw number of replies to this topic is not a meaningful metric when trying to gauge how many individual people are affected by this crash. Many people have responded to this topic multiple times (myself included). More useful numbers to look at are the number of unique users who have responded to this topic and the number of votes for this bug report. Even those, however, can potentially be misleading. As we’ve seen, many people are using this topic as a catch-all location to report any CTD (including the “memory could not be read” error), not this specific crash related to ntdll.dll that appears to have started within the last 48 hours.

To re-iterate, we are aware that many people are experiencing this crash, we are watching this topic very closely, we are treating it seriously, and we have escalated the issue to our support teams. However, it’s not accurate that this is affecting every MSFS player.


Finished a full reinstall because I had kicked that off before becoming aware of wider issues.

Re-enabled various add ons (Orbx GB North, various airports)

Installed the BN-2 Islander update.

Turned off live weather.

I’ve just flown two extended circuits from EGNM (Leeds Bradford) with a weather preset with no problems.

may be your route is shorter than I choose and the data are then in third try within the rolling-cache…
( I know, its a guess :slight_smile: )

PS: may be I should disable rolling-cache and checking whats happen

Exact same here. CTD on approach to LSZH with Fenix A320:

Never look into these forums, but i came here because i had my first CTDs since i started using msfs a few months ago. Had the first on Tuesday and one on friday and now today, haven’t flown between.

No, I dont use Rolling cache.

1 Like

Not every player no, but a very large amount, just look at how many streamers/youtubers have had CTD’s if the handful I watch pretty much every day at least half of them have had CTD’s in the last few days. So it’s a high percentage, and should be fixed ASAP.