1.37.8.0 CTD with every single flight

Sim Update 15 Beta CTDs
, ,
1

Have you disabled/removed all your mods and add-ons?

Enabled

Are you using Developer Mode or made changes in it?

Happens with/without

Brief description of the issue:

CTD almost immeadiately on every single flight. 3 flights, three CTD (see below)

Detailed steps to reproduce the issue encountered:

Happens every time, with VR within 1-2min, without after ~5min

PC specs and/or peripheral set up:

5800 and RTX4800, 32GB RAM

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

1309923317488086963, Typ 4, 1199392694677716710, Typ 4, 1199392694677716710, Typ 4

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

2

Another 4 flights, another 4 CTD with always the same bucket:

Fehlerbucket 1199392694677716710, Typ 4
Ereignisname: APPCRASH
Antwort: Nicht verfĂĽgbar
CAB-Datei-ID: 0

Problemsignatur:
P1: FlightSimulator.exe
P2: 1.37.8.0
P3: 65eeffba
P4: StackHash_e331
P5: 10.0.22621.3235
P6: a2c4352c
P7: c0000374
P8: PCH_B7_FROM_ntdll+0x000000000009FEC4
P9:
P10:

3

Which a/c and airports are you using?
Have you just joined the Beta or have you been using it for a while and CTDs have just started happening?

Might help to narrow down the issue.

4

Better try it first with an empty community folder. Hasn’t been the first time for me to get CTD’s because of some addon. I always try it quickly by just renaming the community folder first so you can put it back after in a sec.

If you don’t get any CTD’s with an empty community folder then you can start hunting for the bad one. I do this by copying half my addons to another folder and see in which part something is wrong. You can narrow it down pretty quickly this way.

1 Like
5

Joined Beta since the beginning and always hapenend. Will give it a try today with the empty community folder.

6

Chances are it’s an incompatible third party addon causing the crashes.

7

No, also with an empty Community folder there is the same behavior. Crashes within seconds to minutes with always the same bucket. Here the latest:

Fehlerbucket 1199392694677716710, Typ 4
Ereignisname: APPCRASH
Antwort: Nicht verfĂĽgbar
CAB-Datei-ID: 0

Problemsignatur:
P1: FlightSimulator.exe
P2: 1.37.8.0
P3: 65eeffba
P4: StackHash_e331
P5: 10.0.22621.3235
P6: a2c4352c
P7: c0000374
P8: PCH_B7_FROM_ntdll+0x000000000009FEC4
P9:
P10:

8

If you have any Marketplace addons, they could also cause that.
You can confirm that by starting the sim in safe mode.

9

Does this happen with all aircraft and airports?

From you bug report it looks like you’re using VR. Do you get the same results without?

10

I’ve heard people complaining about CTD’s with the Dune expansion, did you install that one?

If you still have crashes in MSFS safe mode you might want to verify the stability of your system. Especially try a RAM test and some benchmark tool pushing your system to the limits. Are you overclocking your CPU or GPU? If so you could try without overclocking. Are your system temperatures within normal range?

Also check your Windows installation:

https://www.geeksinphoenix.com/blog/post/2022/02/24/how-to-check-and-repair-system-files-in-windows-11

If all else fails you can always try to reinstall MSFS and as a very last resort try a clean installation of Windows. But better wait to see if the release build still gives you CTD’s before going that far.

11

The game up to now for me was as smooth as silk but since the update this morning I have had a CTD and stuttering and a drop in frame rates. a bit disappointed sadly. Hope they can fix it quickly.

1 Like
12

Having this exact same issue over and over for the last six weeks or so when fying in VR. Up until around mid january flying in VR worked fine for almost all flights. Normal flight durations: 60-90 mins. Now with these CTD’s: 8 mins max, usualy around 5 mins.

When flying without VR (why would you want that once hooked on VR :slight_smile: ), the same flight runs smooth, even on Ultra settings. It looks fantastic on a monitor, but it’s just not VR…

Have tried rebuilding the entire stack (both Win11 & MSFS) more than a dozen times, so my system could not be more vanilla.

My config:

[Hardware]
CPU: AMD Ryzen 9 3900X 12-Core Processor
GPU: NVIDIA GeForce RTX 4070 Ti
NVidia Driver Version 551.86
HWS_Enabled=1
Memory: 32GB

[VR set]
Model: HP Reverb G2
Have tried both WMR portal and SteamVR as well
OpenXR for WMR developer tools enabled, have tried without as well with same results

[MSFS]
BuildVersion=“1.37.9.0”, had the same issue with build 37.8, 37.7 and even before I entered SU15 beta.
Tried D3D12 and D3D11 as well, same result
DLSS enabled, have tried TAA as well, same result

The exception code is almost always 0xc0000005 (access violation / access denied).
Sporadically I get 0xc0000409 (Buffer Overflow Exception for 64-bit applications).

Alls signs indicate a memory leak in the “VR lines of code”, simply because the whole thing works fine outside VR.

The sad thing is that even while flying in VR is the ultimate experience, it’s still a niche in the FlightSim world, which explains why VR receives (too) far less developer attention.
I understand that Asobo/Microsoft focus on the larger part of the market, but guys, you cannot leave us VR forerunners dangling!

13

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

Yes, as described in my reply.
This is a list of a few fault bucket entries in the WER which resulted in an APPCRASH with exception code 0xc0000005:
Foutbucket 1417751604115941837, type 4
Foutbucket 1164240508398525552, type 4
Foutbucket 1788669631525869689, type 4
Foutbucket 2296468849755647796, type 4
Foutbucket 1701016865665084306, type 4
Foutbucket 1276364370937964841, type 4
Foutbucket 1159745975004421193, type 4
Foutbucket 1211449679889257850, type 4
Foutbucket 1254877888855980011, type 4
Foutbucket 2153908470478635220, type 4
Foutbucket 1332348878437595395, type 4
Foutbucket 1491771502508150710, type 4
…etc., etc.

This is one fault bucket entry in the WER that resulted in an BEX64 event with exception code 0xc0000409:
Foutbucket 1595665587158094314, type 5

If relevant, provide additional screenshots/video:

14

All aircraft, all airports. VR lets it crash much faster, but it can happen without VR too.

15

Dune is installed. It behaves exactly like a RAM problem, but outside MSFS there is nothing causing problems. No overclocking and temperatures are quite cool, as I have a 5800/4080 setup running way below of what it could do.

16

The problems started with the first SU15 Beta and have not stopped ever since. Today I updated to 1.37.9 and I got a different bucket today:
1380490673824309001, Typ 4

17

I wish this was true but it is 1,000% the SU 15 beta.

I’ve flown for 3 years with minimal CTDs in this sim using all kinds of 3rd party planes/airports.

I decided to give SU 15 beta a whirl because I was excited for the changes it brings and every single flight CTD’d on departure.

Rolled back out of the beta and not a single issue.

2 Likes
18

But did you actually try it without those addons, and only default Asobo planes?

Think about it logically. Can you guarantee that all those addons are compatible with SU15?

If you can’t, a necessary diagnostic step is to remove them, and try again. If you didn’t even try, you can’t know.

2 Likes
19

Yes, I removed the complete content of the community folder.

2 Likes
20

Hi All,

Turns out there is always light at the end of the tunnel :slight_smile:

In my case: manually resetting the CMOS RTC RAM data solved all of my problems!!

My random but persistent crashes in VR and later on, also outside VR were caused by a conflict between on the one hand a firmware upgrade in the BIOS data that I performed around mid january for both the motherbord (Asus Prime X570-PRO) and the AMD chipset, and the BIOS setup data in CMOS at the other.
Manually resetting the CMOS by performing a CLCTR (shortcut two specifically located jumpers on the motherboard) and a reboot fixed everything!!

I never had expected that the root cause would be this deep, especially because the crashes occurred not very often in the short period after the firmware upgrade, but increased in number later on.

I bumped into the solution because I even replaced two memory banks and tried different timing frequencies that ended up in a completely dead PC that was unable to even start up. That forced me to manually reset the CMOS BIOS data by performing a CLRTC, shortcutting the two jumpers.

For those of you who run into the same kind of random, but persistent crashes in MSFS / VR, check to see if the solution that worked for me, might be a possibility for you to consider as well.

I sincerely hope that your situation will be resolved in time as well, because boy, did I miss flying in VR!!

2 Likes