0xc0000005 CTD every time I try to start MSFS

[Soulflight]

I just got back from 2 weeks offline and tried to start MSFS, yesterday it worked fine, i downloaded the recent WU and mandatory update. Now I cannot get to the main menu anymore. Loading finishes and then MSFS crashes without any error. Event log shows this:

 

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.37.19.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.37.19.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000bee81e
ID des fehlerhaften Prozesses: 0x0x3120
Startzeit der fehlerhaften Anwendung: 0x0x1DAF4A7B1461F4A
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: 723bb2d6-1ccb-486d-956d-f02d071da89e
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

 

I used addon manager already to deactivate all addons, but even plain vanilla MSFS crashes the same way.

sfc /scannow also didnt show any corrupted system files.

Some threads I found about it online point towards memory timing problems but I didnt change anything recently. I use 2x16GB DDR4-3200 sticks and applied the corresponding preset in my BIOS setup. Other than that I didnt make any changes and didnt OC anything.

So nice, you have one day off and you spend it downloading updates and then troubleshooting, fml. 😄

[Bob Scott]

If you suspect a memory issue, a quick run of Memtest 86+ should answer that question.  An hour or two of testing should answer the mail given that your problem is consistently repeatable.  Memory and a CPU's IMC can degrade over time without making any changes, and voltages on the motherboard can drift as the voltage regulator components age.

An overclock that's on the ragged edge of stability can also work for some time and then start throwing errors with just a slight amount of degradation in any of a number of components.

[Soulflight]

 

5 hours ago, Bob Scott said:

If you suspect a memory issue, a quick run of Memtest 86+ should answer that question.  An hour or two of testing should answer the mail given that your problem is consistently repeatable.  Memory and a CPU's IMC can degrade over time without making any changes, and voltages on the motherboard can drift as the voltage regulator components age.

An overclock that's on the ragged edge of stability can also work for some time and then start throwing errors with just a slight amount of degradation in any of a number of components.

memory issues were not really my suspicion as the system itself is very stable with anything except MSFS. Its just something i read that 0xc000005 points towards memory instability. But I just ran a full memtest, which took 4,5 hours and returned 0 errors, so nope...

[Bob Scott]

Well, unfortunately C0000005 errors are like running a fever...it tells you something is wrong, but not what.  If the computer passes basic diagnostics, like MemTest 86+, a moderate-length run of a stress test, etc, then it points to a software problem.

If you have rolling cache enabled, try clearing it and loading the sim without it active.  And clear out your directx shaders as well.  Is your video driver up to date?

Do you have a backup of MSFS made at a time it was working?

[Soulflight]

Got back from work today and did some checking. Updated nvidia driver the usual clean way without any changes.

But I can get into safe mode! This is strange because I deactivated my addons already using the addon manager. But there are some which are installed by their own installers and are still present in the community folder.

Is there anything else MSFS safe mode changes when activated, except for not loading addons inside the community folder?

[Soulflight]

After several hours of gradually removing stuff from the community folder and subsequent testing i found out that it seems to have been caused by a navigraph AIRAC I had installed. Weird enough this causes such a crash but its gone when removed.