It disappeared with version 1.27.20.0, but returned with the literal regression to 1.27.18.0. Now I’m again, not able to fly for more than 2 minutes without a CTD (In case I’m able to, since most of the times I cannot even reach that point at least)
2 Likes
Do you have the same issue if you follow the OP’s steps to reproduce it?
yes
Provide extra information to complete the original description of the issue:
This crash happens when trying to pop out displays(pfd,nd…)
Are you using DX12?
Yes
Are you using DLSS?
No
If relevant, provide additional screenshots/video:
Welp don’t I feel the fool.
Turned off Resizeable BAR in Bios, less messages.
Increased fan curve and then later increased OC out of spite same.
Disabled HAGS who had become a friend recently, no message.
None.
2 Likes
Nonsense. What kind of conclusion is that, and the advice based off of it?
Their PC is fine. The solution to a technical issue that only appeared in a beta in the last few hours is not, nor is it ever, to buy a game console. I can’t speak for everyone here, but I know my computer is far more powerful than an Xbox Series X.
The solution is for Asobo to investigate, and fix.
Thanks.
7 Likes
I’m still running the same settings as far as graphic fidelity however turning off Resizable BAR (bios) and HAGS (Windows graphics) has completely eliminated the issue as far as I can tell.
That’s good.
I don’t have Resizable BAR and HAGS is off in my case.
@TheGreatHadoken Totally agree. The only thing that has changed is the new beta release, the problem lies there and nowhere else.
1 Like
The only other thing it could be is they have changed something server side without an update.
As for not having Resizeable BAR is that AMD, very early Intel, is there an AMD counterpart?
6+ hour flight and nothing, I’m dumbfounded.
Isn’t Resizable BAR something on the new Nvidia GPU’s? I’m on a 5900x and 2080ti.
It’s an intel motherboard thing since Gen9
Ah, good to know 
Smart Access Memory is the AMD equivalent to Resizable BAR as far as Google says.
As I’m discussing here in a much less heated fashion I was able to complete lengthy flights without issues after some modest tinkering without lowering graphical fidelity.
Any “Improved Memory Share” in both having hardware/bios level (Resizable BAR) and software/OS level HAGS seems to have been cause for the error … (at least for me) … when Hardware and Windows tried some actions to more efficiently use VRAM.
It may not be a panacea, it may not even fix one more users sim but it’s something, it’s clearly something.
Edit: And as always, specs are in my profile-sig, it’s the least any beta tester should do.
Which is why it’s baffling and dumbfounding that you’re encountering the issue. As your specs are very high end. I’d be utterly amazed if you ever used all 10GB of VRAM on the sim.
Switching off HAGS can’t be considered a loss. I haven’t seen a single convincing proof that HAGS has any performance impact whatsoever, but I remember at least one time in a previous update, where switching OFF HAGS did reduce CTDs for people.
In my case “Smart Memory Access” is also doing nothing to improve performance on my 5950X, so I don’t care if it’s switched on or off.
There is definitely something to this.
I have been working with nVidia support to solve an issue with MSFS 2020 and the nVidia GPU Activity monitor that lives in the taskbar that can be enabled from the nVidia Control Panel. I had recently noted that it no longer showed MSFS as using my nVidia GPU and this was puzzling.
After reading your comments re: HAGS, I turned it off and now the nVidia GPU Activity monitor is back to showing that MSFS 2020 is using the GPU.
I don’t think there was ever a question that MSFS was not using the correct GPU, but it was really odd that the indicator would not work anymore.
There is something whacky going on with HAGS and MSFS.
Here’s the way it was looking until I turned off HAGS (nVidia GPU Activity is in the lower right corner):
And here is how it looks with HAGS off:
Note: Other applications would show up in the nVidia GPU Activity monitor if I set them to use that GPU, so it wasn’t a universal issue with HAGS. It was only affecting MSFS.
1 Like
A fix that worked for me was to not run other apps alongside the sim. I’m not talking about the sort of apps that open up automatically WITH the sim, they seem all fine. I’m mainly talking about running a web browser alongside the sim. HAGS has always been off in my case for years although I suppose I can double-check that. This works for me 100% of the time, unsatisfactory a solution though it is for many of us, particularly streamers, etc!
You may be on something. I was away from my machine for a few days. Got the latest SU10 update yesterday. Made a couple of flights under VR (Reverb1), no “problem enountered”.
Today, I didn’t use the VR goggles but Opentrack for driving my Grassmonkeysolutions Puck. Got three “problems” in a row, either immediately after starting the situation, or after a few minutes.
Next, I deactivated the Grassmonkey Puck and Opentrack and voila, I could complete half an hour of flight without the “problem”.
Certainly, that’s not enought of statistics, but the latest update might have an issue with interprocess communication.
I should add, I very rarely had CTDs so far and could nearly all of them trace back to faulty or incompatible addons.
It certainly will not help to exchange the error message by another one, the team has to find the root cause within the sim.
1 Like
Switching off HAGS didn’t change anything for me.
New update, same issue. It didn’t happen in the original non-rolled back .20 I could try for a few hours some days ago… What a pity…
Running the new 21 on my pc. Initially had 3 CTDs and the warning. GPU overclocked (but stable on all builds before) so I turned that off and had a few flights successfully before bed. No issue so far but overclock fps in 60s and reduced to 40s and 50s at stock. We’ll see what tomorrow brings.
I9900k
64 gig ram
Gigabyte Vision OC
DX11
1 Like