My specs: Ryzen 7 3700X, 32GB 3200MHz, 1000GB SSD, RTX 2070 Super, 3840x1200 (32:10), CH Products Yoke+Pedals, MS Store version, Nvidia 471.11,
After my last post I updated to Win 21H1 and since then I had no CTDs so far. But it’s much too early to draw any conclusions.
I’m getting CTDs since the update, as well. Happens shortly into flight. System just drops to desktop with no error message.
My specs: Ryzen 3700X, 64GB 3200Mhz, Vega 56, 2560x1440.
Why do you make us do these updates??? this shoud be a option!!!
I’m getting CTDs since the update, as well. Happens shortly into flight. System just drops to desktop with no error message.
I have the Win Update since May. No CTDs prior this MSFS Update. Glad to hear, it helped with your setup. But it isn’t the solution for everyone, sadly.
Can’t even start a flight… The sim loads in, but before I can click ‘fly’ I get a ctd
Crashes shortly into any flight, usually minutes into the flight. no error message, just crash to desktop. Nvidia driver up to date, latest windows update, just started happening after Sim Update 5…
Crash to desktop after minutes flying. Happens every time, no message.
I just updated to version 1.18.13.0
My system specs are way above the recommended, Intel core i9, 64GB RAM, RTX 2070 Super, 2 SSDs (1 and 2 TB).
Note: MSFS installed in drive C initially but then moved to D via symlinks.
Windows Event Log (several like this):
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: 0x0000000001124a00
Faulting process ID: 0x10b4
Faulting application start time: 0x01d783b328ca8e2c
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 4cf77988-3be2-44e9-8ff9-2d8ff7934104
Faulting package full name: Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Yep same here, just updated to version 1.18.13.0 CTD without error message within 10 - 20 mins of flying.
Intel i7, GTX 1080 Ti, 32Gb ram.
I am having the same problem. No mods, community folder is clean. I have yet to experience a CTD untill this latest update. Now I’m getting them everytime I leave the airport or fly for a few minutes.
I have a GTX 1080 Ti, i7 6700k, running on a m.2 ssd
I’ve had more CTDs tonight after updating to SU5 than what I had this whole year.
You guys using MSI Afterburner or any other overclocking to your GPU?
Before SU5 I was always overclock my GPU and there was no problem but after SU5 the sim does not like the overclocking and does CTD. So I decided to not overclock and closed the Msi Afterburner. Not a single CTD after all.
So try to disable overclock.
Plenty of people joining our club. Welcome all. Can’t say I feel happy you had to end up in our bottomless pit of CTDs, but it is what it is.
Speaking as someone who has been experiencing CTDS since January I have to say I’m overjoyed with the fallout from this update. I can only hope something similar will afflict XBox users. That way at least Asobo and Microsoft will be forced to be far more proactive in getting to the bottom of this issue as opposed to sweeping it under the carpet.
Hopefully they will stop producing ever more fluff and nonsense and get down to actually rectifying the issues they’ve caused since the turn of the year. Unfortunately there is no way to really hit them where it hurts, in the wallet, as we’ve already paid for it, but I think I will just go back to XP11 and do some flying, albeit not in a VFR wonderland.
Take a leaf out of the Square Enix book and grasp the nettle the way they did with FFXIV Microsoft. Start again from the ground up. This is a mess. You can roll a ■■■■ in glitter but it still ends up being a ■■■■.
We proudly release our newest performance update!
Its called:
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: 0x00000000019e5fd7
Faulting process id: 0x2d8c
Faulting application start time: 0x01d7837e5f0862fa
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: b741d3d5-0826-4a54-b461-41596e76a921
Faulting package full name: Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
i use afterburner but never overclock gpu, is factory overclocked, use msia only for look graphics after crash, and change fan control, default take gpu at 80+ c*, with change curvature t about 70 ± 1*c yes it much more unstable than was before
I’m in the club too. This sucks 1500+ hours and I get a CTD before I can start a flight. I’ve had more CTDs today than in the last 3 months.
Ryzen 9 3900x, RTX 3090, 64g RAM…
even far cry 4 more stable than this right now
SU5 is also causing crashes for me. Community folder is clean and I’m on latest nvidia drivers. Sometime scrash seconds after intial loading, sometimes during initial loading bar before reaching main menu, sometimes during download of content updates… this sucks. Never had a problem before.
I’m giving it one more shot tonight. Microsoft better clean this up. This may be the worst update they’ve put out since the release last year.
I doubt that has anything to do with it. There are too many of us having issues on a multitude of setups to say it’s OC’ing. This, as the vast majority of issues w/this title, is on the Microsoft side. I really figured that this going to XBOX would prevent these occurrences. The number of affected people when they pull this nonsense is way higher now. Looks like QC didn’t check this update(AGAIN). Sitting here with a beast rig and I can’t fly. Needless to say, every other game I own runs just fine on it. Ugh..