If you’re in the beta I think that’s just a switch they forgot to disable. Anyway it’s not graphics.
Spanish not my strong point but the small blue writing should say something like more settings, try to choose a high power or ultimate setting
this it translate ;
when plugged in turn off the screen after 5 minutes
when it is plugged in, suspend the equipment after 15 minutes
Default items
click on small blue text
Im now back on driver 517.48 without any issues and system health is OK. In my case it is a driver issue or you can say an intercation issue between driver and OS.
1 Like
Yes I believe that is a stable one and it’s recent enough to be useful, well done and others take note.
FYI: There is a video on youtube about the driver issue
Desktop Window Manager High GPU Usage Fix (Nvidia GPU).
The 100% at idle with last driver have been reported several times in NVidia forum.
1 Like
I still believe its a little issue with how the “engines” are reported, and may be only happends for some kind of gpu models. If you GPU would realy be in 100%, then it would be not cool idle at 45° 
But good to know …
WDDM driver has no direct relation with non windows system graphic processing, & for the record, iam using the latest nvidia driver and i have no issue with WDDM power usage in idle state.
I got this message after turning on “hardware accelerated gpu scheduling”. Stopped after turning it off again.
2 Likes
FYI I am on latest driver and also have hardware accelerated gpu scheduling enable and not getting any high GPU usage and haven’t crashed since setting to DX12 and DLSS on for my 3070FE.
I did get the error early on after the update but it went away, most likely when I change my setting back to DX12. Got it while in VR mode.
I revert the version of the drive to 517.48 (nvidea) and now is running very well.
I have started getting this message, the sim normally crashes every 3rd flight or so. I am running the latest graphic drivers and latest version of the sim. RTX2060 Super. PC is definitely not overclocked or running at a high temp. Vents are clear of dust. Hope it is sorted soon.
People having this issue (I have it twice and not anymore I don’t know why) should really try a simpler fix I read here, as it seems IMHO the only logical one: Try to reinstall the graphic drivers right before flying. I mean really just the graphic driver, not all stuffs around it, to keep it quick and clean. So far all people doing this have success unless I missed one post (still possible).
Edit: the logic behind this is MSFS breaking something at driver level. This happen, I test lot of Alpha and Beta apps and it happen.
1 Like
Indeed. I switched to DX12 with new driver . It works!
1 Like
The latest driver seems borderline and unstable for some … Some are reporting 517.48 is better.
PS if it’s a Super it is IMO already overclocked in the factory by way of it’s high boost and memory clocks. However I agree that MSFS should be able to handle it so I think it’s mostly a driver issue.
Had this error three flights in a row.
Rolled back to the previous driver (517.48) and just completed a flight with no issues at all.
Before getting back to 517.48 for some, when SU10 launched, some also got back to the driver before 517.48, & the one before. LOL.
it indeed can be driver situation, but not necessary from the driver side, maybe from the sim side dealing with the driver. & the cause maybe not due to a programming error, as some sort of conflicts between well programmed sectors can be a good probability too.
having that said, it’s also good to say that trying to connect unconnected things in aim to connect things will result in unconnected things in the end. LOL.
1 Like
I might agree but no matter how many the amount of individual complaints on here are tiny compared to the current userbase. Some hardware/driver conflicts should be expected for every SU and every new driver.
1 Like