Crash to desktop without error message

I haven’t experienced CTD’s since the game launched (which were caused by my old bluetooth keyboard that I have since replaced), but I’m getting them now after I haven’t flown much since WU3, but prior to that I never had CTD’s after switching keyboards.

Mainly caused by VCRUNTIME140.dll, as others in this thread have reported. I did recently install some software that installed additional C++ libraries, but I have uninstalled those to no effect. Running Just Flight’s new Piper as well, but I don’t really feel like uninstalling a bunch of stuff. Will just stick the sim back on the shelf for now…

1 Like

Bluetooth keyboard? Hadn’t heard that one before. Seriously, the number of different ways that MSFS can CTD knows no bounds apparently.

I’ve managed to crash it twice myself in the past 10 minutes by simply pressing Windows key while in the middle of the flight (again this is new as I hadn’t seen it before). I’m pondering the idea of raising a separate ticket with Asobo every time the game crashes in a different way.

3024 comments and counting. Still waiting for a fix that will make the game stable.

Thanks for the tip, but it didnt help. Screen froze just as I was starting to taxi. will ctd in a while when it has finished sending the dump file. Which of course I send to Zendesk who just ignore them.

I believe they made the bluetooth peripheral issue better, but the sim used to CTD when low power bluetooth devices went into power save mode and were woken up again.

I was undervolting my 3090 via MSI Afterburner. Went back to stock and flew for 2 hours without a CTD. Re-enabled my undervolt profile and flew around for another hour with no issue. Not sure if that was actually causing a problem or if I just got lucky… I’ll continue to fiddle with MSI Afterburner if I CTD again.

It sucks now. Time wasted again. Four flights on the same IFR route from LEMD to EDDF and each time a CTD, after a usage time of around 1h 30 minutes. In the case of commercial software, lawyers would write.

edit: on the route - PINAR UN870 SEGRE UN871 DITON T163 EMPAX

It’s a bit of a pain I’ve never had a CTD now since I set up flight on world map press fly immediately ctd this after patch only.
So did a clear out and full reinstall of sim and end up with same result.
No changes made to system.
So disappointed as before patch no problems.

  1. How many version of the C++ libraries do you have installed?
  2. Did you have any external tools using SimConnect, such as LittleNavMap, Volanta, Navigraph Charts vis SimLink?
  3. Any CPU, or GPU overclocks?

Just uninstalled all extras like simshaker littlenav map etc.
Did a full system shutdown rebooted now on second sim reinstall :crossed_fingers:

Guys - please give this a try. Worked a treat for me. No more stutters or crashes

1 Like

@CatapultF4E Public link: GitHub - AmbitiousPilots/CPUAffinityForFS2020: Batch file that launches Microsoft Flight Simulator 2020 with custom CPU affinity.

a like but a link which currently not works… yep…

( can you made it public ? )

still not sure what should this change :wink:

Have a look here, there you’ll find more details: [FIXED] Random CTDs due to internet and hardware issues

1 Like

yes… I seen this long ago, but also with it I still not sure how this should avoid a CTD if the Fl…exe is shifted to another core or limited to run not at all cores. If this would be an issue, then we all must have a CTD and need to change the affinitiy :slight_smile:

My only idea was, that CPU Turbo modes comes in steps at the cores and the user system have an thermo issue. But was also not sure about…

Example: in my case (i7-8700k) the cpu11 is the one which msfs use in 100% . I can simple shift it with the affinity to another core, but it makes not different and this in special because I use kind of overclocking “Sync All Cores” : so all my cores run in 100% Turbo Frequency.

But of course: users can try that. But for a “Try” they can also simple use the Taskmanager :slight_smile:

The reason why a custom CPU affinity mask might prevent a CTD is, that when Windows is low on resources, it is forced to free some in order to prevent a system crash or BOD. Thus, it shuts down all resource intensive processes in order to save the system from crashing.

So any CPU core that is left over for anything other than FS2020, allows the system processes to utilize this free core alongside the demanding tasks of the sim. This however makes only sense for CPUs with more than 4 cores, as DX11 uses 4 cores and anything lower than that would lower the overall performance.

And of course people can try this via the task manager directly. That’s how I described it in my performance forum thread :wink:

hmmm… I’am so often in 100% load ( real load ), never seen that windows killed my game :slight_smile:

But I think I understand the idea behind : let one core free for the system…

It might be interessting for which kind of CPU this would be helpfull. Possible a list should be created where it was helpfull.

Here you can see a switch where I disable Core0 and it jumps to another core.
( note: I made former a test-case, normaly CPU11 is my 100% core… and it is not a full-load scenario where also all other cores in near 100% load ).

PS.: DX11 is not limited to four cores,… the most games only use max four cores.


ah yes… I should think about more within the other topic :slight_smile:

1 Like

OMFG !!! 3rd CTD now after the patch !!! No stutters but CTD !
How can they be so useless ?
I am beyond frustrated !!
This is the next Cyberpunk !!



I tried it and found no issues… IFR, all live, used Navigraph, …

1 Like

I have the same, second flight after update, one hour and CTD.

ando also some sudden freezes out of nowhere !!

1 Like