MSFS CTD without warning

: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? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

yes

Brief description of the issue:

Switched from cockpit to external view and MSFS crashed to desktop

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

Detailed steps to reproduce the issue encountered:

Start flight and switch to external view…

Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version (Learn how to find your current graphics card driver version):

Everything is up-to-date

PC specs and peripheral set up:

i7 10700k, 32GB DDR4 3200, RTX3090

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 2245496120914643988, type 5

Build Version # when you first started experiencing this issue:

1.35.21.0_x64


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

More info:

Problem signature:
P1: Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.35.21.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.35.21.0
P7: 00000000
P8: c0000005
P9: 000000000187ee84
P10:

Faulting application name: FlightSimulator.exe, version: 1.35.21.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.35.21.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000187ee84
Faulting process id: 0x144
Faulting application start time: 0x01da39c57d084dd1
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: d18eb21f-2dff-44cd-89ff-8c698dd3f182
Faulting package full name: Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Are you saying it does this every time, 100% repeatable?

Nope, that was just the 1st time it happened… And hopefully the last time

Edit: It definitely wasn’t the last time, MSFS has been extremely unstable since the last update

2 Likes

Yea it’s pretty common. The 00005 error. No rhyme or reason except for general flakiness I think. Annoying for sure but so long as it’s not every time we just need to live with it :frowning:

1 Like

Go through each of the following steps one at a time. Copy each line, one at a time , paste it into the Dos window (crtl + V) and press return

and it will then run. Wait until each runs and finishes before you move on to the next one.

When you are completely finished, Restart your computer and then try to see in MS2020 will start and run properly

Dism.exe /online /Cleanup-Image /checkhealth

Dism.exe /online /Cleanup-Image /scanhealth

Dism.exe /online /Cleanup-Image /Restorehealth

sfc /scannow

Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

Dism.exe /Online /Cleanup-Image /StartComponentCleanup

RESTART your computer as the last step. Then go for a test flight.

1 Like

Did that, still crashes, they done screwed something up with the last update sadly…

1 Like

Try signing out of your Xbox account then back in.

Didn’t work either sadly

I am also now getting this same issue out of nowhere.

Rejoice, yet another CTD, MSFS with only payware addons out of LFSB, rotate and right turn about 20 seconds after positive rate, sound stops, MSFS freezes, 10 seconds later quickly get sound for 1 sec then CTD. It’s just sad at this point, the last time MSFS crashed so much was in SU3 I believe

Here’s what event viewer says:

Faulting application name: FlightSimulator.exe, version: 1.35.21.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.35.21.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000187ee84
Faulting process id: 0x3ecc
Faulting application start time: 0x01da3fd54b172c2e
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: fe69cb4e-e587-4e32-b4f8-bd70d623ebc1
Faulting package full name: Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

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

Problem signature:
P1: Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.35.21.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.35.21.0
P7: 00000000
P8: c0000005
P9: 000000000187ee84
P10:

Analysis symbol:
Rechecking for solution: 0
Report Id: fe69cb4e-e587-4e32-b4f8-bd70d623ebc1
Report Status: 4100
Hashed bucket:
Cab Guid: 0

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

Problem signature:
P1: Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.35.21.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.35.21.0
P7: 00000000
P8: c0000005
P9: 000000000187ee84
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9756.tmp.WERInternalMetadata.xml

Analysis symbol:
Rechecking for solution: 0
Report Id: fe69cb4e-e587-4e32-b4f8-bd70d623ebc1
Report Status: 268439552
Hashed bucket: 0c073638bc5c87452f299ad327a28c14
Cab Guid: 0

Hi, I was getting intermittent CTD’s whist using different aircraft, different routes and different flight durations. There would be a stuttering then the sound would go off then a CTD with no error message. Very frustrating so I tried everything suggested online and still they came (CTD’S). Different settings upgraded to Windows 11, moved the MSFS 2020 to a new location, updated my Nvidia drivers, nothing worked. I always kept a log of my flight details and then I noticed that with one certain Nvidia driver I never had a CTD. It was driver version 536.67, with this version I have flown 25 flights with no CTD’s compared to version 535.98, 5 flights with 4 CTD’s. Other versions were just as bad for CTD’s. I have not had a CTD since the 9th November 2023. If you are having CTD’s frequently it may help to roll back to this driver version. Hope this helps.

1 Like

Awesome tip, I’m on the latest drivers as of today, I’ll roll back to the version you suggested and see if that fixes my constant CTD issues. May I ask what the rest of your PC specs are please, curious if it’s in the ballpark of what I have.
Also, do you currently use the frame gen mod, since I tried it I refuse to fly without it, it’s so smooth now, will the driver rollback effect that? If you know perhaps :slightly_smiling_face:

Thanks in advance

I’ve not yet tried frame generation. Holding off until it is more stable.

System specs:

Win 10 Pro 22H2 19045.3803
Gigabyte GA-Z68XP-UD3 rev 1.0 (BIOS F-10)
Core i7 3770K (no OC)
32GB G-Skill Trident X F31600C7-8GTX (CL 7-8-8-24)
Asus RTX 2070 OC 8GB (drivers 546.33)
1TB Crucial MX500 SSD (OS drive)
2TB PNY CS900 (DCS/MSFS drive)
(x3) 1TB RAW Mushkin SSDs
LG Blue Ray DL
Inateck KU5211 USB 3.2 Adapter
LTERIVER PCE-G2S4 PCIe 4 port SATA 3.0 card
Corsair RM750w PSU
Rosewill Chalenger Mid Tower
X56 HOTAS
Tt esports Commander Keyboard/Mouse Combo
Oculus Quest 2
Thrustmaster 2x MFD Cougar
T-Mobile Home Internet 5G (KVD21)

I haven’t used the frame gen mod because I’m happy with my present set up for MSFS.
My system specs are
Windows 11 PRO
Motherboard - MSI Z390-A-PRO (MS-7B98)
INTEL (R) Core ™ i5-9400F CPU @ 2.90 GHz
NVIDIA GeForce GTX 1660 Ti
32 Gb Ram.
The longest of the 25 flights I had lasted 2 hours so I intend to try a longer one when I have the time. Of all the solutions online for CTD’s they all suggested "use the latest GPU drivers and I think that is where the problem lies (horses for courses), just my opinion.

It’s a varied array of system specs, surely not specific to me, I’m on an i7 10700k, 32GB Ram and a RTX3090, the CPU is really struggling tho, then again no surprise with the 3090 asking for more than the CPU could ever process… The frame gen smoothened things out for me, like night and day, I guess the GPU drivers are to blame, we all have Nvidia cards, I’ll try the 536.67 driver as UrbanerPark suggested.
Will report back if I notice a difference :slight_smile:

Alright, update 1.0

I removed my graphics drivers in safe mode using the DDU tool, installed version 536.67, did a flight in the A300 feom CYYZ to CYUL using the frame gen mod too, v0.81 if i remember correctly.

Not a single hiccup, I’ll do a few more tests when able over the course of this week and weekend (my toddler daughter comes 1st tho)

So far it seems to have been the issue, the latest nvidia driver. Will post updates as I test, thanks for the help so far, I appreciate it :blush:

1 Like

I have tried more current drivers, but always reverted to 536.67, which was (and still is) the most stable, best performing driver I’ve used.

I hope and pray Microsobo doesn’t deprecate it, like they did with my beloved 529.31, which was my previous best, most stable driver.

2 Likes

Thanks for your response and yes I agree if it isn’t broke leave it alone.

2 Likes

Thanks your welcome.

3 Likes

Update 1.2

EDDS taxi to RWY 25, got to the holding point, CTD :joy:

Same old generic crap 0x…05 exception code.

1 Like