Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

CTD's after su13

Featured Replies

Before SU13 (and coincidentally rex accusim advanced) I had a rock solid sim with no crashes pretty much ever, now I am getting a crash on every flight I have tried with the fenix A320.  It has happened right at the start of the flight while panning in the cockpit, and twice 10 minutes after takeoff in VR, and again 3 hours into a flight after switching back into VR.  Any advice would be a big help.  Right under the MSFS crash in event viewer there is always a .NET runtime error with flightsimulator.exe also listed as the faulting module. 

 

Crash Data for msfs crash:

Faulting application name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001f96a99
Faulting process id: 0x0x69BC
Faulting application start time: 0x0x1D9F3EB36B254A2
Faulting application path: D:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: c5693921-18d3-4a61-bb6c-567143a858fc
Faulting package full name: 
Faulting package-relative application ID: 

 

.NET crash data:

Application: FlightSimulator.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FF60DF76A99
 

 

Lian Li 011 Air Mini | AMD 9800X3D | Asus ROG STRIX B650E-F | Arctic Cooling Liquid Freezer II 280mm RGB | 2x32GB G.Skill DDR5-6000 | ASUS TUF RTX 5090 | Seasonic Prime Platinum 1000W | Pimax Crystal Light

 

This is not going to help much, but it at least supplies information that might be useful. Prior to SU12, I rarely had CTDs, but since then they have been frequent -- all being of the "graphics error-must-be-something-wrong-with-your-graphics-card" variety. Changing Nvidia drivers (old/new) made no difference, nor did anything else. From my experience and that of a number of others, we concluded that SU12 was to blame. I pinned my hopes on SU13 to fix the problem, which it has not. Yesterday I had two "graphics-error" CTDs, both happening when I called up the logbook -- bizarre! Two more today -- both during flight after about 10 minutes of flying.

Something that was introduced by SU12, and perpetuated with SU13, has made MSFS 2020 unstable for me. I haven't a clue what it is, except it is NOT the graphics driver, my rig, or my settings -- I have been down those paths ad nauseum. Possibly if enough of us collect enough info we can zero in on what the real problem might be. Let's hope so -- or wait for SU14?

Alienware Aurora R11, 32 GB ram, Intel i7-10700F, GeForce RTX 2080 Super, Ultra graphics settings

 

Edited by cobalt

  • 2 weeks later...

OK, I am having to eat crow, big-time. I found the solution to the problem -- at least for me --, and it is not Asobo's fault after all. A suggestion in a post a while back, which I ignored for a long time, turned out to be the answer: in Windows 10 (and maybe W11 too), go into Settings -> Apps -> Startup, and set most apps to NOT start up automatically when Windows opens. (Most of mine had been set to open automatically, unbeknownst to me). Result: no more "graphics error" CTDs whatosever. Very few add-on programs, aside from those having to do with security and antivirus protection, need to open when Windows opens. Lesson learned.

Edited by cobalt

34 minutes ago, cobalt said:

OK, I am having to eat crow, big-time. I found the solution to the problem -- at least for me --, and it is not Asobo's fault after all. A suggestion in a post a while back, which I ignored for a long time, turned out to be the answer: in Windows 10 (and maybe W11 too), go into Settings -> Apps -> Startup, and set most apps to NOT start up automatically when Windows opens. (Most of mine had been set to open automatically, unbeknownst to me). Result: no more "graphics error" CTDs whatosever. Very few add-on programs, aside from those having to do with security and antivirus protection, need to open when Windows opens. Lesson learned.

That worked for me some time ago and still does.  I was going to experiment with a normal startup again but it seems I should keep current settings.

Bruce

Bruce Bartlett

 

Frodo: "I wish none of this had happened." Gandalf: "So do all who live to see such times, but that is not for them to decide. All we have to decide is what to do with the time that is given to us."

I have CTD with Fenix occasionally before or after SU13

Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASEL

My System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSD

Put my hands on (pic/dual/given)

7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22

 

It may not be the root cause, but I found if I set MSFS aviation traffic to anything other than Off I get CTD's.  I had read others had that issue as well.  For me no aircraft traffic = no CTD.  With traffic, often CTDs.  I do not use any addon traffic.  Again. It may not be the root cause, but stops them.

Edited by fppilot

Frank Patton
Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; 
NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener.  
Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126
                       
"I will never put my name on a product that does not have in it the best that is in me." - John Deere

4 hours ago, fppilot said:

It may not be the root cause, but I found if I set MSFS aviation traffic to anything other than Off I get CTD's.  I had read others had that issue as well.  For me no aircraft traffic = no CTD.  With traffic, often CTDs.  I do not use any addon traffic.  Again. It may not be the root cause, but stops them.

I use AI traffic and don't have CTD's but I'm using FSLTL.

Thinking about going back to PSXT though, today at LTAI I had traffic landing on opposite runways simultaneously, a real mess. That never happens with PSXT. Didn't want to pay to have AI traffic so I cancelled it, but I guess I have no other option. 😒

Alvega

CPU: AMD 7800X3D | COOLER: Cooler Master MasterLiquid 240L Core ARGB | GPU: RTX 4070 TI Super 16GB OC | Mobo: ASUS TUF GAMING X670E-PLUS WIFI |
RAM: 32 GB Corsair Vengeance RGB DDR5 6000MHz PC5-48000 2x16GB CL36 | SSDs: WD Black SN770 2TB NVMe SSD (WIN11), WD Black SN850X SSD 2 TB M.2 2280 PCIe Gen4 NVMe (MSFS), Crucial MX500 2TB (Other stuff) | CASE: Forgeon Arcanite ARGB Mesh Tower ATX White | Power Supply: Forgeon Bolt PSU 850W 80+ Gold Full Modular White 

  • 2 weeks later...

Simmers, non of that is the cause of crashes after SU13!  It is an ASOBO issue with the scenery rendering, something to do with that and their servers!!   I have issue a ticket to see if they fix that asap.  Who knows how long is going to take.   It is not your equipment nor settings, I have tried everything!!  After hitting FLY it crashes for me about 99% of the time!!!  and if it loads, it will crash during the flight, which means that I have not been able to fly for a while now.  I am really frustrated with this issue which seems that it has been going on for a while now.  Tried everything and nothing.  

 

4 hours ago, emgarcia69 said:

Simmers, non of that is the cause of crashes after SU13!  It is an ASOBO issue with the scenery rendering, something to do with that and their servers!!   I have issue a ticket to see if they fix that asap.  Who knows how long is going to take.   It is not your equipment nor settings, I have tried everything!!  After hitting FLY it crashes for me about 99% of the time!!!  and if it loads, it will crash during the flight, which means that I have not been able to fly for a while now.  I am really frustrated with this issue which seems that it has been going on for a while now.  Tried everything and nothing.  

 

I have a similar problem.  It'll crash upon loading to the main screen, or less often, while loading a flight.  Last night it took two or three attempts to load into KLAS.  It seems to be random, but I am able to fly more often than not and it never crashes "in flight", only while loading.

- Chris

Gigabyte Z790 Aorus Elite AX | Intel Core i9 13900KF | Gigabyte GeForce RTX 4090 24 GB | 64GB DDR5 SDRAM | Corsair H100i Elite 240mm Liquid Cooling | 1TB & 2TB Samsung Gen 4 SSD  | 1000 Watt Gold PSU |  Windows 11 Pro | Thrustmaster Boeing Yoke | Thrustmaster TCA Captain X Airbus | Asus ROG 38" 4k IPS Monitor (PG38UQ)

Asus Maximus VII Hero motherboard | Intel i7 4790k CPU | MSI GTX 970 4 GB video card | Corsair DDR3 2133 32GB SDRAM | Corsair H50 water cooler | Samsung 850 EVO 250GB SSD (2) | EVGA 1000 watt PSU - Retired

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.