For me it is obious, it has something to do with the way the audio is produced. I did so often read that the crash happens when clicking a button in the cockpit, for me it always happens when there is ATC communication. After their last hotfix update i get different error messages in the event viewer:
And i have to say if i fly over New York, it does NOT crash, i can fly there without problems, it seems there are faulty regions, combined with the internet network traffic, combined with the ATC audio.
i think it is a general problem with the way they play audio. I bought a new soundcard because at first i thought my x-fi titanium was the problem but with the new card nothing changed.
I fly VR with the reverb G2. At first HP did release firmware updates to fix audio problems, have installed all, but i don’t think that changed anything.
With SU 5 my AMD ran rockstable, it did not crash once and the crashes were re-activated with SU 6. But i still think it has something to do with the audio engine.
here is a video over new york, at the end of the video i added a short take off from innsbruck ending in a crash to desktop, that shows how it 90% of the time it ends.
ah… have no experiance related to VR… best would also be to switch to VR category then
Only know that sound-driver related issues are common… you tried allready things like disbale nahimic service, etc ?
EDIT: I forget… and may be realy try the windows-offline atc… since the issues in first ages of msfs with that, I still use offline only ( not necessary to cause extra network traffic if my pc can do that itself )
i don’t know what nahimic is, is it related to msi/asus tweaking tools or something like that? Don’t have something installed.
Did you check the video i have posted some minutes ago? after the first flight there is a second take off added which shows a ctd.
there is a windows service ( services → search for nahimic → deactivate )… often worth to try… newer versions should no longer made trouble, but who knows… ( a note: this service will sometime auto re-activated and this was a big issue in ages where this service caused realy lots of crashs, not only msfs )
yes… checked the video… atc speaking and crash… may be random, but can of course relates to atc voice ( therefore the windows-offline setting ).
i just checked, this nahimic is realtek related, right? i don’t have realtek drivers installed, using a creative AE-7. I also didn’t find the service in msconfig services, so it is not running.
yep… then, we can assume no issue from this side in your case… then currently only idea with the atc offline voice ( sounds a bit different than the online voice, but is ‘okay’ )
In case of OC, MFS is simply very sensitive to not 110% stable OC. So if u have CTD and OC it is very possible that is not as rock solid stable as u think. Solution for this is disabled OC completely if you are not a power user (for example using auto OC), or tweak OC settings (lower clocks or increase V) for better stability. The same solutions are for people doing UV (Undervolting).
For sure.
MSFS does not like overclocks at all, no matter how stable they seem.
I have seen a few instances where they worked, but in almost all cases they led to CTD’s
U see CTD when OC (system) is unstable.
Believe me, I played almost 8 months on system with OC and I didn’t have CTD.
I play now on system with UV and I still don’t have any CTD.
It’s a matter of stability of the system. Nothing more.
Of course, CTD will still be happening from time to time. MFS is not 100% stable itself, especially with Community content. Maybe this is why is so sensitive for unstable systems.
When MFS came out, it prove to me that my OC was in fact unstable. This is a lesson that i learned with this sim. Little tweaks and problems with CTD gone with OC active.
Asobo should implement a stability stresstest then, to check if the system is ready for the load.
I would really want to see the Xbox versions doing that, ending in blackscreen & crash to desktop
This community is too big to say that every system is overclocked by everyone, thats too simple.
I usually overclock my gpu memory but that always incudes an overnight burn-in test which has always been a good indicator however recently I’ve had to wind it back to near default again. At least my CL14 PC-3200 ram is still behaving itself at 3600Mhz.
)
