CTD every single flight

Have you disabled/removed all your mods and add-ons?

Yes

Are you using Developer Mode or made changes in it?

No

Brief description of the issue:

I get CTD every flight approx after 15- 20 min

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:
Fault bucket 2235940092945315002, type 5

Faulting application name: FlightSimulator.exe, version: 1.37.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.37.2.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000002544c7e
Faulting process id: 0x0x1610
Faulting application start time: 0x0x1DA60E2CB2DCAB3
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: f27d1591-0aed-458d-96b7-5a032dd90305
Faulting package full name: Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

PC specs and/or peripheral set up:

If on PC, Fault Bucket ID - Instructions [here]
(How to find your Fault Bucket ID after a crash [PC]) - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

Fault bucket 2235940092945315002, type 5

Faulting application name: FlightSimulator.exe, version: 1.37.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.37.2.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000002544c7e
Faulting process id: 0x0x1610
Faulting application start time: 0x0x1DA60E2CB2DCAB3
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: f27d1591-0aed-458d-96b7-5a032dd90305
Faulting package full name: Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

Do you have the same issue if you follow the OP’s steps to reproduce it?

yes

Provide extra information to complete the original description of the issue:

happened with DX11 and 2D, I have CTDs in VR too but different Fault Bucket IDs, will report in a separate post

If relevant, provide additional screenshots/video:

Fault bucket 2235940092945315002, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0
Problem signature:
P1: Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.37.2.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.37.2.0
P7: 00000000
P8: c0000005
P9: 0000000002544c7e
P10:
<
<
<
<
<
Faulting application name: FlightSimulator.exe, version: 1.37.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.37.2.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000002544c7e
Faulting process id: 0x0x1A64
Faulting application start time: 0x0x1DA6116E16B6937
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: f200d939-89c5-49a3-bf12-8c30398263d8
Faulting package full name: Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Fault bucket 2235940092945315002, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.37.2.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.37.2.0
P7: 00000000
P8: c0000005
P9: 0000000002544c7e
P10:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes.

Provide extra information to complete the original description of the issue:

Same exception bucket after two hours of flight.

If relevant, provide additional screenshots/video:

I upgraded the SDK version. This was suggested may be the culprit. However, as usual, I had a CTD again after an hour or so. I will probably have to downgrade to the non-beta version after this. I cannot complete a flight now.

Last time I had had CTD troubles it was linked to some faulty AIRAC installation. Reinstalled the navigraph stuff and all was fine again

1 Like

Interesting. I guess a good way to find out is see how many of you have l Navigraph AIRAC installed?

I do, and I moved it out to see if it made a difference, but no, it didn’t.

What’s worth noting is that this is at a very specific offset, which really needs some of the MSFS/Asobo staff to look into and let us know what it is exactly.

1 Like

Just got updated to the .4 version of the beta. First two attempts ended in CTD as I was making my way to the runway at my usual test airport KMRY in the TBM850. Both were type 1000 faults with the sim being the faulting application. I’ll test more later.

Edit: well… go figure…
I restarted the PC and deleted a bunch of cache and scenery index files (per this thread SU 14 & Beta 15 No Noticeable Difference - #4 by TenPatrol)

Just had the smoothest and probably best FPS performance ever out of the sim.

1 Like