Constant CTDs after flying a bit

:wave: Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons?

No

Brief description of the issue:

CTD after 30mins through 2hrs. of flight time

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

No screenshot as program abruptly crashes straight to desktop

Detailed steps to reproduce the issue encountered:

Any flight

PC specs and/or peripheral set up if relevant:

i7-7700K stock speed, 32GB ram, 3080 12GB, Windows 10 22H2, OS build 19045.2251

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

Fault bucket 1154412257640373589, type 4

Build Version # when you first started experiencing this issue:

Been having these CTDs for the last few months through SU10 and SU11


: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:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

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

Today’s CTD 12/4/22 12:45:49 EST. Straight to Desktop after about 30mins of flying

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

Fault bucket 2280724046231571846, type 5

1 Like

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

Another CTD today 12/4/22 2:27:52 EST Clicked fly Now at approx. 1:32 EST, took off from runway at approx. 1:50 EST and CTD at 2:27 EST

If relevant, provide additional screenshots/video:

Had Process Explorer running and graphing Flightsimulator and this is a capture after CTD.



CTD-process-expl03

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

Fault bucket 1154412257640373589, type 4

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

This morning’s CTD 12:16 AM EST 12/9/22
Event 1000
Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Exception code: 0xc0000005
Fault offset: 0x0000000000806209
Faulting process id: 0x290c
Faulting application start time: 0x01d90be1358b56dc

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

Fault bucket 1154412257640373589, type 4

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

This morning’s CTD, 12/10/2022 12:05:42 PM EST
Event ID 1000 Error
Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Exception code: 0xc0000005
Fault offset: 0x0000000004b4ce40
Faulting process id: 0x44d0
Faulting application start time: 0x01d90cb2e6d940da

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

Fault bucket 2152828638152270779, type 4

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

Second CTD today 12/10/22 at 3:23:40 PM EST.
Thought I’d got lucky as this flight lasted almost 2hrs.
Event ID 1000 Error
Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Exception code: 0xc0000005
Fault offset: 0x0000000000806209
Faulting process id: 0x4a1c
Faulting application start time: 0x01d90cc8ab8d56db

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

Fault bucket 1154412257640373589, type 4

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

This evening’s CTD 12/11/22 5:35PM EST
Event 1000 Error
Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Exception code: 0xc0000005
Fault offset: 0x0000000004b4ce40
Faulting process id: 0x4284
Faulting application start time: 0x01d90da9cd223d7d
Report Id: 345a8439-3a7e-42fa-b897-085b40540fc7

If on PC, Fault Bucket ID

Event ID 1001
Fault bucket 2152828638152270779, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator.exe
P2: 1.29.30.0
P3: 637cad1c
P4: FlightSimulator.exe
P5: 1.29.30.0
P6: 637cad1c
P7: c0000005
P8: 0000000004b4ce40
P9:
P10:

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

Today’s CTD at 4:34PM EST
Event ID 1000
Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Exception code: 0xc0000005
Fault offset: 0x0000000004b4ce40
Faulting process id: 0x1ba4
Faulting application start time: 0x01d9118e7d1d4967

If on PC, Fault Bucket ID

EVENT ID 1001
Fault bucket 2152828638152270779, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator.exe
P2: 1.29.30.0
P3: 637cad1c
P4: FlightSimulator.exe
P5: 1.29.30.0
P6: 637cad1c
P7: c0000005
P8: 0000000004b4ce40
P9:
P10:

Gave in a did a complete reinstall yesterday. Uninstalled the sim and removed all flight simulator folders from appdata too. Took half a day installing all then the world updates, etc. Tried a flight from KTHA to KTBR. Reinstall did not help one bit.

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

Today’s CTD 12-18-22 at 10:39AM EST
Event ID 1000
Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Exception code: 0xc0000005
Fault offset: 0x0000000000806209
Faulting process id: 0x3150
Faulting application start time: 0x01d912eafead2e46
Report Id: ac04fab0-c174-4541-9a27-5b459c21c2c7

If on PC, Fault Bucket ID

Event ID 1001
Fault bucket 1154412257640373589, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator.exe
P2: 1.29.30.0
P3: 637cad1c
P4: FlightSimulator.exe
P5: 1.29.30.0
P6: 637cad1c
P7: c0000005
P8: 0000000000806209
P9:
P10:

1 Like

Interestingly I’ve been having strange CTDs - here is the post I have (VC Runtime VCRuntime140.dll crash - #4 by TootyFruity123)

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons?

No, nothing has changed in a few weeks

PC specs and/or peripheral set up if relevant:

i9-13900KF Stock, 64GBGB Memory, MSI RTX 4090, Windows 11 Version 10.0.22621 Build 22621

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

Similar issue, but I can only assume different locations (my CTDs have been around the Alps)
See the above link for my details of CTDs

If relevant, provide additional screenshots/video:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

Fault bucket 1765966596762904075, type 4 and Fault bucket 1907571318042605930, type 4

Once I’m past a certain point it’s perfect and I can continue on with no issues at all.

Example from yesterday

-Red = Crash location
-Blue = Depature points
-Yellow = Current

Once past the red, it was fine, I continues on and finished another 3 hours with no issues

Today, took off from Barcelona, crash and loaded back in close to my CTD point. Passed the area and it seems OK (ignore Volanta landing, I tried to load a save but didn’t realise the Fenix wasn’t supported)

Crash would be around here:

Flightplan - -LEBL/24L F360 DALIN3Q DALIN DCT ETREK UN854 BULOL DCT IDARO DCT
TUTOV DCT BASUM M170 ELSOB DCT ROSBI DCT RISMA RISMA3S ESGG/21

As seen still on-going with no issue. Furthermore I’ve completed the flight

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

Figured I’d try again. Today’s flight CTD at 3:36PM EST
Event ID 1000
Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Exception code: 0xc0000005
Fault offset: 0x0000000000806209
Faulting process id: 0xe08
Faulting application start time: 0x01d917ce25cb1784
Report Id: c61fa3bd-c773-427e-98c0-5c855c66632b
Faulting package full name:
Faulting package-relative application ID:

If on PC, Fault Bucket ID

Event ID 1001
Fault bucket 1154412257640373589, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator.exe
P2: 1.29.30.0
P3: 637cad1c
P4: FlightSimulator.exe
P5: 1.29.30.0
P6: 637cad1c
P7: c0000005
P8: 0000000000806209
P9:

I don’t know if this helps but in game from the MSFS Marketplace I have the Carenado Mooney (though I’ve not flown it for a while), the Top Rudder 103 Solo, USA Ground Vehicles (Airport Regional Environment X North America) and KTBR airport. The flight was the same (KTHA-KTBR) as the last couple times.

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

This morning’s CTD 12:30 PM EST
Error - Event ID 1000
Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Exception code: 0xc0000005
Fault offset: 0x0000000000806209
Faulting process id: 0x3208
Faulting application start time: 0x01d9194889a881fb
Report Id: 49a92259-4fc1-4a6e-abd0-6d1ed1362607
Faulting package full name:
Faulting package-relative application ID:

If on PC, Fault Bucket ID

Event ID 1001
Fault bucket 1154412257640373589, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator.exe
P2: 1.29.30.0
P3: 637cad1c
P4: FlightSimulator.exe
P5: 1.29.30.0
P6: 637cad1c
P7: c0000005
P8: 0000000000806209
P9:
P10:
Analysis symbol:
Rechecking for solution: 0
Report Id: 49a92259-4fc1-4a6e-abd0-6d1ed1362607
Report Status: 268435456
Hashed bucket: d7fa26090fb62c8a90054bd4fd02dd55
Cab Guid: 0

Extra Info from Reliability History:

Problem signature
Problem Event Name: APPCRASH
Application Name: FlightSimulator.exe
Application Version: 1.29.30.0
Application Timestamp: 637cad1c
Fault Module Name: FlightSimulator.exe
Fault Module Version: 1.29.30.0
Fault Module Timestamp: 637cad1c
Exception Code: c0000005
Exception Offset: 0000000000806209
OS Version: 10.0.19045.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 7c28
Additional Information 2: 7c28e5893ebab519caaca888c1882dc4
Additional Information 3: 71d9
Additional Information 4: 71d9d36785392ef152f45d69b41bf2e1
Extra information about the problem
Bucket ID: d7fa26090fb62c8a90054bd4fd02dd55 (1154412257640373589)

Had deleted the USA Ground Vehicles and KTBR from the Content Manager before flight. Same Flightplan KTHA-KTBR.

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

Latest CTD 5:26PM EST
Error. Event ID 1000
Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Exception code: 0xc0000005
Fault offset: 0x0000000000806209
Faulting process id: 0x1d6c
Faulting application start time: 0x01d91973748333dd
Report Id: 80d9bf10-3076-4aaf-aa34-ad270333dc04
Faulting package full name:
Faulting package-relative application ID:

If on PC, Fault Bucket ID

Event ID 1001
Fault bucket 1154412257640373589, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator.exe
P2: 1.29.30.0
P3: 637cad1c
P4: FlightSimulator.exe
P5: 1.29.30.0
P6: 637cad1c
P7: c0000005
P8: 0000000000806209
P9:
P10:
Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FB6.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER515C.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER517D.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER517B.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER518B.tmp.txt
These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FlightSimulator._f5909bf2d6bb60d0c17dbcda6205f3d329cb96_ffd118a1_94505176-2cf5-49c7-8a55-12e353a9dec9
Analysis symbol:
Rechecking for solution: 0
Report Id: 80d9bf10-3076-4aaf-aa34-ad270333dc04
Report Status: 268435456
Hashed bucket: d7fa26090fb62c8a90054bd4fd02dd55

Extra Info from Reliability History:

Problem signature
Problem Event Name: APPCRASH
Application Name: FlightSimulator.exe
Application Version: 1.29.30.0
Application Timestamp: 637cad1c
Fault Module Name: FlightSimulator.exe
Fault Module Version: 1.29.30.0
Fault Module Timestamp: 637cad1c
Exception Code: c0000005
Exception Offset: 0000000000806209
OS Version: 10.0.19045.2.0.0.256.48
Locale ID: 1033
Additional Information 1: cf43
Additional Information 2: cf43bdabb72c8cb6aa612341ddfc8c1b
Additional Information 3: deda
Additional Information 4: dedabbd910ce3e428bdc1e9ed61e2ab5
Extra information about the problem
Bucket ID: d7fa26090fb62c8a90054bd4fd02dd55 (1154412257640373589)

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

Today’s CTD 12:53 pm EST
ERROR - EVENT ID 1000
Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Exception code: 0xc0000005
Fault offset: 0x0000000000806209
Faulting process id: 0x36fc
Faulting application start time: 0x01d91adf1ecdb9d2
Report Id: efaf8fc9-a5c2-4dfc-a2d9-747dd3e46be8
Faulting package full name:
Faulting package-relative application ID:

If relevant, provide additional screenshots/video:

From Reliability History. Every one of those Red Xs is a MSFS CTD


and the details of today’s CTD

If on PC, Fault Bucket ID

Event 1001
Fault bucket 1154412257640373589, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator.exe
P2: 1.29.30.0
P3: 637cad1c
P4: FlightSimulator.exe
P5: 1.29.30.0
P6: 637cad1c
P7: c0000005
P8: 0000000000806209
P9:
P10:

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

Today’s CTD at 2:58PM EST.
Error - EVENT ID 1000
Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Exception code: 0xc0000005
Fault offset: 0x0000000000806209
Faulting process id: 0x1908
Faulting application start time: 0x01d91c7b561032f4
Report Id: 5e672205-13e9-48c8-8fa2-3de524468d6d
Faulting package full name:
Faulting package-relative application ID:

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

Thought I had beat the CTD this time. Before launching, I had set FlightSimulator.exe to run as administrator. This flight (KTHA-KTBR) I made it almost to my approach point (about 9mins. away) before the CTD… I had Open Hardware Monitor running monitoring temps, memory and loads. Below I’ll post the screenshot during flight and right after crash. Nothing seen in it that suggests a hardware problem. Right after the CTD happened the loads, temps, etc. dropped as expected but you can see there were no spikes in the graphs right before.

If relevant, provide additional screenshots/video:

5 minutes before CTD


Right after CTD

Reliability Monitor report

If on PC, Fault Bucket ID

EVENT ID - 1001
Fault bucket 1154412257640373589, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: FlightSimulator.exe
P2: 1.29.30.0
P3: 637cad1c
P4: FlightSimulator.exe
P5: 1.29.30.0
P6: 637cad1c
P7: c0000005
P8: 0000000000806209
P9:
P10:
Analysis symbol:
Rechecking for solution: 0
Report Id: 5e672205-13e9-48c8-8fa2-3de524468d6d
Report Status: 268435456
Hashed bucket: d7fa26090fb62c8a90054bd4fd02dd55
Cab Guid: 0

Which GPU are you using? Which Driver Version?
I have the same issue.

3080 12GB on the latest driver. This has been ongoing through about the last four drivers though, so I don’t think it’s a graphics driver issue.

I’ve stress tested my machine with OOCT on graphics, memory, harddrive, etc. Also ran Windows Memory Diagnostic and memtest86, etc… I’ve found no hardware problems.

I’m flying in the Southeast USA mostly.

Windows 10 OS is on a Samsung 950 Pro NVMe M.2 and MSFS is on a Sabrent NVMe M.2. I have a couple other HDs, but they are just used for storage. Temps are fine, loads are fine, memory is fine, HDs show no errors, etc., etc. I have a 1000 Watt EVGA Gold PSU, 32GBs of Corsair memory at stock speeds, a EVGA 3080 12GB and a i7-7700k on a MSI Z290 Sli Plus board. I run 2 monitors, MSFS on one at 2K (and before all this, other apps such as FS Flight Control map on other before disabling it). OS and all drivers are up to date. No overclocking at all (ever). I’m to the point of just giving up on MSFS.

In my case, I get these CTDs every now and then. Sometimes, I can fly for hours without any issues. Other times, I don’t even get off the ground before I get a CTD. Looking at the error message in the Application log in WEV, it’s always the same thing…

Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x00000000
Exception code: 0xc0000005

What I’ve noticed is moments before the CTD, I always know it’s coming because I hear how the audio stops for a split second…then I get the audio back for another split second and moments later…back on the desktop.

This really takes away much of the fun flying. When you never know if you will land at your destination or on your desktop.

Based on what I said about the audio above, I figured maybe it indeed has something to do with audio drivers. I read you should get rid of 3rd party audio drivers and instead allow Windows to install it’s default drivers. In my case, I’m using the built-in Realtek audio on my MSI MAG Z690 Tomahawk. I uninstalled the Realtek drivers I got via MSI Live Update but sorry to say, I still get the same CTDs.

Not sure if I remember this correctly but I think I heard Asobo saying in one of their Q&As how they had implemented some kind of system that would collect data whenever someone was having a CTD. If so, I wonder what the status is and what they have been able to figure out from the data they received. Anyone heard anything more about this?

All of us having these issues can of course continue to post about it in threads like this one. However, I’m not so sure that will help us get rid of the CTDs. Of course, if we could find a common denominator for everyone having these CTDs, that could of course help.

Sigh…I’m starting to ramble without really saying anything useful. I’m just tired…before posting this I was enroute LICJ-ENVA and after about 2.5 h…yep…you guessed it right…CTD.

Think I’ll spend what’s left of this evening with Netflix instead.

1 Like

I don’t get the audio thing, just a pause for half a second and then the desktop.

I’ve basically just stopped flying for now which really hurts as it’s one of the things I really enjoy doing.