Do you have any add-ons in your Community folder? If yes, please remove and retest before posting.
Are you using Developer Mode or made changes in it? no
Brief description of the issue: ctd mid flight
Provide Screenshot(s)/video(s) of the issue encountered: Log Name: Application
Source: Application Error
Date: 3/23/2021 11:13:42 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-HJP64PA
Description:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6040b793
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6040b793
Exception code: 0xc0000005
Fault offset: 0x0000000003bf7690
Faulting process id: 0x38dc
Faulting application start time: 0x01d71fecebe522c6
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 888329c9-550d-429d-ba91-a773d41f78de
Faulting package full name: Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
1000
0
2
100
0
0x80000000000000
19366
Application
DESKTOP-HJP64PA
FlightSimulator.exe
0.0.0.0
6040b793
FlightSimulator.exe
0.0.0.0
6040b793
c0000005
0000000003bf7690
38dc
01d71fecebe522c6
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
888329c9-550d-429d-ba91-a773d41f78de
Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe
App
Detail steps to reproduce the issue encountered: normal flight
PC specs for those who want to assist (if not entered in your profile)
Processor Intel® Core™ i7-9700K CPU @ 3.60GHz 3.60 GHz
Installed RAM 32.0 GB
GeForce RTX 2080 Super
System type 64-bit operating system, x64-based processor
Window 10
Did you submit this to Zendesk? If so, what is your ticket #? no