I have been recently experiencing CTD more often. Lately I was on a flght into London and everything just freezed when on short final, no crash nothing just freezed and I had to exit via task manager. Two days ago, I was departing in Hamburg and a CTD without any error message in the event viewer occured on the take off phase. Just a moment ago, I wanted to depart in Luxembourg - after a 30 minutes wait, due to the vatsim event - and it again crashed during take off phase.

I thought maybe this is because of my ssd was pretty full, so I emptied it and get some 35GB extra. Obviously this hasn't any effect. I do not run the BETA, GPU drivers are up-to-date, new windows updates not available. After the last crash the event viewer says that ntdll.dll is faulty. I don't run GSX, yet.

Does anyone experiening the same lately, or is it just me?

Just now, 737_800 said:

I have been recently experiencing CTD more often. Lately I was on a flght into London and everything just freezed when on short final, no crash nothing just freezed and I had to exit via task manager. Two days ago, I was departing in Hamburg and a CTD without any error message in the event viewer occured on the take off phase. Just a moment ago, I wanted to depart in Luxembourg - after a 30 minutes wait, due to the vatsim event - and it again crashed during take off phase.

I thought maybe this is because of my ssd was pretty full, so I emptied it and get some 35GB extra. Obviously this hasn't any effect. I do not run the BETA, GPU drivers are up-to-date, new windows updates not available. After the last crash the event viewer says that ntdll.dll is faulty. I don't run GSX, yet.

Does anyone experiening the same lately, or is it just me?

My friend is recently getting CTDs due to ntdll.dll and funnily enough I also got one today for the same module - It's pretty annoying as it's not always known what is actually causing them in the first place.

Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.22000.832, time stamp: 0x3907dfbc
Exception code: 0xc0000374
Fault offset: 0x000000000010c9a9
Faulting process ID: 0x19f4
Faulting application start time: 0x01d8b48a60e0efea
Faulting application path: F:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report ID: 9d9a56da-f2f8-4017-b405-8558a2901b4c
Faulting package full name: 
Faulting package-relative application ID: 

 

I had exactly the same CTD today 3 and a half hours in to a flight. Same Module/Exception code. 

Manged to recover the flight only for it to crash again within an hour, with the same Module but a different Exception code (0xc0000005)

Recovered the flight again and landed safely.

Had one yesterday too 005 code.

Annoying to say the least, not had a CTD for 2 months before these.

9 minutes ago, Tigerhawk said:

I had exactly the same CTD today 3 and a half hours in to a flight. Same Module/Exception code. 

Manged to recover the flight only for it to crash again within an hour, with the same Module but a different Exception code (0xc0000005)

Recovered the flight again and landed safely.

Had one yesterday too 005 code.

Annoying to say the least, not had a CTD for 2 months before these.

I had 3 CTDs in one day a out a month ago. First CTDs in over a year. I suspected it was a server issue, because I had not changed anything in the sim at all. The next day and since then, back to normal. I still think it was a server problem. 

I had CTD without an error message. Was due to my MSFS licence somehow getting corrupted, needed to reinstall from scratch but it fixed it.

2 hours ago, 737_800 said:

Does anyone experiening the same lately, or is it just me?

I've had "memory could not be read" CTDs for about a month now, after upgrading 10900KF=>12900KF and switching from z490 to z690 motherboard with DDR5. But the CTDs have been infrequent and random. Now they are rampant, every single session, even in the menu and while loading the sim. It's unbearable 😡

Edited August 20, 20223 yr by Cpt_Piett

2 hours ago, Zangoose said:

My friend is recently getting CTDs due to ntdll.dll and funnily enough I also got one today for the same module - It's pretty annoying as it's not always known what is actually causing them in the first place.

Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.22000.832, time stamp: 0x3907dfbc
Exception code: 0xc0000374
Fault offset: 0x000000000010c9a9
Faulting process ID: 0x19f4
Faulting application start time: 0x01d8b48a60e0efea
Faulting application path: F:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report ID: 9d9a56da-f2f8-4017-b405-8558a2901b4c
Faulting package full name: 
Faulting package-relative application ID: 

 

NTDLL crashes are either hardware or driver related. That's a kernel library. 

Got two CTDs today after loading up flight from KCLT to KSAV while powering up plane.

When happening often , any pilots do a couple test flights with MSFS Off-line?

From FS2CREW discord, it seems there is a « peak » with CTDs currently reported on official forum…maybe a server issue Asobo’s side.

Pierre

Hello,

I had 3 CTDs today without any error message... I didn't touch the simulation or windows!

I also had one CTD today without any error message, a long time now i had none..

cheers 😉

Also two CTDs yesterday after, literally, months.  Today everything running smoothly. 

Hasn't happened here yet. If it does I'll report.

Edited August 20, 20223 yr by Tuskin38

That is very Interesting indeed! 🤔 I had my first MSFS CTD last night, after 3 months of using it.
Okay, scecond, but the first one was due to my stupidity (playing with USB ports/devices while simming).