Repeated CTD's 1.18.14.0 & 1.18.15.0

SU5 changed and improved file handling and exFAT is not compatible (nor never really was). Had you read the MSFS install notes they have always specified NTFS

My only CTDs so far consist of me pressing the pause button, then trying to exit the pause menu and crashing.

The escape key doesn’t respond in initial pause screen so I have to click “Resume” and that is when the game crashes.

You’re right, of course, but I have limited my FPS to 60 for a along time, and right now it’s limited to 39. Heat was my first thought too, as the GPU peaked at 86c. I read somewhere in this forum that this was acceptable, but once I cleaned my long-forgotten dust filters, it fell to 63c! :woozy_face:

For a while, I thought I had nailed it, but then it froze again. It did begin shortly after SU5, but I have almost lost hope that it’s a bug in the sim, because nobody else seems to report something like this. As things stand, my best hope is a driver error, and my greatest fear is that my one year-old RTX 2070 has developed a tick, perhaps caused by my attempts to fry it. :scream:

1 Like

yep… and more worst there is a big disadvantage: the missing journal. And this makes this more vulnerable against file system errors.

2 Likes

dear simmers,

If you like me using joystick (any type of brand) or rudder pedal to play this sim and the sim keep CTD and for some reason your are a steam user like me.

Check this post out. CHeck the solution in this post. I hope it will help you as it did help me. Seems like it was corrupted controller profile. Please read and follow and hope it helps you. This post helps me after battling the constant CTD since the SU5 until the recent one.

No more crashing for me folks. Zendesk, please update your standard troubleshooting template

I never had CDT’s before the wu6 update, even after update 5. I was even skeptical of all the complaints on this forum, but now I am part of the club. Repeated CDT"s after the WU6 update. Asobo should have made a separate version for Xbox. I understand why they didn’t. it’s a matter of time and money. As previously reported, they didn’t take into account the endless variations in Pc’s and setups. They just destroyed the sim and the beautiful graphics. i’m tired of always reading the same comments from the developers regarding the possible causes that not help.

1 Like

I am on the other hand finally able to do flights. However, One location i find is crashing and that is OPIS to OPPS. Everytime I approach OPPS it causes CTD. No addons…

what i found: these add-ons show an error.
if you don’t understand, translate it

chyba c0000005/při vypnutí simu druh scenery
GAIST_MSFS_V1 AI lodě z flightsim.to
coastline-scenery-coastline-italy-v1-1-4 Italie pobřeží
redwingssimulation-airport-lfly-lyon-bron-v0-1-4 není to pěkná scenerka-SMAZANO
scenery-CH-bern-belp-lszb z flightsim.to
sdr-himalaya-pack z flightsim.to
pyreegue-airport-lytv-tivat
seafront-livingworld-vessels-ai-v1-1-7 lodě
seafront-livingworld-vessels-globalshipping-v1-2-6 lodě
aerosoft-airport-edny-friedrichshafen-v1-0-6-0 100pro problém po vypnutí 0xc0000005
digitaldesign-lows 100pro problém po vypnutí 0xc0000005
bmw-airport-lipz-venice-marco-polo-v1-0-0 100pro problém po vypnutí 0xc0000005
bmw-airport-lipb-bolzano-v2-1-0 100pro problém po vypnutí 0xc0000005
flylogic-airport-lsza-lugano-v1-0-0 100pro problém po vypnutí 0xc0000005
flylogic-airport-lszf-birrfeld-v1-0-0 100pro problém po vypnutí 0xc0000005
flylogic-airport-lszq-bressaucourt-v1-0-3 100pro problém po vypnutí 0xc0000005
aerosoft-eddk 100pro problém po vypnutí 0xc0000005
aerosoft-paderborn 100pro problém po vypnutí 0xc0000005

I’ve just given up trying various solutions to identifying the cause of the CTDs that I’ve experienced since the release of SU5 and installed Windows 11 (without retaining any of my existing Programs or Settings).

After completing the OS install, the Intel motherboard and NVidia drivers, I’ve only installed Steam, MSFS2020 (Steam Edition) and Orbx Central. The MSFS re-install was fairly painless as the content is on a separate drive and was found when I re-installed the executable that was downloaded via Steam.

So far after an hour flying before adding back all the WU content and the contents of my Community folder and a couple of hours since adding everything back in, all is well :slight_smile:

1 Like

I was able to complete a 1 hour 17 min flight around Puget Sound with nVidia driver 457.30 and this 45 fps limit in nVidia control panel.

I have been having CTD at ~ 10 minutes during approximately 95% of my flights in this area prior to this setting so I’ll keep my fingers crossed and report my findings after more testing.

2nd flight - CTD at 10 minutes. One notable difference between the first (successful) flight and this one is the first was free flight (no flight plan). This one had a flight from KOLM (parking 3) to 21W. As on numerous prior occasions, the sim CTD in the vicinity of 06WN (near Yelm Washington).

[Edit] 3rd flight - CTD 1 minute after takeoff at KOLM, no flight plan entered. Sadly 45ps limit appears to not improve CTD situation for me.

I decided to try the sim without Navigraph yesterday as Zendesk mentioned it was one of the causes of crashes, after 5 and a half hours I was thinking they were right and then I had another CTD! :frowning_face:

Up until SU5 I had very few crashes, now its just a nightmare…

Log Name: Application
Source: Application Error
Date: 11/09/2021 20:28:55
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-Q2EK6FG
Description:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000009dbead
Faulting process id: 0x103c
Faulting application start time: 0x01d7a7389da136c5
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 95f1201c-1a23-4119-b71f-15ff39b8d54d
Faulting package full name: Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:



1000
0
2
100
0
0x80000000000000

5043


Application
DESKTOP-Q2EK6FG



FlightSimulator.exe
0.0.0.0
00000000
FlightSimulator.exe
0.0.0.0
00000000
c0000005
00000000009dbead
103c
01d7a7389da136c5
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
95f1201c-1a23-4119-b71f-15ff39b8d54d
Microsoft.FlightSimulator_1.19.8.0_x64__8wekyb3d8bbwe
App

I have Capture One software installed on my PC. For me the solution was discovered here:

CTD caused by Capture One 20 codec - Bugs & Issues / CTDs - Microsoft Flight Simulator Forums

Hopefully this helps someone else. Perhaps there is other software that is causing MSFS issues.

I gave up. I’m extremely angry and frustrated. Tried a lot of different stuff. None worked. I never had a CTD or other difficulties with MSFS 2020, but since the update to 1.18.15.0 only CTD’s. I’ve used a lot of different software and games the last 15 years and I had never a program causing so much trouble and headache over a longer period of time - now 2 months. Only CTD’s. So frustrating. I switched back to xplane 11. Not the same beautiful rendering and graphics, but at least it’s running stable - always!

3 Likes

Did you check the disk you have it installed on is NTFS, and not exFAT? That seems to be be a hard blocker for users.

Repeated CTD since SU5! First flight in the latest update , CTD when taking off? This machine runs the graphics without a hitch! Previous update 1 out of three had CTD. Overall, sim works great until CTD?

Origin
64G
RTX 3090
Factory clocked

With the 3090 in some situations they have been just running too well … I would attempt limiting the frame rate in nVidia settings to I guess like 60fps with that monster?

Hi, yes it’s NTFS since the beginning. I also reinstalled MSFS 2020 twice… and experimented with various settings.

I should add that I started with MSFS 95, and also used various other flight simulators like for example Lock On and I’ve been using xplane since version 9. But nothing beats MSFS 2020…well, not in a good way at the moment! All these flight simulators had maybe 3-4 times a CTD in a year - at maximum! But not constantly like MSFS 2020 which ruins everything.

1 Like

There are a couple of FAQ’s you should probably look over. They list some common possibilities, as well as a list of software known to cause issues for some users.

https://flightsimulator.zendesk.com/hc/en-us/articles/4406280399250-All-versions-Crashing-CTDs-issues-Basic-Troubleshooting

https://flightsimulator.zendesk.com/hc/en-us/articles/4406280653202-All-versions-Crashing-CTDs-issues-Advanced-Troubleshooting

https://flightsimulator.zendesk.com/hc/en-us/articles/4406047820690-All-versions-Sim-freezes-or-crashes-before-loading-fully

Hi there,
I had the same situation with this last update (no CTD’s before and now several, every 20 min or less) ,but yesterday I changed the virtual memory (something I red on this forum) and now I’m back to the past, meaning flying 1 hour or more (hand flying and autopilot) and landing the aircraft🙂 Have you tried doing this?