Here is a first. Starting MSFS 2020. Got to the screen where it says start flight, and it CTDs.. Never even got to the parking area. 

 

Log Name:      Application
Source:        Application Error
Date:          3/5/2021 8:05:21 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-7AJT4EM
Description:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6038d404
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6038d404
Exception code: 0xc0000005
Fault offset: 0x0000000000185950
Faulting process id: 0xa80
Faulting application start time: 0x01d711bf4eb81f83
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: af5b8836-b18d-43ce-8d46-327531fb6e8f
Faulting package full name: Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-03-05T13:05:21.2358109Z" />
    <EventRecordID>7447</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-7AJT4EM</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FlightSimulator.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>6038d404</Data>
    <Data>FlightSimulator.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>6038d404</Data>
    <Data>c0000005</Data>
    <Data>0000000000185950</Data>
    <Data>a80</Data>
    <Data>01d711bf4eb81f83</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>af5b8836-b18d-43ce-8d46-327531fb6e8f</Data>
    <Data>Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>

Welcome to the Club, Bob!

11 hours ago, Dillon said:

I'm another member of the CTD party.  I found updating my Rolling Cache with each new update helps.  If I get a crash over an area once I usually don't have that issue again in the same area as whatever was the problem is copied into Rolling Cache.  If the problem persists I create a flight plan away from that spot.  UK update seems to have improved things but deleting and rebuilding rolling cache is a must.

Very good advice. I forgot about this. Never had an issue with other updates, so I did not think of doing it. Will try this later today.

30 minutes ago, David Roch said:

Can you please elaborate a little bit?
Thanks!

I turned off Azure, deleted and left rolling cache off, nothing in the community folder other than the A320nx, EGKK and Lima airports. ( I use the addon Linker ) AMd 3800x here 32gb DDR4, and M570 Pro M/Board, 2x Nvme gen 4 drives.) Latest bios, and WIN 10, MSFS , Xbox app all upto date.

Perfect, thanks! 😉

Thing is, if you have to disable key features, mess with CPU settings, have no addons whatsoever, etc., it's a broken application and not user related. I have games and applications that are far more demanding than MSFS and never do they ever CTD. Asobo really need to sort this out, especially considering what we paid for this software. 

Edited March 5, 20215 yr by Jeeper
Spelling

2 hours ago, Jeeper said:

Thing is, if you have to disable key features, mess with CPU settings, have no addons whatsoever, etc., it's a broken application and not user related.

Understand your frustration but here's the difficult bit - there are also overclocked systems with addons that aren't CTDing, so pinpointing the cause is even more sticky.

I'll add my setup below if helps with troubleshooting:

- Sim installed on separate drive outside of Program Files (dedicated SSD)

- Sim: Rolling cache enabled @ 32GB on the same dedicated drive as the sim

- Sim: Manual cache disabled

- Sim: All data services enabled

- Sim: Traffic / multiplayer enabled

- Win10: Running latest feature update and all optional updates (that's where a lot of driver updates sit)

- Win10: Game Mode enabled / background game capture recording disabled

- Win10: XBox networking services show connected with NAT @ moderate (doesn't seem to affect the sim)

- Win10: Hardware-accelerate GPU scheduling enabled

- Win10: MSFS set to high-performance in graphics performance settings

- Win10: Audio - was getting intermittent audio clicking but solved by installing motherboard-specific Intel RST drivers for the AHCI controller, and plugging all USB devices into ports from the Intel USB controller; audio drivers

- System and GPU overclocked and stable in AIDA64

Update, second flight all ok,here's hoping.

I just realized that in the last day and a half, MS 2020 has been slower loading to opening menu. It has also crashed several times, before I could even hit Fly Now. I started thinking, something has changed, it never did that before. Then I realized that i had installed the G 530 latest patch in the community folder. It was the only thing in there besides a Mooney Repaint. I removed the 530 patch, and now it starts up normally. Go figure....

i never used rolling cache, nothing inside my communtiy folder cept a few airplanes,

no CTD since weeks ago

But maybe because  fly VR. ?

I just had the same after a 4 hour flight crashed on final ahh the pain.

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6038d404
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6038d404
Exception code: 0xc0000005
Fault offset: 0x00000000008cfe1f
Faulting process ID: 0x21f0
Faulting application start time: 0x01d711e4a731b08c
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 9a2be0c7-e3d8-49ef-866c-8eee46c842c6
Faulting package full name: Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

This morning (as suggested by Dillon) I deleted my 8Gb rolling cache and then reenabled/rebuilt it. Created a flight plan away from where I had been flying. It ran great. Did two more flights where I had been flying and no problems. When I said before that 30% of my flights end in a ctd. I was exaggerating, my wife says I do that. Its closer to 15% to 20%.  Only time will tell if this is *my* fix. I jinxed myself last time so I do not know why I am here. Again my problem is a ctd with vcruntime140.dll.

My specs:
i7-9700F
Asrock B365M Pro4 (1 or 2 bios behind)
Gigabyte 2070 super no OC
16Gb
48" 4k HDR TCL 49S405
NVidia HDMI sound 
NVidia Driver version 460.89 (think I lied in an earlier post about the version, wife says I do that too)
MSFS at 2K Ultra/No VSync (40-50fps in most...15fps in Manhattan - at these settings.)
All data services on/Live traffic/Multiplayer
Still have Azure turned on (testing one thing at a time)
Win Game mode on
Hardware GPU scheduling on

Never installed a single mod only the freebies from the marketplace. I wanted to, but it was too stable and I did not want to just yet.
 

Well I thought I had solved the problem, with the Garmin fix, but it is back again. This simulator has more bugs than a flop house bed. I am going to seriously consider going back to P3D, because this just isn't any fun anymore, it looks great until it screws up. . 

Edited March 6, 20215 yr by Bobsk8

12 hours ago, Bobsk8 said:

Here is a first. Starting MSFS 2020. Got to the screen where it says start flight, and it CTDs.. Never even got to the parking area. 

 

Log Name:      Application
Source:        Application Error
Date:          3/5/2021 8:05:21 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-7AJT4EM
Description:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6038d404
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6038d404
Exception code: 0xc0000005
Fault offset: 0x0000000000185950
Faulting process id: 0xa80
Faulting application start time: 0x01d711bf4eb81f83
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: af5b8836-b18d-43ce-8d46-327531fb6e8f
Faulting package full name: Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-03-05T13:05:21.2358109Z" />
    <EventRecordID>7447</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-7AJT4EM</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FlightSimulator.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>6038d404</Data>
    <Data>FlightSimulator.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>6038d404</Data>
    <Data>c0000005</Data>
    <Data>0000000000185950</Data>
    <Data>a80</Data>
    <Data>01d711bf4eb81f83</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>af5b8836-b18d-43ce-8d46-327531fb6e8f</Data>
    <Data>Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>

I have been getting this from the moment the hotfix was installed.

Getting it with and without community folder active.

Getting it with mixed reality installed and uninstalled.

Graphics drivers changed, 

Settings in MSFS turned down. Nothing makes a difference. When it finally lets me get in a cockpit it its a coin toss whether you complete the flight before another CTD.  

Weird how some folks have no problem, but the rest of us....

I am so frustrated I haven't even reported this latest fiasco, cause eventually this will get fixed, only for something show stopping to be created from that fix, for some other  users, or us all over again.

Lets just keep or fingers crossed, that sim update3 takes care of some of these.   

1 minute ago, Romeo_Tango said:

I have been getting this from the moment the hotfix was installed.

Getting it with and without community folder active.

Getting it with mixed reality installed and uninstalled.

Graphics drivers changed, 

Settings in MSFS turned down. Nothing makes a difference. When it finally lets me get in a cockpit it its a coin toss whether you complete the flight before another CTD.  

Weird how some folks have no problem, but the rest of us....

I am so frustrated I haven't even reported this latest fiasco, cause eventually this will get fixed, only for something show stopping to be created from that fix, for some other  users, or us all over again.

Lets just keep or fingers crossed, that sim update3 takes care of some of these.   

I hope your right. Tonight I finished a flight hat I started a week ago, after 5 attempts, from EGSC to EGCC.  All the way, I am holdingmy breath that the sim won't crash again. Luckily, this time I made it.