CTD since, at least, SU5 with 0xc0000005

[Marvk4]

Are you on Steam or Microsoft Store version?

Steam

Do you have any add-ons in your Community folder? If yes, please remove and retest before posting.

No

Are you using Developer Mode or made changes in it?

No

Brief description of the issue:

Crashing to Desktop, most commonly in the Content Manager, but also while playing or before even having finished loading the menues.

Provide Screenshot(s)/video(s) of the issue encountered:

Not applicable, no error message shown.

Detail steps to reproduce the issue encountered:

1. Start the game
2. (game might crash while loading the menu)

or:

1. Start the game
2. Enter content manager
3. (game might crash while entering content manager)
4. Start a download
5. (game might crash while downloading)

or:

1. Start the game
2. Start a flight with any aircraft from any airport
3. (game might crash at any time while on the ground or flying)

PC specs for those who want to assist (if not entered in your profile)

AMD Ryzen 9 3900X
be quiet! Dark Rock Pro 4
MSI 450M Mortar MAX
G.Skill Trident Z Neo 32GB
ADATA XPG SX8200 Pro 2TB
Gigabyte GeForce RTX 2070 SUPER 8GB GAMING OC 3X
Fractal Design Ion+ 760W 80+ Platinum

Build Version # when you first started experiencing this issue:

At least 1.18.13.0, possibly earlier

Are you on the Steam or Microsoft Store version?

Steam

Did you submit this to Zendesk? If so, what is your ticket #?

126879

Steps I have tried so far:

• Safe Mode

• Delete Community folder

• Set Quality to low, apply, set Quality back to ultra

• Just set quality to low

• Clean reinstall of the game, run with nothing but base content installed

• Unterclock my GPU

• Update GPU drivers

• sfc /scannow

• DISM.exe /Online /Cleanup-image /Restorehealth (u/nAssailant)

• Game is installed on an NTFS drive (u/TempestTornado23)

• Installed the latest C++ Redistributables (u/TempestTornado23)

• Clear rolling cache and increase cache size (u/SmallTownTokenBrown)

• Limit Game to 30FPS via Nvidia Control Panel (u/nAssailant)

• Set pagefile size manually

• Completely reinstall GPU drivers

• Update All Microsoft Store Items

• Apply all outstanding Windows Updates

• Install English (United States) Voice Pack

• Synchronize Time Settings

• Set MSFS2020 to high performance in Windows

• Reinstalled all VS redistributables

Error shown:

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.19.9.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.19.9.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000001a0b677
ID des fehlerhaften Prozesses: 0x2590
Startzeit der fehlerhaften Anwendung: 0x01d7acac08ee3e1b
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Berichtskennung: 3087d498-e10e-438f-b976-6a3d27e81047
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

Additional Windows Error Reporting Information:

1:

Fehlerbucket , Typ 0
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: FlightSimulator.exe
P2: 1.19.9.0
P3: 00000000
P4: FlightSimulator.exe
P5: 1.19.9.0
P6: 00000000
P7: c0000005
P8: 0000000001a0b677
P9: 
P10: 

Angefügte Dateien:

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_FlightSimulator._f384cb0b55aefc014efcd0974570e5d6ede7e6_23eb822b_db4408d6-954c-4f8d-81c1-f451ce9970aa

Analysesymbol: 
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 3087d498-e10e-438f-b976-6a3d27e81047
Berichtstatus: 4
Bucket mit Hash: 
CAB-Datei-Guid: 0

2:

Fehlerbucket , Typ 0
Ereignisname: LiveKernelEvent
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: 141
P2: ffffa5829fec7460
P3: fffff80016332610
P4: 0
P5: 2694
P6: 10_0_19041
P7: 0_0
P8: 256_1
P9: 
P10: 

Angefügte Dateien:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20200824-0029.dmp
\\?\C:\WINDOWS\TEMP\WER-131577781-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0CD.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0CE.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0CD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0ED.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_58e0e603af4f918a1c1a3d2d6d8b7b1c2dc81c3_00000000_6741197b-1d39-4210-a6e9-d80b83d155e5

Analysesymbol: 
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 6741197b-1d39-4210-a6e9-d80b83d155e5
Berichtstatus: 2051
Bucket mit Hash: 
CAB-Datei-Guid: 0

3:

Fehlerbucket , Typ 0
Ereignisname: LiveKernelEvent
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: 141
P2: ffff928699a1f220
P3: fffff8048ec998bc
P4: 0
P5: 2590
P6: 10_0_19043
P7: 0_0
P8: 256_1
P9: 
P10: 

Angefügte Dateien:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20210918-1851.dmp
\\?\C:\WINDOWS\TEMP\WER-25141687-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAFD0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAFE1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAFF2.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB012.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_e03652c6eaf435c55776e4899151fbe68163440_00000000_84343a19-aad4-4d1d-97e8-1f7158178f93

Analysesymbol: 
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 84343a19-aad4-4d1d-97e8-1f7158178f93
Berichtstatus: 4
Bucket mit Hash: 
CAB-Datei-Guid: 0

4:

Fehlerbucket 1209728792312984238, Typ 4
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: FlightSimulator.exe
P2: 1.19.9.0
P3: 00000000
P4: FlightSimulator.exe
P5: 1.19.9.0
P6: 00000000
P7: c0000005
P8: 0000000001a0b677
P9: 
P10: 

Angefügte Dateien:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAD60.tmp.WERInternalMetadata.xml

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FlightSimulator._f384cb0b55aefc014efcd0974570e5d6ede7e6_23eb822b_db4408d6-954c-4f8d-81c1-f451ce9970aa

Analysesymbol: 
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 3087d498-e10e-438f-b976-6a3d27e81047
Berichtstatus: 268435456
Bucket mit Hash: 20624b1395a51f7ff0c9d1ed5c60b2ae
CAB-Datei-Guid: 0

5:

Fehlerbucket , Typ 0
Ereignisname: LiveKernelEvent
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: 141
P2: ffffa5829fec7460
P3: fffff80016332610
P4: 0
P5: 2694
P6: 10_0_19041
P7: 0_0
P8: 256_1
P9: 
P10: 

Angefügte Dateien:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20200824-0029.dmp
\\?\C:\WINDOWS\TEMP\WER-131577781-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0CD.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0CE.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0CD.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC0ED.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_58e0e603af4f918a1c1a3d2d6d8b7b1c2dc81c3_00000000_6741197b-1d39-4210-a6e9-d80b83d155e5

Analysesymbol: 
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 6741197b-1d39-4210-a6e9-d80b83d155e5
Berichtstatus: 2051
Bucket mit Hash: 
CAB-Datei-Guid: 0

6:

Fehlerbucket , Typ 0
Ereignisname: LiveKernelEvent
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: 141
P2: ffff928699a1f220
P3: fffff8048ec998bc
P4: 0
P5: 2590
P6: 10_0_19043
P7: 0_0
P8: 256_1
P9: 
P10: 

Angefügte Dateien:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20210918-1851.dmp
\\?\C:\WINDOWS\TEMP\WER-25141687-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAFD0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAFE1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAFF2.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB012.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_e03652c6eaf435c55776e4899151fbe68163440_00000000_cab_84343a19-aad4-4d1d-97e8-1f7158178f93

Analysesymbol: 
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 84343a19-aad4-4d1d-97e8-1f7158178f93
Berichtstatus: 2049
Bucket mit Hash: 
CAB-Datei-Guid: 0

[daveolej]

I had the same crash as you and basically did all the troubleshooting you did. A couple of days ago I decided to revert my bios settings to default. Haven’t had a single crash since then. I did have a slight CPU overclock and changed some other settings as well that I dont remember but it looks like defaulting the bios fixed it.

[udidwht]

I had 1 CTD ealier. I went in to ‘Controls’ and noticed duplicate axis assigned to throttle and stick (X-56 HOTAS). Could be related. I did not set them up this way. The recent updates may have changed them.

[Marvk4]

Thanks for your suggestions, but no luck.

[Marvk4]

No change in SU6. Haven’t been able to play for months. I followed all the steps, I did everything. Zendesk Support is just sending me boilerplate text blocks.

[ITDreamFly]

Hello @Marvk4,

sorry to hear that.
I do not have a solution for you, but maybe this can help: Unofficial Reference Guide to CTD Solutions

[Marvk4]

I was able to get past the initial loading screen thanks to this:

CTD during loading game even after clean install

UPDATE 2: I can now confirm it was a Steam save data corruption. My installation is fully working now after doing these several steps: Disable MSFS2020 Steam Cloud Backup Delete save data folder (C:\Program Files (x86)\Steam\userdata\ {steam user id}\1250410) Clear Steam Download Cache Relogin to Steam Recheck MSFS2020 Steam Cloud Backup is disabled Start the game I have to thank these two threads (which I think are caused by the same issue of this thread): EDIT: Fixed …

Unfortunately, I’m still crashing a few minutes into every flight with the exact same error messages in the event viewer.

[Kapzaisien]

can you go to nvidia control panel and enable “debug mode” under “help” at the top.
It’s weird it is showing kernel 141 and watchdog errors when you say everything is stock/default in bios?

[Marvk4]

I didn’t say everything was stock in the bios, but barring from XMP and (maybe?) AMD-V, I don’t remember touching anything.

What am I supposed to do after enabling debug mode? Just launch the game again and check the event manager?

[Kapzaisien]

Yes, try it with debug mode on first.

[EThommessen]

Sooo. This took a while to figure out. I have been having CTD since SU5. I have done everything mentioned on any forums, BIOS update, reinstall of the sim an even blank installation of windows. Uninstalled all drivers and other periferals.

I was thinking it was my screen ultrawide 5K, but this has been working well before SU5.

So this morning in pure desperation after months of CTDs. I dissconnected my Logitech MX keyboard and mouse, and plugged in my wired gaming keyboard and mouse, and voila. The sim has now been runnning steady for 6 hours.

I entered Dev mode and put on the fps monitor and noticed that is stated lagging and freezing when i switched the keyboard and mouse between computers.

Just putting it out there in case it can help anyone else.

[Marvk4]

The solution seems to be leaving debug mode on in the NVIDIA Control Panel.

So somehow, this is the fix?

I tried running it on my work laptop (where it didn’t crash) and then ran it again on my main machine, and it worked flawlessly. I thought that was the fix. However, after disabling debug mode, the game was once again crashing.

I will report back if it crashes again, but I really think this was the fix. I was able to play for more than an hour yesterday, before I wasn’t able to menu for 2 minutes.

Thank you so much.

[Kapzaisien]

I suspect that your GPU is going bad, or unstable at default clocks.
another fix is undervolting with msi afterburner.

[deluxeparkpt]

Two CTD’s when i finish the flight, turn off the engines and appear the flight menu automatically. When i press in “Continue”, CTD…

[Marvk4]

Doubtful. FurMark runs without issues for more than an hour. And I have tried underclocking, which also didn’t help. Also, this only happens in MSFS, every other game runs absolutely issue-free.

[CaptainSp0rk]

I’m also getting a CTD with error code 0xc0000005 in Event Viewer. After I reboot my PC, I’m usually able to fly for a few minutes before it crashes. If I relaunch after that however, I can’t get past the splash screen.

[CaptainSp0rk]

I tried basically everything to fix my CTD with error code 0xc0000005. What finally sorted it out was removing Realtek drivers from my PC and using the built-in drivers from Windows for that device instead.