After installing the 737-800 I began having the crash and memory error while it was in the final loading stage. I tried removing the EXE file but it happened again. I recently installed AMD’s adrenalin software and from what I have read this may be related to drivers and more specifically audio drivers. Back to the drawing board for me starting with a reinstall of AMD…
UPDATE:
After UNINSTALLING AMD on my pc and its affiliated sound driver I am no longer receiving a memory error. Will continue to troubleshoot and attempt to isolate the problem.
Not sure there is any documentation about automatically creating a new exe file. Where would it obtain the info to recreate it especially if some 3rd party apps add their own info to the file? The 3rd party apps can be installed anywhere, not in one place like the Community folder.
With other recent mods also being blamed for these CTD, it is starting to look like the mods the sim loads into memory at start-up do have an effect, regardless of the code inside the addons and how well it might work.
Simplistically, MSFS differs in the amount of memory it uses, depending upon the mods in the community folder, and possibly affects when and where the exception that causes the CTD is occurring. Perhaps the more mods you have, the more likely you are to have a CTD, regardless of exactly what mods they are? I know that some people can get this CTD, even with an empty community folder, so there must be something else going on, but mods do appear to be a factor.
I really hope that Asobo can get their heads around this one and get a fix out shortly.
I got a new beefy PC about 3 weeks ago as well to replace my lower end PC. I have gotten more CTDs with this new PC in 3 weeks than I did for the 2 years prior with this sim in my lower end PC. My new PC is overclocked on all cores so I am thinking about turning off the overclocking to see if that helps. I have 32gigs of DDR5 5200MHz RAM and I already disabled XMP in BIOS to see if that would help but it hasn’t so I guess the CPU overclock is the next to turn down.
we should mentioned, that the error from @biggathebeast is “memory could not be written”, instead “… read”: see its own topic: Random memory crashes?
And yes, OC was one possible reason for that and others too. But because its a different error, we come bit off-topic then
Hopefully not. But I mean… shouldn’t we expect Microsoft to support current hardware? They’re not exactly a small company. And I’m not saying that hardware is related to this. But there must be a reason why some people with certain system configurations get these, and others almost never get any CTDs. It’s such a mystery!
as mentioned… if we find the root-cause, we made a party
Currently we have all that “possible” solutions, which helps some users and some not. But, the state is “bug-logged” , so affected users know at least that they are not forgotten.
Yeah, that would indeed need to be celebrated big time, lol
Just super frustrated as I’ve spent so many weeks of this issue. One minute it seems that I’ve fixed it, then the next minute another CTD. At the moment I’m getting reluctant to start a flight, as I will never be sure if the flight will end at the runway… or on the desktop. So sick of seeing that error message.
For chronic errors and crashing, I highly recommend a complete uninstall, reinstall. This has worked on Xbox, where corruption from either the update process or layers of updates results in random weird behaviour and crashing. And uninstall / reinstall results in a much more stable instance (at least for me).
What works for me most of the time is to turn off AI . This has resulted with no crash with the MCBR error most of the time. It does come back from time to time but at least I’m flying and not crashing all the time.
