CTD within a few minutes of starting a flight

User Support Hub Crashes (CTDs)
,
1

:wave: Thank you for 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?
Yes

Brief description of the issue:

When starting at any airport I seem to get 2-3 mins in to setting up, possibly managing a takeoff. For the sim to then CTD. I intially had this with stock planes. But also had it with A320 FBW.

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

Detailed steps to reproduce the issue encountered:

Pretty simple for me really. Load the sim at any airport, start doing pre-start checklists and within 2-3 mins it will CTD,

PC specs and peripheral set up:

AMD Ryzen 7 3800X 8-Core Processor 3.89 GHz
32GB Ram DDR4
Nvidea 2070 SUPER 8GB GDDR6

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

1544645382212942123, type 4

Build Version # when you first started experiencing this issue:

Not sure how to find this?

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

I wonder if things are running too hot, as while the sim worked briefly before the updates last week. I have not really played this game much. Is there a good monitoring program I can try to see if it is my hardware underperforming?

Thanks

2

Moved to #community-support:tech-support which is more appropriate :+1:

3

first starting point might be to open the windows event viewer and check/share the message related to the crash.

Sometime a clean of rolling-cache, etc. might help in such situations. If you assume hardware problems, you can do test-cases where you limit in nvidia control center the max fps to a low value.

4

Thanks for the replies.

I have cleaned the cache and I share the message below:

This was from the crash log “error report”

Fault bucket 2011637954514022221, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: FlightSimulator.exe
P2: 1.30.12.0
P3: 63c582fa
P4: FlightSimulator.exe
P5: 1.30.12.0
P6: 63c582fa
P7: c0000005
P8: 0000000001722649
P9:
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5333.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER549C.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER54AC.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER54AA.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER54CA.tmp.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_FlightSimulator._b71a6856c1d49da0b732805f5fa0929e868594_ec018cca_1e1bd29e-729d-421e-bc7a-a9b433e0cbfe

Analysis symbol:
Rechecking for solution: 0
Report Id: 46cb45aa-d97f-4cc3-a8a2-3787e280f05b
Report Status: 268435456
Hashed bucket: c8c792357b52c658ebeac60fbf806f4d
Cab Guid: 0

and this from the appcrash log

Faulting application name: FlightSimulator.exe, version: 1.30.12.0, time stamp: 0x63c582fa
Faulting module name: FlightSimulator.exe, version: 1.30.12.0, time stamp: 0x63c582fa
Exception code: 0xc0000005
Fault offset: 0x0000000001722649
Faulting process ID: 0x87c
Faulting application start time: 0x01d93e65b50f8725
Faulting application path: D:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report ID: 46cb45aa-d97f-4cc3-a8a2-3787e280f05b
Faulting package full name:
Faulting package-relative application ID:

Incidentally I tried several aircraft at EGKK over yesterday and today. Not doing much, I just let it sit there after clearing the cache. I turned off all traffic but kept live weather going. I also limited Nvidea control to 40fps. No crash, no stutter, ran for ages.

I then took one off using same settings, just put it on autopilot up to 35,000 -unway heading and it flew for a good 2 hours with no issues.

Ill try repeat with a heavy amount of live traffic but I think limiting the card may well be the trick here - and I could not see any depreciation in performace. Its like its working far too hard to pump out max FPS when it really does not need to!

If you pick anything up from the log above be good to know - and thankyou!

John