Sim CTD after updating to SU16 Beta

Sim Update 16 Beta | MSFS 2020 SU16 Beta Discussion
22

I hadn’t been watching RAM so far. This time I did. RAM usage was holding steady at about 16GB in use out of a total of 24GB available, when CTD just happened again under similar conditions. Again it was about 30 minutes into the flight along the same route, although previously the CTD along this route happened about 90 minutes into this flight, so it’s not location specific. This time it happened just as I switched from external camera to in-cockpit and then quickly to drone.

Window layout includes main FS view on screen 1, with ATC and GNS view undocked on screen 2, with FSLTL and LittleNavMap running in the backgound on screen 2.

Source
FlightSimulator.exe

Summary
Stopped working

Date
‎2/‎07/‎2025 5:59 PM

Status
Report sent

Description
Faulting Application Path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.39.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe

Problem signature
Problem Event Name: MoAppCrash
Package Full Name: Microsoft.FlightSimulator_1.39.5.0_x64__8wekyb3d8bbwe
Application Name: praid:App
Application Version: 1.39.5.0
Application Timestamp: 00000000
Fault Module Name: FlightSimulator.exe
Fault Module Version: 1.39.5.0
Fault Module Timestamp: 00000000
Exception Code: 80000003
Exception Offset: 0000000001e8de82
OS Version: 10.0.26100.2.0.0.768.101
Locale ID: 3081
Additional Information 1: cf43
Additional Information 2: cf43bdabb72c8cb6aa612341ddfc8c1b
Additional Information 3: c0c3
Additional Information 4: c0c3725621f53fd2b39b3b54648d545e

Extra information about the problem
Bucket ID: 45dd1f2595b1b928747f949fe635ce54 (1477062617283808852)

23

Same crash, same route, about 30 minutes in, this time with a different aircraft (Beechcraft King Air vs Cessna ???) and with only FSLTL running (no LittleNavMap).

Source
FlightSimulator.exe

Summary
Stopped working

Date
‎2/‎07/‎2025 7:18 PM

Status
Report sent

Description
Faulting Application Path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.39.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe

Problem signature
Problem Event Name: MoAppCrash
Package Full Name: Microsoft.FlightSimulator_1.39.5.0_x64__8wekyb3d8bbwe
Application Name: praid:App
Application Version: 1.39.5.0
Application Timestamp: 00000000
Fault Module Name: FlightSimulator.exe
Fault Module Version: 1.39.5.0
Fault Module Timestamp: 00000000
Exception Code: 80000003
Exception Offset: 0000000001e8de82
OS Version: 10.0.26100.2.0.0.768.101
Locale ID: 3081
Additional Information 1: 414c
Additional Information 2: 414c3744e3e98e3d1f2aea49a3f3e459
Additional Information 3: 1e12
Additional Information 4: 1e1208c9168883b335aa57e75f36d267

Extra information about the problem
Bucket ID: 45dd1f2595b1b928747f949fe635ce54 (1477062617283808852)

24

Another CTD. Same aircraft, same route, no LNM and no FSLTL, had just started the take-off run when CTD happened. This one is happened so quickly it didn’t appear in the Reliability monitor. Went into the event viewer to see what I could find there, and discovered “resource exhaustion” messages corresponding to previous CTDs. This is odd because the task manager “resource monitor” showed there was still unused physical RAM (24 GB installed) available at the time of the crash.

Recreated the flight again after a full restart of the system, with all other apps (steam client, other non-gaming clients) fully shut down. Another CTD was triggered about 30 minutes into the flight, again corresponding to a memory resource exhaustion event.

Turns out under “advanced system settings” I had set my computer to “no paging file” this whole time, originally done to preserve the life of my primary SSD. And by some stroke of luck this setting has NEVER caused problems with FS2020 until build 4 or 5 of SU16. I have to assume this version relies more heavily on virtual memory, and for some reason doesn’t appear able to use more than about 18GB of the 24GB of RAM my system has.

I have turned the paging file back on, let’s see if that improves anything. For now, here are the details of the last CTD using the “no paging file” setting.

Source
FlightSimulator.exe

Summary
Stopped working

Date
‎2/‎07/‎2025 9:06 PM

Status
Report sent

Description
Faulting Application Path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.39.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe

Problem signature
Problem Event Name: MoAppCrash
Package Full Name: Microsoft.FlightSimulator_1.39.5.0_x64__8wekyb3d8bbwe
Application Name: praid:App
Application Version: 1.39.5.0
Application Timestamp: 00000000
Fault Module Name: FlightSimulator.exe
Fault Module Version: 1.39.5.0
Fault Module Timestamp: 00000000
Exception Code: 80000003
Exception Offset: 0000000001e8de82
OS Version: 10.0.26100.2.0.0.768.101
Locale ID: 3081
Additional Information 1: 6ed0
Additional Information 2: 6ed066ab37ebe8ea754f0a3b1959c5f2
Additional Information 3: efb0
Additional Information 4: efb07b67a52995c9811527fae568e408

Extra information about the problem
Bucket ID: 45dd1f2595b1b928747f949fe635ce54 (1477062617283808852)

And here is the event-viewer entry that corresponded to the CTD

Log Name: System
Source: Microsoft-Windows-Resource-Exhaustion-Detector
Date: 2/07/2025 9:06:28 PM
Event ID: 2004
Task Category: Resource Exhaustion Diagnosis Events
Level: Warning
Keywords: Events related to exhaustion of system commit limit (virtual memory).
User: SYSTEM
Computer:
Description:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: FlightSimulator.exe (14980) consumed 18458877952 bytes, dwm.exe (1848) consumed 368963584 bytes, and MsMpEng.exe (6448) consumed 302116864 bytes.