Yes hopefully they are seriously looking into this. I don’t know how much time I’ve spent troubleshooting this issue. And my system is pretty much brand new, custom-built, 12900KF, 3090, DDR5, high-end motherboard, PCIe 4.0 SSD and a 1600w PSU. Fresh win 11 install as well as fresh MSFS install.
They answered my support ticket quickly though, and have asked me to send them more information, which is a good thing. And this topic is bug-logged.
But yes the issue is extremely random. Yesterday I was able to complete a near 2 hr flight to my surprise. I definitely get the CTD less frequently after reducing the GPU core clock. But it still happens unfortunately.
With a new install HAGs is on by default yet for me it brings nothing to MSFS except problems. If you haven’t turned it off already it can be found under System/ Display/ Graphics/ Change default graphics settings.
I fear they will need more time than SU10 beta to resolve this issue. It got bug-logged not long ago.
As for my troubleshooting, I’ve gone 100% vanilla MSFS as per Zendesk instructions as they suggest my issues “indicate a conflict with third party software.” Which could very well be true. So far I’m about 2 hours into a +5hr flight in the stock 787. No peripherals except keyboard and mouse connected (not even my Xbox controller). This troubleshooting is very tedious, but I’m determined to do what I can to resolve the issue.
This error isn’t really a MSFS problem, but more of it highlighting a looming hardware issue. There’s been a variety of suggested solutions that work for some and not others, which only adds to the complexity. Fortunately, a lot of users don’t have this sort of error, so I don’t think the finger can be pointed only at MSFS.
I would suggest people to be more active in identifying potential hardware issues on their setup, rather than “waiting” for Asobo to fix the issue.
Not sure if that’s the case here. Just want to repeat that I’m on a completely new build, very high-end hardware, fresh Win11 install, vanilla MSFS install. I suspect there’s some component of hardware incompatibility to this, but I still feel it’s on Asobo to ensure compatibility also for very high-end systems. That people have invested (a lot) of money in. To make this sim run as best as it could.
But I do understand it’s out of the scope for Asobo to provide support for third parties.
If this was the case then surely this thread would not be tagged bug logged?
Hardware has been my my main theme in trying to track this down. My system is 12 months old and only used for MSFS. I’ve been through it testing everything. All tests have found no hardware issues even done overnight memtests. Everything is stock with no overclocks. And still random read errors.
Yea, but realize there’s plenty of us on high-end systems that don’t have this problem. Unfortunately, with an almost infinite number of hardware configurations on PC, it’s almost impossible to ensure compatibility.
It gets tagged as bug logged once enough people vote. It just means Asobo is aware of the issue. It would be interesting to see the inverse - how many people DON’T have this issue.
Again, I’m not sure I agree. If this would be true for Windows… But as I said I am looking into this in terms of my own system. Default BIOS, GPU to stock values.
It means the issue is being tracked in our internal bug logging tool and the dev team is actively investigating and/or working on a fix. It is not confirmation that it is a bug with the MSFS software itself. It could be a problem caused by individual players’ hardware, mods, background apps, security settings, or possibly even a combination of both hardware and software. As many posts in this thread indicate, this particular memory error occurs seemingly at random. Some players are reporting they can never complete a flight of more than a few hours without getting it, while many other players (myself included) never get it at all.
Considering I have the same hardware/software as the first day I installed MSFS at which I never received this error until this past April 2022 when MSFS did their World Update. It is in no way my hardware. The best repair would be to give paid software users the ability to revert MSFS back to original install without any World Updates. The program was running perfectly back then. MSFS doesn’t even offer this and make World Updates Mandatory. I could care less about elevation, clouds or weather improvements. This error is getting old!!!
It is not MSFS which crashed in that case, it was not running. With the same error " Navigraph Navdata Center.exe" crashed.
As the issue started there was also a windows update, and beside of the hardware issues was that the first big trouble maker. For some users it “killed” the system-sound-settings and correcting that, fixed the problem for lots of users. But then we got additional reports and we come back to the hardware/driver stuff ( or still a windows-x thing ). The main problem is, that with the MSFS update also a windows update comes out and so we can unfortunately not ensured say it happens because of “msfs update 9”. But I will never exclude a relation to MFSF itself, its complex application and who knows, but then I ask me why only “some” users see these error.
And, it have nothing to do wiht “high end” or “not high end” as some users mentioned. The issue was reported also from users far away from high end.
And be careful thinking that with auto default or auto optimized BIOS setting all must be ok in settings in hardware side, that does not mean an stable PC or CPU etc..
Not for all but for me this is one of the causes sure, and not the only cause sure too.
W11 SU9, PSU 1000W
MOBO Z690
12900K, 32GB DDR5 ok (despite it isn´t in the list of supported DDR5 of MOBO)
3080Ti
Same issue from my side.
Configuration:
i7 12700k
32GB RAM
RTX 3080Ti
For some days I could reproduce by using ingame navigraph charts. After deinstalling the ingame toolbar, this did not happen again - but might just be coincidence. As per my stomach, it might be navigraph plugin related…
On my side on vanilla MSFS hence no Navigraph I still get this CTD. I have been able to complete one several hour long flight, but I still get the CTDs, only infrequently. There seems to be no pattern to it.