After Update #5, constant CTD when about 5 minutes into flight while in VR mode

After update #5, I’m getting a CTD after approximately 5 minutes into any flight. I’ve updated my nvidia driver, reset the rolling cache, my community folder is empty. I’ve never had this issue before so I’m sure the update caused this.

I’ve tried different locations, stock planes (C152, C172).

Obviously the program is unusable at this point.

Specs:
i9-9900K
NVIDIA 2080 Super
32GB RAM
HP G2

Here is the event log output.
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: 0x2ea0
Faulting application start time: 0x01d78422b5ea406a
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: 7a876000-e9f6-4f29-a493-9c29034b4e07
Faulting package full name: Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Happened to me 3 times today, during flights of various length. I also agree that it wasn’t nearly this bad with the previous build. Apparently the 0xc0000005 exception code crashes have gotten worse for some, including me. :frowning:

Here’s my report:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0x27dc
Faulting application start time: 0x01d7841d5a097526
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: unknown
Report Id: 88e4ea78-25d5-45b2-90ea-1df6d266edd0
Faulting package full name: Microsoft.FlightSimulator_1.18.13.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

First one earlier that I captured a pic. . .

Then followed the advice of some of the folks that reported these things helped them:

  1. Shut off all AI.
  2. Use DevMode to see the main thread. Not sure how I can not be bottlenecked by my CPU though, since I am running a 3090, and have it stock speeds.

My computer specs are similar to yours:
i9-9900K
RTX 3090
32GB RAM
Rift S

I get only about min in and boom.

It happened while taxiing, flying over water (very little scenery), over the country side, and over Brooklyn.

Anybody have any idea what Exception code: 0xc0000005 means?

Grrrrrrrr I wanna fly.

I never had any CTD since I purchased MSFS2020 last year. Yesterday, I experienced multiple CTDs after the SU5.
While some were random, I could note that others were due to my actions: I kept on changing settings and load flights, and even change settings during a flight.
I have only 16GB RAM, GTX 1080, Ryzen 5 3600 and a Quest 2 - Bing is ON as well as PG; so I can’t really complain as the sim works better now.

I now switch to VR only after loading the flight - I don’t make changes to settings while in VR.
I also don’t have other software running in the background apart from the oculus desktop software - the OTT is not even on now.

So far so good…

I need OTT because of awful tearing I get with ASW and the Rift S that I can’t seem to shut off without OTT. Doh!

Underclocked RAM? No effect. :frowning: No AI? No effect. :sob:

I am wondering if this is down to issues with the microsoft servers and that is not being handled properly. I flew around and around my home airfield within 5 miles for about 40 minutes and no problem, but as soon as I ventured further away it went bang. One thing that consistently broke it was getting the map up and resizing it horizontally. In VR I put it on the passenger seat and turn on the lines. It now goes bang if you do that. So note to self - do that first before take off.

The same, 7/10 flights = CTD for me, Community folder empty, AI the whole traffic is OFF.
Before SU5 near no CTD during last ONE year!

1 Like

I wonder how u guys did not have CTD for such a long time before SU5.

My story;
Bought Quest 2 ….3.5 months back
Bought MSFS 3 months back
CTD after CTD.
REINSTALL uninstal windows a trillion times
Tweaked GPU trillion million times
Read the forums for answers until there was no tomorrow.
Updated to SU5 yesterday.
I am currently reinstalling windows.

My pc specs
Z490 Aorus ultra
I7 10700k
1080ti 11gb amp extreme core

1 Like

Is everyone running HAGS? I was getting crashes randomly, i turned HAGS ON & it got much worse.
So if its ON turn it off it may help reduce the crashes.
I never got a single crash b4 this update.

I have gotten up to 11 minutes before CTD!! Also, after one CTD I got this message:
Flightsimulator.exe Application Error
The instruction at 0x00007FF750711A15 referenced memory at 0x00000196F891D000. The memory could not be read. –
Does anyone [Asobo!] know anything about this? Does it mean anything? I have also emptied my Community folder to no avail. Makes no difference.

What is HAGS? :face_with_monocle:

Same here, anywhere from 5-30 mins and CTD
i9 9900k
32g ram
evga 3090 ftw3
HP G2

Sometimes it even CTDs on the flight loading screen.