interessting… not that again HAGS made trouble. I have this Off… it was just to random that with an update of windows or nivida the whole PC run into reboot issues ( not game related ).
But if I read this here:
… I can only recommend: dont do that… the 1fps more is it not worth
I took part in the livestream earlier, and decided to turn off the scenery cache for once. Flew for nearly 2 hours in the vicinity of many other players in all sorts of aircraft. No stutters, or crashes.
Afterwards I repeated my flight, in reverse, that gave me two CTD’s last night, from Meribel ro Courchevel. No crashes, and I spent about a half hour or so doing landing practise.
I think I may continue with no scenery caching for a bit.
Just before the infamous SU4 came out NVIDIA messaged me of an update and I accepted it. Now CDT after CDT, after futilely trying every fix recommended on Youtube, I decided to try to roll back my graphics card driver to that which I was using with SU4. This CDT problem is totally new to me. Never had them with MSFS since its inception. Unable to find a way to do it within NVIDIA , I contacted support and they helped me find the version of my old driver and install it. So far I have not had a CDT and prior to my rollback I couldn’t even start most flights let alone complete them.
Could this be an added glitch to those of us with NVIDIA graphics cards? I had already changed from gaming to studio setting as recommended but that alone did nothing. More testing necessary but so far seems to be the light at the end of the tunnel on this issue for me.
Everything seems to indicate that these crashes are not Asobo’s problem. Exactly at 6:30 am on June 6th, on July 27th, my computer broke down.
But what is mysticism?
It is worth literally for a second to take a look and run, for example, the X-Plane 11.55 occupying 370 gigabytes and installed on the same one terabyte new ssd disk, specially purchased for these two simulators. With a huge bunch of orthophoto scenery, plugins, airplanes and external programs - all sorts of Active Sky, LittleNav or Pilot2Ats. And this ■■■■■■■ (bad) computer is instantly repaired, the X-Planeworks like a reinforced concrete, it is simply impossible to crash it … Moreover, the load on the processor in it will be even more, it takes up the same amount of memory as a video card. Moreover, the PC does this on old drivers, and on new ones, with or without patches, with any sound or usb devices.
I’m trying to bring the PC to clean water and run a 16 gigabyte virtual machine with a production environment and working with a 3D environment - also, the infection does not fall into any.
And it is worth for a moment to stretch the mouse to the MSFS icon and the PC breaks down at the same second …
Looks like I need to think about changing the computer. (Not really)
ähmm… yes, at least you “try to run it in parallel” :). You have MSFS running and then you start the VM. For a game which needs hardware in the way like MSFS it does ( may be other games too ), I would not wonder about issues. Also a VM ( MS or Oracle ? ) try to reserve pieces of hardware for its own ( RAM, GPU resources, etc. )… Thus, for me not a good idea to start a VM… Fly and bring your passangers safe at home, or work within the VM
I gave an example of a working highly resource-loaded virtual machine simply as an illustration of the fact that, with a very high probability, the problem is not related to the system environment or the hardware component of my personal computer.
I think I understand now ( with my Google-English-Knowledge too )…
But a VM itself isnt realy comparable with a game… it’s just a VM within limited resources.
The only hint I can give, in special if the CTD happens some seconds after starting the game, that it points often to overheating issues ( we had not less cases ). Test cases with limited fps , e.g. nvidia control center, can help to find this out. Of course sometimes also the drivers are the bad-boys.
But I have also seen that you have VR hardware. We have older cases where users run into ctd since the installed the vr softrware/drivers.
And the last hint might be the memory XMP mode. I seen you own 4300’er which is , for me, nothing else as Beta-Test-Memory. May be do some tests without xmp, or with lower settings than 4300.
Since the latest update, I can take off from a busy airport in VR without issues, but crash out 30 mins into the flight close to cruising altitude on the monitor, when not one bit of my hardware is stretched.
So I cannot even start looking where the issue is. Ridiculous.