CTD after SU10

Hello. after updating the sim, clicking on “Fly now” results in a CTD. I’ve tried several times in Safe Mode and the issue still persists. Running the game in vanilla mode.

Edit: DX11, DLSS disabled.

Faulting application name: FlightSimulator.exe, version: 1.27.21.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.27.21.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001b40cd2
Faulting process id: 0x1e7c
Faulting application start time: 0x01d8cf0acde36ca4
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: c30852ed-9137-4378-bc3c-9c44c41fd4e2
Faulting package full name: Microsoft.FlightSimulator_1.27.21.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Specs:
Asus ROG STRIX Z690-A
Intel Core i5-12600K 3.7 GHz
DDR4
RTX 3080
Western Digital Blue SN550 NVMe

2 Likes

I have the sam problems, before su10 everything was working fine. After the update i can take the lessons in the tutorial part but if i choose an airport and klik ready to fly my fan on the computer is making a lot of noise and then back to windows.

I have a new laptop, i installed windows 11 from scratch, then i installed flight simulator from the ms store. same problems:
Faulting application name: FlightSimulator.exe, version: 1.27.21.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.27.21.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001b40cd2
Faulting process id: 0x0x2AB0
Faulting application start time: 0x0x1D8CF3745549C83
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: c9ec0fd9-47e0-412d-b035-7a11df06d242
Faulting package full name: Microsoft.FlightSimulator_1.27.21.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

My laptop config:
AMD Ryzen 7 5800H
Nvidia gforce rtx3070 8Gb
32GB memory

I hope ther will be a fixe soon :frowning:
Greetings from the Netherlands,
Ed

1 Like

Click the friend’s location on the global interface to set the departure place to flash back

I’m on Xbox series X. My first 4 flights after SU10 worked perfectly and looked amazing. Today I have had 2 CTD on the runway prior to takeoff. Both in Airbus A319 flying routes in Europe. I was hoping this stability issue was fixed. Prior to SU10, I had 18 flights in a row with CTD either on the runway prior to takeoff, or 300 ft from landing, or the loading screen would freeze up and I would have to exit the sim. Enjoy the sim very much. Let’s hope Asobo gets this CTD problem figured out. All occurred with Airbus A320,A321.

1 Like

Hi Ed, (leuk een naamgenoot).

There seems to be a problem with the latest Windows-11 update 22H2. If you updated your Win11 version with this latest update you can try to roll-back to the previous situation. Nvidia is aware of this problem (which only seems to occur with Nvidia GPU’s). There will be a fix ‘soon’.
I’m not sure if this can be the cause of your problem but it could be.
Goodluck,
Ed

1 Like

Same for me - everything worked in SU9

SU10 i installed after upgrading to latest Windows 11 (was 10 in SU9)

Updated to latest Geforce and Graphic Drivers

Checked all Motherboard Drivers and Windows etc etc updated

Not overclocking

Tried safe mode

Removed Community folder

2 new installs of the SIM

Still get to “Ready to Fly” and can see the airport (various airports tried) once clicked screen stutters for a 1 second and CTD no error message or anything

12900K
3080ti
32gb DDR5
1500 Watt Bequiet Dark Power 12
Asus z690 Formula Rog
1tb 980 PRO sim game files

2 Likes

Hi… after su10, my ctds frequency leveled up, specially with the asobos A320n… i simply cannot comolete one single fly with it… and i dont know what to do… pls somenone Help! I play on Xbox S

‘Quit to desktop’ then clicking OK on message 'sure you want to exit flight simulator ’ doesn’t respond, freezing all other options. Reset or task manager are the only options for me at this point. I have also noticed after apparently having shut down FS, and then trying to relaunch get the message FS is already running. But it isn’t or at least I can’t see it.
Ryzen 5 5600X 32GB DDR4 RTX2060 1GB NVME
PS Hi Hank1284 welcome welcome. You might spend a while here! All part of the fun! Afraid Im a PC user, but sure some other kind folk who knows what an Xbox is will help. ! :slight_smile:

Exact same problem here :sob:

Hi, after SU10 update, I’ve had two CTD at the end of two flights; the Event log is as follows:


Thanks for any help,
Fulvio

Same problem!

I had just got to the gate after a 3.5 hr flight, CTD

Faulting application name: FlightSimulator.exe, version: 1.27.21.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.27.21.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000073d159
Faulting process id: 0x6ac8
Faulting application start time: 0x01d8d4052e116bec
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 69c2786f-d4de-4be2-8b34-3381ad141154
Faulting package full name: Microsoft.FlightSimulator_1.27.21.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Hello guys,
This workaround worked for me :slight_smile:

1 Like

Getting the same on new pc everything is upto date not updated laptop to test if it works yet but will try later but i can fly topgun training etc its just when i pick any airport go into cockpit it crashes.

Faulting application name: FlightSimulator.exe, version: 1.27.21.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.27.21.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001b40cd2
Faulting process ID: 0x3c24
Faulting application start time: 0x01d8d90ba744ea3b
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 31e69803-9c48-4778-aafd-cc22e91bc071
Faulting package full name: Microsoft.FlightSimulator_1.27.21.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Thanks Byothe1, that workaround worked!

If anyone fixing this issue sees this, I had the same issue, every single time I got a CTD on “Ready to Fly” button. Error:

Faulting application name: FlightSimulator.exe, version: 1.27.21.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.27.21.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001b40cd2
Faulting process id: 0x5b80
Faulting application start time: 0x01d8e0a3a6828046
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: f4cb5bc1-c2a4-4a83-b38e-c86ddbdcf248
Faulting package full name: Microsoft.FlightSimulator_1.27.21.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

System:

OS: Windows 11 Pro 64-bit (10.0, Build 22000) (22000.co_release.210604-1628)
Motherboard: ASUS TUF GAMING H670-PRO WIFI D4
BIOS: 2004 (type: UEFI)
CPU: Intel i7-12700K
RAM: 32GB
GPU: ASUS TUF GeForce RTX 4090 OC
PSU: Seasonic Focus GX 850W Gold

4090 : ~500W ( If I read OC, who knows, may be more )
i7-12700K : ~ 200W
MB: ~50W
RAM , SSD, whatsever: ~50W

ups

A bit off topic, it’s not causing the “Ready to Fly” crash issue. Measuring with a hardware meter, the total system draw is never over 550W in MSFS, haven’t seen any game so far to pull more than 600W. Running a GPU and CPU stress test at the same time is a different story, but hardly a use case I care about until some reasonable priced PCIe Gen 5 PSU enters the market :slight_smile:.

why off-topic ?.. you reported about a CTD and we know some cases where the PSU was relevant and caused a game crash because it affects e.g. the gpu. The systems today, in special the rtx cards and more in special these “4090 OC”, have often short very high peaks ( which no watt meter can show you ) in how much power they need and 850W for your system is a very edge case ( I would say it would b e already edge for a 3090 TI). At least it was one possible reason I mentioned. So may be a limitation in fps ( e.g. 30 ) can be a test worth :wink:

But of course there are other reasons as e.g. the post which was already linked, or invalid app-data, or google-maps-add-on, and all of that.. ( lots of topics in forum )

PS: as these reason exist the new atx norm, where the gpu reports back the power-consume and the psu report what it can deliver. Also because the gpu manufactors are not able to produce power-circuts with less power-spikes, the new PSUs must react much faster and much more tolerant on power spikes