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 for unknown reasons

Featured Replies

I have had about 3 CTDs out of a dozen flights since SU12. Any advice would be appreciated

System:

I7=9700K

GPU Geforce RTX 2070 Super

MB MSI 2390

16 GB RAM

CTD happens about 40 minutes into flight. Last occurrence with Carenado PA44 IFR KDAY to KSDF with PMS50 GTN

Default scenery

From Event Viewer:

Log Name:      Application
Source:        Application Error
Date:          4/9/2023 6:15:55 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Dale5
Description:
Faulting application name: FlightSimulator.exe, version: 1.31.22.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.31.22.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000004f52410
Faulting process id: 0xcd4
Faulting application start time: 0x01d96ac408829f12
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: d1b4d4f0-b1b0-4da0-b1f9-377add4fac3b
Faulting package full name: Microsoft.FlightSimulator_1.31.22.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="2023-04-09T10:15:55.8814040Z" />
    <EventRecordID>74467</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Dale5</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FlightSimulator.exe</Data>
    <Data>1.31.22.0</Data>
    <Data>00000000</Data>
    <Data>FlightSimulator.exe</Data>
    <Data>1.31.22.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>0000000004f52410</Data>
    <Data>cd4</Data>
    <Data>01d96ac408829f12</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>d1b4d4f0-b1b0-4da0-b1f9-377add4fac3b</Data>
    <Data>Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>

 

 

Dale

This happens to me as well.....since about January. Either within a few minutes after takeoff or 40+ minutes into the flight usually on decent or final approach. With me its 8 or 9 out of 10 flights.

  • Author

I flew the same route and approach with a different aircraft today and got the same CTD at about the same time and location. I'm thinking a default scenery error?

RAM, VRAM, CPU and GPU all checked ok.

Will try again later with a different approach

Dale

  • Author

Just finished the same flight, this time to RNAV rwy 29 instead of RNAV rwy 17l. No CTD, everything worked perfectly.

Dale

  • 3 months later...
On 4/10/2023 at 10:20 AM, tanker said:

Just finished the same flight, this time to RNAV rwy 29 instead of RNAV rwy 17l. No CTD, everything worked perfectly.

How have you done since this report?  I have started having similar CTDs.

 

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

  • Author

No CTDs in the last 2 months. I have not really changed anything in my setup. I suspect the CTDs I experienced in the past were tied to a particular default scenery and/or approach.

Dale

  • 3 months later...

I'm getting occasional CTDs and am not sure why. Doesn't happen every flight but when it does occur it is right at the moment of touchdown. Running default scenery. Using Fenix with GSX-pro and I downloaded the software that coordinates GSX and Fenix. Other than that the only thing I am using is Navigraph/simbrief. 

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.