Repeated CTD's 1.18.14.0 & 1.18.15.0

Someone like @Jummivana should tell Asobo coders to check if this update caused some issue with external SSDs.

Updating following my last happy post - CTDs started again on external SSD, even in the world map screen.

Moving the fs back to the internal one, hope it’ll work perfectly like just one hour ago.

Has anyone else already mentioned CTD problems while using external SSD after the last update?

Yes, someone else did in another post (I can’t remember the exact thread).

Well, I hope that at least it’ll be possible to move only the community folder to external SSD without getting CTDs.

Hello Edgar. I get your storage concerns, but I’d be you’re ok using your internal SSD, or if you have room on your board, looking into a second one. My Community folder is massive at this point; I’m at over 300g/1300 items and, unless there are some really huge add-ons coming anytime soon, I have no concerns. I keep this title on one SSD and all of my other games on my second one.

Good luck!

Sorry to write that but you’ll have CTD also with internal ssd.
It’s so random that you can have a 6h flight without CTD between a lot of CTDs.

1 Like

Hopefully not, cause i had about 2hrs of flight on the internal previously and without a single CTD. Before that I couldn’t even start a single flight, had CTDs right in the world map.

1 Like

I hope for you but I had yesterday 0 CTD in 12 hours.
Today a lot (until I put my gpu speed to 20% but was so stupid imo)

I have been lucky enough to have a few problem free flights recently, until today!

Log Name: Application
Source: Application Error
Date: 01/08/2021 20:47:03
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: 0x00000000009d4e7d
Faulting process id: 0x369c
Faulting application start time: 0x01d786f2df25c11e
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: ba4c5199-cd55-4b21-a2a7-c76a17c58da7
Faulting package full name: Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:



1000
0
2
100
0
0x80000000000000

63150


Application
DESKTOP-Q2EK6FG



FlightSimulator.exe
0.0.0.0
00000000
FlightSimulator.exe
0.0.0.0
00000000
c0000005
00000000009d4e7d
369c
01d786f2df25c11e
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
ba4c5199-cd55-4b21-a2a7-c76a17c58da7
Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe
App

Since update 5, i.e. since I bought the game when it was released on Steam in August until before update 5 I have not had any problems.
Since update 5, there have been several crashes that obviously destroy my flight, I have significant performance losses when I turn the camera sideways and I also see that the objects or textures load later which causes them to appear sometimes out of nowhere.

Have I gained frames with udpate 5? Yes, but at the cost of losing lateral fluidity, stability and the desire to fly.

I don’t have anything external, I only have the intermediate version of mfs installed, all updated.

I’m having repeated CTD, 3 for each completed flight, after I start a flight 10 - 30 mins into the flight. Cannot find a consistent reason, options switched on/off, sliders up/down community folder in/out and overclock on/off.
flummoxed and extremely frustrated. First time I’ve been really p****d off
Please fix ASOBO

Well I was able to complete my first flight since the update without a CTD.
I noticed that Rex had updated Weather Force for MSFS 2020. Updated Weather Force and turned Live Weather off in MSFS data. Used Weather Force for weather and completed a Flight from KEWR to KORD in the WT CJ4. 2 1/2 hour flight. All other MSFS settings remained the same when I was getting CTD’s.
Intel I9 10900KF
MSFS on an internal SSD
Nvida RTX 3080

Also getting some CTD’s since the last update.

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: 0x00000000009dd838
Faulting process ID: 0x35a0
Faulting application start time: 0x01d7871079781c29
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 3833c8b6-3e21-4d59-8148-77914c01cb57
Faulting package full name: Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

EventData

FlightSimulator.exe
0.0.0.0
00000000
FlightSimulator.exe
0.0.0.0
00000000
c0000005
00000000009dd838
35a0
01d7871079781c29
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
3833c8b6-3e21-4d59-8148-77914c01cb57
Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe
App

I’ve got plenty of space in my internal SSD, but I also already got about 800GB of addons in the community folder and I believe that with time, the size of the folder will only grow.

I did move the community folder to external SSD (symbolic link) with the game itself installed on internal one. Works fine so far.

Wow. What a collection. I feel your pain then. I thought I had a lot. Ha.

Hey, I may have found a workaround for the CTD’s. At least this worked for me:

  1. AI TRAFFIC - Seems like there is a memory problem, when your AI traffic settings are not set to “Generic” aircraft. This seems to be the CTD problem at large airports. (=lots of AI traffic, bad memory allocation possibly) I was using the normal (flyable) models and had a CTD at every airport with a lot of AI traffic. I switched to generic and the crashes stopped. Was able to fly several flights with no problem. I have a good perfomance PC, AMD Ryzen 9 3900x, 32GB Mem, RTX 3080).

  2. Blurry Textures (Workaround, though not perfect). I read this on a different post, so I tried it.
    I went to the the config.toml in the following directory:
    C:\Users[YourName]\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\bf-pgg\PGG

Set the following in the “# enables switching lods for debugging” section:

lod_override = True (Was “False”)
lod_override_with_lod = 6 (Was “2”)

Don’t change your settings in the Flight Simulator Grafic Settings Menu! Just leave it to your normal settings. You may try a higher or lower number, if you run into performance issues.

With this Workaround the textures on the ground look a lot better, even though they are still not as crisp as before the xBox Update and Hotfix.

ADDONS: I put back the addons into the community folder and everything works. Some aircraft liveries look strange. They may have changed the opaque handling of some materials/colors. Scenery addons seem to be fine. Asobo 787 - engines won’t start.

This way I can at least enjoy flying again until the next fix comes around.

1 Like

Still unable to even get TO the menu…

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: d3d11.dll, version: 10.0.19041.746, time stamp: 0xfc177b9d
Exception code: 0xc0000005
Fault offset: 0x00000000001764a0
Faulting process ID: 0x2054
Faulting application start time: 0x01d7872866ad84e6
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d11.dll
Report ID: 4f2ad520-43cf-4a7f-bb35-71cb04229cb8
Faulting package full name: Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

I have not been able to use the flight sim for over a week. I tried to do a few things, like resetting the app, etc. Even did a clean install All 123 GB!!! Still CTD. I know this is a complex program but for what I paid, it needs to work when I want to use it.

Here is my error:

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: 0x0000000001a123c7
Faulting process id: 0x8d10
Faulting application start time: 0x01d7872918cd7aa7
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: c46dc148-8a2c-4410-853e-4d8dfbd5fabc
Faulting package full name: Microsoft.FlightSimulator_1.18.14.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

After an hour flying in the Denali National Park, I had few statters and than the last CTD of the day.
It seems to be copletely random to me.
This Simulator was very close to be OK before update 5 release. I was able to have 30 solid fps with high end setting even with my cheap GTX1060 6gb.
After update 5 I gain 5 fps but the sim is unstable as a drunken guy on a bicycle.
Trim control is so fast that is impossible to trim a/c for straight and level flight.
MSFS is now in the good way to be a nice game for xBox, not a Simulator.
I think that all MSFS team effort of last years are going to be enjoyed by someone that will make 5 mins of aerobatic with a 787 and than he will probably change game (on the xbox obviously)

1 Like