I would be very happy if paywares or addons in general were the source of my CTD problems. At least I’d know what to exclude. Sadly MSFS crashes at the same way with the same errors even without addons.
This is not to say that addons can never be the source of such issues, because they often are. It’s to suggest that MSFS can be so unstable at times (or hardware configurations), that it can crash for 100 different reasons with the same error and you can never guess what’s going on unless you stumble upon something by accident.
I have 2 installations of Windows on my PC.
With the 1st installation of Windows, I only have VCRUNTIME140.dll or FlightSimulator.exe errors
With the 2nd installation of Windows, it is the dwm.exe error that I have in the vast majority of cases.
Would this Windows update KB5001391 fix dwm.exe errors, but otherwise?
What are these errors that this KB5001391 update causes?
None now.
If MS is to be believed, they have removed the portion of the update the caused the manager errors over the weekend.
If you had already done the update, I would suggest removing it and restarting before redownloading the update. If you were like me and only do updates when I ask for them and had waited to download it, you should be good to go.
i uninstall two days ago KB5001330 and no more CTD… i profit to update the asus bios for X570, and less stutters over dublin… hasard or memory optimisation as annonced by asus ans amd ? sorry i m french
Still getting completely random crashes. It’s either this error, the VCRuntime error, or sometimes I can go a few days without a crash. My community folder is only a FBW mod and 1 livery that was updated after the latest patch. Do I need to run a modless Flight Sim just to get it to work?
I still have the CTD, but it’s sometimes hours into the flight. It’s something Asobo needs to fix. Mostly it happens when I fly towards land or descend and buildings must be loaded again. But it can also be a coincidence.
today i installed msf 2020 again and i get ctds without any message the last time i had big fps issues but today i have ctds after 15 or 20 mins i cant enjoy my regular flight plan.
i upgraded cpu since last time but i dont think that is the problem
i have a 5600X 32gb 3200mhz a 2070S and 4K medium settings solid 35 to 37 fps until crash.
Do you use simconnect things like Stream deck plugin, Onair, Xmapsy, Flight events, etc?
What addons do you use? Which aircraft you fly in?
Do you have multiple monitors?
Lets find out what this is because i’m doing a long flight now, no CTD yet after i emptied the community folder and not using any simconnect programs.
Specs: 9900k currently at stock speeds, 3080, 32GB RAM
2 screens 4k and 1080p as second screen for maps.
I use Streamdeck plugin and Onair. Both work via simconnect. Mods:
JF Arrow
GTN750
Global AI ship traffic addon
Currently i’m flying the Justflight Arrow on the same route i got multiple CTDs on this morning, uninstalled all other mods and no CTD yet.
Besides, it would be good, if a moderator, could change the subject title, because there is always a message in the WIndows event viewer, after each CTD crash
These ‘error messages’ are just Windows events and are all identical with generic info, they don’t give info about the sim and what happenend in the code. Every software crash tiggers an event.
The software itself should have error handling code, if a mod misbehaves you should get an error message which mod/which part of the sim caused the error. And most games also have a crash reporter that sends a report to the developer automatically so they can see what happens.
Now this is just a guessing game for everyone including the developers. If you get a CTD 4 hours into the flight, good luck with testing that 10 times, it will take days if you have to do the flight over and over.
Ok you are having an issue with DX11 so graphics related. Did you update drivers? Try to pull out the second monitor and test again. Did you overclock video card?
Ok try with a single monitor, without G-sync and without HDR, reset nvidia control panel settings too. And maybe even a uninstall and clean re-install of the drivers.
