Crash to desktop without error message

I use to suffer tons of CDTs which i never use to get with xplane…what seemed to work for me was capping my boost on my ryzen 5 3600 to 4000mhz and manual voltage using ryzen master. Not had a CDT since fortunately. Just thought id share incase someone has similar cpu based issue. I know i should RMA my cpu but CBA to wait forever with no PC

That should not be the solution. If a software ran perfectly and it suddenly stops working although nothing was changed on the computer, then why mess with voltages? Makes no sense. Of course, if the software does not run well right from the very beginning then we can assume it has to do with the system. But it is not the case for the majority of us.

1 Like

Although the main menu CTDs still happen frequently, I got the JF Piper 28 Arrow a couple of days ago and thankfully it doesn’t seem to crash for me (unlike the CJ4 WT which crashes 100% of the time since my issues began).

However there are heavy stutters every 20-30 minutes though, as the screen completely freezes for a second and then resumes. Other than that it’s an excellent experience. After 3 hours of flying with the Arrow, I’m now fairly confident I won’t be getting CTDs out of it. Of course things can change, like they already have a few times now.

I assume you didn’t mean to reply to me since I don’t mess with my voltage or overclock anything.

1 Like

No, sorry, it isn’t aimed at you!

1 Like

everything said my friend, I also had no CTD until Update

I know the problem is with microsoft and I am not going to submit to making adjustments to the machine, it is not my job, we are end users.


we have a exaclty the same problem and the same playing time before the problem

Just had my first CTD in this sim. I think definitely related to the hotfix patch. Nothing else changed.

Faulting application name: FlightSimulator.exe, version:, time stamp: 0x60783c14
Faulting module name: VCRUNTIME140.dll, version: 14.28.29231.0, time stamp: 0x5f4c66c9
Exception code: 0xc0000005
Fault offset: 0x0000000000001550
Faulting process ID: 0x5a4c
Faulting application start time: 0x01d7355bae4ad270
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.15.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.29231.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll
Report ID: 0c058685-f244-4f82-b696-ae6eca819f88
Faulting package full name: Microsoft.FlightSimulator_1.15.8.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

After a few days of CTD free simming, it happened again to me today in the JustFlight Arrow III, straight and level half way between LFKB and LIRJ when I opened the ATC menu and clicked ‘airports further than you’ :pensive:


So now this game is unplayable due to CTD until Microsoft releases the update in 20000 years? Are we still in BETA version??

1 Like

I just purchased a 3090 (which arrives tomorrow), so that I can enjoy the continued experience of the CTD in MSFS2020, but in a whole new level of detail and performance.


You’re being very generous, it’s clearly still in alpha.


LOL I thought that CTDS were over since i made a clean install of gpu drivers and now all of a sudden i tried to fly with a bonanza in the Grand Canyon and i got CTD without error just by being in the airport

Third time after hotfix i have CTD during a flight after 1h.

1 Like

Before the last update I rarely had CTDs…now I’m having them with almost every flight.

1 Like

First CTD after a long time (at least where are no scenery addons involved). Was about 1hr in the sim. Flew the Justflight PA28, crash was enroute over the Lake District, UK. Will do this leg again tomorrow to see if there is a reproducable issue there.
Eventlog nothing special

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version:, Zeitstempel: 0x60783c14
Name des fehlerhaften Moduls: FlightSimulator.exe, Version:, Zeitstempel: 0x60783c14
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000016df8a
ID des fehlerhaften Prozesses: 0x31a4
Startzeit der fehlerhaften Anwendung: 0x01d73612377439fe
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.15.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.15.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: 8bc15333-6d30-4968-9ed3-fa240ef07531
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.15.8.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

Crash on final, runway 22L at KBOS, about 2 miles out. I was also in the JF Arrow, with the GTN 750.

Report.wer.pln (32.8 KB)

Faulting application name: FlightSimulator.exe, version:, time stamp: 0x60783c14
Faulting module name: FlightSimulator.exe, version:, time stamp: 0x60783c14
Exception code: 0xc0000005
Fault offset: 0x000000000016df8a
Faulting process ID: 0x4364
Faulting application start time: 0x01d7362b6f769192
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.15.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.15.8.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 1f8d8923-f5de-460e-bba7-3b420dd20fbb
Faulting package full name: Microsoft.FlightSimulator_1.15.8.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Fault bucket , type 0
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.FlightSimulator_1.15.8.0_x64__8wekyb3d8bbwe
P2: praid:App
P4: 60783c14
P5: FlightSimulator.exe
P7: 60783c14
P8: c0000005
P9: 000000000016df8a

How about a SYMBOL TABLE for each Update ?
Then Users could maybe be able to submit meaningful Crash analysis reports .
(to both Zendesk, as well to share with the Community)

I’m having them ( CTD ) after about 30 minutes. I’m running the older version of the Nvidia driver and am wondering if I change to the latest driver it will make any difference in the CTD. Any ideas?

1 Like

My Latest CTD – with WinDbg Analysis


Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\ms\AppData\Local\CrashDumps\FlightSimulator.exe.10024.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 19042 MP (8 procs) Free x64
Product: WinNt, suite: SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Debug session time: Tue Apr 20 23:44:26.000 2021 (UTC - 4:00)
System Uptime: not available
Process Uptime: 0 days 0:09:21.000

Loading unloaded module list

This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(2728.43e8): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
00007ffd`cff4d874 c3 ret
0:000> !analyze -v

  •                                                                         *
  •                    Exception Analysis                                   *
  •                                                                         *

*** WARNING: Unable to verify checksum for WwiseLibPCx64P.dll
*** WARNING: Unable to verify checksum for WTF.dll
*** WARNING: Unable to verify checksum for CoherentUIGT.dll
*** WARNING: Unable to verify checksum for XPlatCppWindows.dll


Key  : AV.Fault
Value: Read

Key  : Analysis.CPU.mSec
Value: 7968

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 60296

Key  : Analysis.Init.CPU.mSec
Value: 312

Key  : Analysis.Init.Elapsed.mSec
Value: 6766

Key  : Analysis.Memory.CommitPeak.Mb
Value: 286

Key  : Timeline.Process.Start.DeltaSec
Value: 561

Key  : WER.OS.Branch
Value: vb_release

Key  : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key  : WER.OS.Version
Value: 10.0.19041.1

Key  : WER.Process.Version





CONTEXT: (.ecxr)
rax=00000198353e0000 rbx=00000198353e0000 rcx=0000019812e1c060
rdx=0000000000000000 rsi=00000199cfd80310 rdi=0000019812e1c060
rip=00007ff6b92cdf8a rsp=0000000d4fbfed70 rbp=0000000d4fbff7b9
r8=0000000000003bfc r9=00000000000312a4 r10=00007ff6bf41639c
r11=0000000d4fbfe200 r12=0000000000000000 r13=00007ffd82f30000
r14=0000019a4f6f5ef0 r15=00000100000001b3
iopl=0 nv up ei pl zr ac po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010256

**00007ff6b92cdf8a 803c1300 cmp byte ptr [rbx+rdx],0 ds:00000198353e0000=??

Resetting default scope

ExceptionAddress: 00007ff6b92cdf8a (FlightSimulator+0x000000000016df8a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000198353e0000
Attempt to read from address 00000198353e0000

PROCESS_NAME: FlightSimulator.exe

READ_ADDRESS: 00000198353e0000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.


EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 00000198353e0000

IP_ON_HEAP: 000000003cd00c88
The fault address in not in any loaded module, please check your build’s rebase
log at \bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.


0000000d4fbfed70 000000003cd00c88 : 0000000000000000 00000197e0034730 00007ff6ba47a9ac 00000197e73012e0 : FlightSimulator+0x16df8a
0000000d4fbfed78 0000000000000000 : 00000197e0034730 00007ff6ba47a9ac 00000197e73012e0 00007ff6b92cb4be : 0x3cd00c88

SYMBOL_NAME: FlightSimulator+16df8a

MODULE_NAME: FlightSimulator

IMAGE_NAME: FlightSimulator.exe

STACK_COMMAND: ~0s ; .ecxr ; kb

FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_FlightSimulator.exe!Unknown

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release


OSNAME: Windows 10

FAILURE_ID_HASH: {b196447b-0ec2-4af8-aed4-49f7b9178656}

Followup: MachineOwner