First post. CTD on bone stock Legion, AMD r9, 3060, 32Gb RAM. No OC. No 3rd party - had to delete beloved Nxi. Even crashed on Xbox a couple weeks ago, first time since September. Almost always with a faster plane over detailed terrain. On landing in metro areas, last night was Baron over steep terrain in CA/NV. I fly longer flights, at least 1-4 hrs. Most CTD on landing. Last night 1st mid flight, as mentioned over mountainous terrain. Played game at medium graphics until recently, am trying Ultra but dialed down in terrain complexity and other resource heavy options. To date have never seen the error mentioned but completely forgot about the Event viewer, will have to start watching that. Very sick of these, honestly. Is there no automated error reporting?
PPS Windows 11. Stock drivers, never touch NVIDIA control panel.
Maybe for pc users could consider too…
Hi,
I found a solution for me, I hooe would help some of you (xbx) .
Started to think simply: if not a capacity problem, than would be a logic problem (3rd p. scenery, airport)
So, made a hypothesis:
types of scenery related add ons in brief
- stock, base airport, base runway or jetway
- “custom” MS airports upgraded runway, jetway
- 3rd party airport, modelled runway, taxiway, jetway
- jetway, or runway/taxiway addon SEPARATELY installed
Ok, when at the 3rd party airports, or even MS upgraded airports, there should be a code segment to make exact hierarchy: which one to render? Default, custom (MS or 3rd party enhanced) OR SINGLE addon enhanced jetway, runway, taxiway, OR any scenery related ADD ON???
It should be conflicted (three options for draw the scenery), since separately programmed, MS testing method etc. , no crosscheks in add on combinations. It is not an easy logical conflict.
Experiment after that thinking
I removed/uninstalled two single add ons related to a PART of airport scenery (so all of that type I had) : taxi, runway graphics, and jetway graphics. KEPT all 3rd party airports, sceneries.
No SINGLE crash on 3rd party airports since than (from 100% ctd rate before, lik Cracow, Milan, Genova, Coppenhagen, LHBP, Edinborough, Glasgow etc.)
I hope works for you, sorry if not, it worked for me 100%, if 1-2 of you can help, that is a benefit for me.
Bing On
Roliing data Off
AI, weather, time Live
HDR 10 On
4K, 60 Hz
Hotas, wireless mouse, controller same time
1.22
VFR and IFR too with ILS
300 Mbit/sec
Lan cable
tested with lots of view changes
I have many CTD experience since the latest update. Never run into problems before the update.
Log Name: Application
Source: Application Error
Date: 27/2/2022 11:19:01 pm
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: BensonLau
Description:
Faulting application name: FlightSimulator.exe, version: 1.22.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.22.2.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000148b311
Faulting process id: 0x758
Faulting application start time: 0x01d82beae2f2c2eb
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 92999181-556e-418e-aec5-9a8a22872bf7
Faulting package full name: Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
1000
0
2
100
0
0x80000000000000
29623
Application
BensonLau
FlightSimulator.exe
1.22.2.0
00000000
FlightSimulator.exe
1.22.2.0
00000000
c0000005
000000000148b311
758
01d82beae2f2c2eb
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
92999181-556e-418e-aec5-9a8a22872bf7
Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe
App
CTD’s on every update.
Faulting application name: FlightSimulator.exe, version: 1.23.12.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.23.12.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001b958fa
Faulting process id: 0x2280
Faulting application start time: 0x01d82d3a64440d38
Faulting application path: D:\Games\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\Games\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: 40fe0db0-5655-493d-98d7-0f00fa73ac91
Faulting package full name:
Faulting package-relative application ID:
I have been struggling with CTD since last November or so. Limiting the frame rate to something lower than the actual limit in the MSfS setting, solved my issue.
Recent update been flying for a couple of hours, I’ve actually reset my whole windows by creating a new account (kept all files) and that removed all the fixes I’ve attempted before from Nvidia 3D settings and virtual memory, and many more. Also turn off any GPU or CPU overclocking (including AI overclocking). So far it’s very smooth, some bugs in a couple of flight modules but nothing too crazy, I’m actually encouraged to re-download all the content I deleted before (in hopes of ending CTDs) but I gotta do more crazy stress tests first. Time to land a 747 in the Hudson with Ultra settings on…
Same here. I’ve been having many CTDS recently.
Your issue may be completely different, but just in case this is the solution I found for my CTDs.
I’ve been an Avast user for more than a decade and never had issues before about 3 weeks ago. My rig almost never had CTDs with FS2020 but then they started happening randomly and almost every time after the Sim fully loaded, sometimes in the World Map but most often while flying. I tried earlier nVidia driver versions, emptying the Community folder, even reinstalling FS2020 in a new User account on the PC. Nothing seemed to work.
On a whim I then disabled all the Avast “Shields” and Windows Defender popped up to replace the Avast firewall, and no more CTDs. I uninstalled just the Avast Firewall, repopulated the Community folder with add-ons and since then not even one CTD. That was more than a week ago and I’ve launched FS2020 at least a dozen times and flown for more than 5 hours.
Hi all, after the SIM loaded and installed the updates today (29/04), it does not start. In fact, it CTD after some seconds.
Any ideas how to solve it?
Thanks.
Yeah same here, xbox crashed four consecutive times, all within a minute or two of trying to load a flight, cursor freezes, screen turns black & simulator reloads back to main menu which takes approx 3 or 4 plus minutes!!
I
Yes, I have the same problem constant crashing now after SU9
Same here. SU9 Update. Crashes on startup. Sometimes to desktop, sometimes crashed the entire computer. I started to re-download the game, got back 4 hours later, the game started. I closed it out. Re-installed FBW Airbus 320. Tried to re-open the game, crashed 12-15 times in a row. Still can’t play. Super annoying that these guys can’t run an update without crashing everyone’s game.
beside of a possible game issue , does these fact point to a issue with your system. Also the timeing factor your described. Related to that, try the usually known tests, like limiting fps. If that helps, you know somewhat on your system may cause that.
And of course the first steps, in case you search crashs of msfs is: remove all mods ( FBW is a mod ). And be aware that some of these mods created folders outside of community folder, which affects the game ( e.g. all these workingtitle* stuff. And we can not repeat it often enough: if you had ever installed the garmin-replacement mod, clean your windows hosts file.
Issue solved.
Hello! So, I am getting two separate errors now.
Faulting application name: FlightSimulator.exe, version: 1.25.7.0, time stamp: 0x00000000
Faulting module name: d3d11.dll, version: 10.0.22000.527, time stamp: 0xf920f323
Exception code: 0xc0000005
Fault offset: 0x000000000018f58d
Faulting process id: 0x2e10
Faulting application start time: 0x01d860a7b833163e
Faulting application path: D:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\d3d11.dll
Report Id: 25d7b961-c1e1-4916-8f7c-ca6c4ef9ca11
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: FlightSimulator.exe, version: 1.25.7.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.25.7.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001c0b458
Faulting process id: 0x212c
Faulting application start time: 0x01d860a2496c37b1
Faulting application path: D:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: 7a94f8a5-4c08-44ef-96e0-3509a5864eea
Faulting package full name:
Faulting package-relative application ID:
Any help is appreciated, as my game had been virtually unplayable since the update.
often gpu related ( overheat or driver ).
Beside of checking driver can a test-case be to set a fps limit to a low value, eg. 30.
I’ll give that a try. I also set my GPU to high power which just gave me a problem-free flight.
Thank you!
Ugh. Me too. Only had the sodding thing running again for about a week since SU5 bricked it last time and i gave up.
Faulting application name: FlightSimulator.exe, version: 1.25.9.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.25.9.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001c10328
Faulting process ID: 0x15a0
Faulting application start time: 0x01d86578ffddd546
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.25.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.25.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 1991384c-0780-4ada-af57-20cdac8b3173
Faulting package full name: Microsoft.FlightSimulator_1.25.9.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Computer Information:
Manufacturer: System manufacturer
Model: System Product Name
Form Factor: Desktop
No Touch Input DetectedProcessor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core™ i9-9900K CPU @ 3.60GHz
CPU Family: 0x6
CPU Model: 0x9e
CPU Stepping: 0xd
CPU Type: 0x0
Speed: 3600 Mhz
16 logical processors
8 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Unsupported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: UnsupportedOperating System Version:
Windows 11 (64 bit)
NTFS: Supported
Crypto Provider Codes: Supported 311 0x0 0x0 0x0Video Card:
Driver: NVIDIA GeForce RTX 3090
DirectX Driver Name: nvldumd.dll
Driver Version: 30.0.15.1215
DirectX Driver Version: 30.0.15.1215
Driver Date: 3 17 2022
OpenGL Version: 4.6
Desktop Color Depth: 32 bits per pixel
Monitor Refresh Rate: 60 Hz
DirectX Card: NVIDIA GeForce RTX 3090
VendorID: 0x10de
DeviceID: 0x2204
Revision: 0xa1
Number of Monitors: 2
Number of Logical Video Cards: 2
No SLI or Crossfire Detected
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 3840 x 1080
Primary Display Size: 20.75" x 11.65" (23.78" diag)
52.7cm x 29.6cm (60.4cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 24575 MB
Supported MSAA Modes: 2x 4x 8xSound card:
Audio device: DELL U2414H (NVIDIA High DefiniMemory:
RAM: 32681 MBVR Hardware:
Headset: Valve Index (lighthouse)
Base station or sensor: Valve Corporation Valve SR Imp (lighthouse)