I never had Acronis backup software installed.
Only suggesting you might want to check Core Isolation in Windows Privacy and security. Should be able to find it easily through the search bar. Can’t say whether you will find anything or not, it may have just been a coincidence.
Me neither. At the time I was deliberately testing a memory overcock with Gigabyte’s Aorus and had nothing else but Windows loaded. It’s a week old Windows 11 install and I only ever back up manually.
Looks like a driver issue, you need to DDU before reinstalling. Install gaming drivers custom install and untick GeForce, you can always add it later.
What does DDU mean (sorry I m native German speaker) . You mean the graphics card driver? Found that How to Clean Install Graphics Drivers Using DDU - The Proper Way! | Clean Reinstall Uninstall | Easy - YouTube
Yes, a clean install using DDU softeware to clean all remnants of old Nvidia installs. It’s run in safe mode or you can simply run and re-run it in your normal Windows. Be sure to get it from a reliable source.
Yes: just follow his instructions
I’ll run the sim in developer mode for a few days to see if I crash due to memory limits.
I just ran the sim with developer mode enabled and it crashed with the graphics device problem message.
However, the developer tools showed that the memory consumption was well within the limits for my system.
I have 32 GB of RAM and 24 GB of VRAM and neither is used more than 50% when this message shows up.
And I never got a CTD on start-up before, but this message showed up on the first attempt to start the sim after today’s Beta update and resulted in a CTD.
So while memory might cause it, there must be another reason to trigger it as well.
Guys this message has no sense and it does not help either. It´s a debug info, so either you print it on the log or you put it in a banner like the “online services not available” one. But this forces a game closing without user even being able to change the settings to prevent it and before the error is even reproduced.
Cheers
Just had the same message pop up and I’ve not changed any settings. Only change was the sim updated to latest Beta. Also not had any CTD’s in a long time…definitely some overly sensitive feature that’s been added with this latest version.
They probably added a test on return value of each call of all (or most) graphical functions, to check if it was successful, and if not, display this generic message. Could be no more vram, or anything graphic related (a vast topic). They need to narrow the issue…
I got this error as well when I first loaded a flight after updating. It happened immediately after entering the cockpit after the preflight cinematics. I’ve never seen this error before. Either it’s something new that was added this latest build, or something was changed to trigger this error. I had a slight overclock that never caused any crashes, but I removed it for now to test if this error comes back.
The only thing I can say for sure is there was no overheating of the GPU. VRAM consumption was ~12 GB total consumption on my 3090, but that’s very typical for my setup and not excessive.
Before If I got a freeze or studder it would just recover not crash the sim. CTD for me was 99% only on Sim startup. Seems the auto recover is no longer working because now it triggers this message.
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:
I have a Premium Deluxe + all WUs and CU1 installation. I’ve launched the sim multiple times today and never saw this message until now. Nothing has changed on my system since the sim was updated.
EDIT: This message appeared at the launch of the sim. I hadn’t even gotten into it yet.
Are you using DX12?
No
Are you using DLSS?
No
If relevant, provide additional screenshots/video:
Never had this error until this release either. Will try turning down graphic settings as suggested…
RT5700XT (Driver 22.8.2)
R7 3700
Reverb G2
Win 11
SU10 beta18
DX11
My summary: I installed the graphics driver from scratch (DDU). I loaded again, this time with a different aircraft, onto the payware scenery from EDDH (Justsim, Hamburg) and immediately this error message came up very briefly - but this time immediately without confirmation CTD. Then again without the scenery - and everything was loaded. For whatever reason - this scenery crashes. The error message is new and came with the MSFS update from 08th Sept.22. Furthermore, I have observed that the frame rates are worse. Before mostly at 50-60, now at about 32. Apparently reinstalling the Nvidea driver didn’t help either. I’m convinced that MSFS / Asobo still doesn’t have the memory management under control as far as the GPU is concerned. I never had any problems before the SU9. The first SU10 beta (first release) brought me a real performance gain, but the subsequent releases brought back the problems of SU9. Sorry, Asobo, it doesn’t work that way, at least as far as PC users are concerned. It may be that a mod makes problems. But something is wrong here. This is probably one of the reasons why the official release of SU10 has been delayed. I know it’s just speculation, but many users have this problem from what I’ve read on the forums.
ADD: Now I believe, there is a bigger problem behind - even without so above named software/mod (EDDH) the error message appears - in the start menu of MSFS. That never appears before and should be a bug that appears since yesterdays MSFS small update / release of SU10beta.
Unfortunately, I have to assume that Asobo generated this new error message to shift the responsibility for the memory problem and CTD onto the user - who now thinks he caused the error himself with a bad graphics card or driver or overclocking - which seems to be a bad thing to act memory management with regard to the GPU memory management. As I said: BEFORE SU9 there was no such thing. The problems have only gotten worse since then.
It pretty much crashes while loading the world every time now. And memory consumption is well WITHIN the limits of my system every time. SU10 is pretty much unusable now.