When Seb actually said nearly all the crashes come from 3rd party addons I find it strange you can’t rename your community file and create an empty one in the same location and just include what you need for your flight … if you still have problems it will be a lot easier to troubleshoot and once you have found the problem you can remove it and rename the original back to community.
It’s not a fail safe solution, for that you would need to uninstall them properly but I can tell you now that you will wait a long time for Asobo to bugfix 3rd party mods because it just isn’t going to happen.
Then sandbox your core app in a way that 3rd party addons cannot cause crashes but only recoverable errors? It’s been done for years and it’s called exception handling. They knew from day zero that MSFS would be heavily dependent on addons, yet here we are 1+ years later.
Funny none of the 284 other games on Steam I have ever had CTD issues nor any production application on my PCs have CTD issues.
Connected devices: Wired Logitech mouse and keyboard. Do I need one from Microsoft to play FS? And a display as mentioned before. There are no other connected devices and devices on board (Motherboard) which are not used are disabled and thus have no installed drivers.
For my GTX/RTX card I have tried about the last 10 different NVIDIA drivers. This is no driver issue, the CTD issues are the same with any driver version.
AMD chipset drivers have always been the latest available. They never changed FS CTD behaviour.
Sorry to say that but a lot of the recommendations made here are total nonsense. Just to name examples “run the game as admin” (no the game has to work with user privileges), “increase page file size” (if not enough RAM is an issue the game has to throw a user readable exception and not just CTD with no specific error logged, with 32 GB of RAM and even with 16 GB of RAM the game shouldn’t have issues even without page file), “turn off XMP memory profiles” (funny every other game and app has no problem with XMP profiles so it would be completely logical that FS has a problem with it). It’s not that I haven’t tried all the recommendations here against common sense but to no avail.
Anyway … it doesn’t help praying the same things over and over again. When I use Windows 10 certified hardware, have a clean install of Windows 10 21H2 with only Steam and FS standard version with no mods installed I simply expect the game to work without CTD issues. A clean install of Windows 10 21H2 including out of the box drivers or vendor drivers doesn’t make a difference to the CTD issues.
with the logitech app running ?.. I remember some older issue about a specific version ( may be it was also in this topic )
… with the GPU … there are lots of other drivers and of course the hardware itself.
pagefile settings was a long time one of the main issue. Also some user assumed they can disable pagefile because the own 32GIG , which is a big mistake. You have to ensure that your system can reach 32GIG memory. And its not the game about we speak, we speak about the whole system.
Similar to XMP profiles.. a lot of users had trouble with that.
The most of the hints, given from community, needs 5 minutes to try. If you not want hear hints from community, I ask me why you joined into
There must be a reason why so many people can play without any single CTD.
My recommendation:
check that all drivers installed ( also these one for chipset, etc. )
check the sound-driver topics
recheck the hints which you call “nonsense”
1-5minutes crashs are often ( not mean allways ) system stuff : may be limit your fps in NCP to a low value
be aware of hints like filesystem format ( not exFAT )
try disable photogramm… ingame
may be try the explorer kill workaround. In case you have nothing else installed an this will work, I would be bit surprised, but who knows.
check the existing .NET error topics
also show us the whole error message. There are ..005 log which mentioned a specific dll
some ctd have nothing with things i will talking about but, i have most unstable game for me is far cry 4, and after i restart pc before play this i have 2 may be 3 ctd when i almost replayed it, something in window’s soft conflict with it, you can close everything but something stay in memory, what give you ctd, so, i suggest before long fly restart pc, and may be your ctd will gone or will reduced significantly… what i can say in collective - some game is stable, some game very stable, some game super stable, and some of them just unstable whatever you do, but, even super unstable like far cry 4 can live without ctd almost… this is not normal situation, but it is how it is… and if you have “xmp on” for your memory, go to bios and use manual voltage for sa and io
in the picture you have 3 voltages, what you must to use only manually, in picture you can see sa and io voltage in auto mod, and this is was cause of my memory stop works at all, till i remove all sticks and add one by one, then change voltage to minimum it’s stay stable…
Application: FlightSimulator.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FF6F362B677
The exception code is a non-specific access violation. So not very helpful. I have tried to debug it with developer mode but that didn’t give any hints as well.
I have the least possible hardware installed in my system to keep driver profiles low and only WHQL certified production drivers (usually the latest versions) installed. I know there are more than GPU drivers but usually when drivers cause crashes I get error messages reflecting the driver DLL causing the issue. This is not the case with the FS CTD issues (see error message).
I don’t know what Logitech software you are talking about, but a wired keyboard does not have any “special drivers” except the WHQL drivers included with Windows. And even if the Logitech keyboard drivers are causing FS to crash … you ignore the fact that 284 other games in my Steam library and all the apps I use never had any such issues. I am not saying every other software is bug free, that’s not what I expect, but I expect crashes to show/log error messages.
My page file is usually set to the default setting (managed by Windows) and not disabled. I have tried Windows with out of the box default settings as mentioned before. It doesn’t stop CTDs.
If these settings are not right then you would have general instability issues with your system and not just a single game. E.g. if you overclock RAM other games may crash too. If you undervolt your CPU to too low values the system in general will be unstable etc.
there is Logitech Gaming Software / Logitech G Hub … as example for creation of game profiles.
Of course I not speak about normal keyboard drivers
you understood that wrong.. I summarized a lot of reports with the comment " all others works " and where we searched then in wrong place, but at the end was, as example, the root cause the xmp mode ( no other game stressed the memory in former releases in this way ).
Of course is allways a chance that the game have a bug ( more exact I assume the game have a lot of it ), but these 1…5 minutes issues are so often not caused by the game ( but again, not allways ).
We can only give hints what you can try and may be you find “the” usefull hint. It similar to users which used some kind of vpn: nobody had expected that this caused strange issue, but in a discussion the communtion find it.
to be sure..
These looks also okay, but can you check that : Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\1033\Release
contains 528372 ?
Not a CTD per se, but I just fired up the sim to test something, exited to the main menu, then quit to desktop. The sim stopped as I expected it to, but the following event was created:
I’ve seen a few of these “shcore.dll” “errors” appearing on the list, and never saw an issue.
hmm.. never seen these log entry.. I checked the file and I have a newer version “.1266”. The update time was 2.10. and this match with install of latest cumulativ update (KB4023057). May be its a windows thing, but also not seen that before the update.
