New MSFS error in graphics

[iliasr 41]

2 hours ago, altenae said:

4 online friends got the same error around the SAME time with all different version drivers. (also some had 531.29).
So think how can this be …
All had the error on the same time.
You really think this is a driver issue when all 4 online players have all different driver versions and encountered the same issue at the same time

reverted with DDU on 531.29 and working as before , maybe you are right , I didn't know this issue happens on 531.29 version ...will see

[wim123 769]

2 hours ago, altenae said:

4 online friends got the same error around the SAME time with all different version drivers. (also some had 531.29).
So think how can this be …
All had the error on the same time.
You really think this is a driver issue when all 4 online players have all different driver versions and encountered the same issue at the same time

and did they all do a clean install, important !!! leftovers of drivers can cause problems too.

but there has been too many issues with nvidia drivers lately

[TacomaSailor 196]

This NOT a new problem - I was getting the error fairly consistently in early fall 2022.  Temps were always low, VRAM and system memory usage was low.   Tried DX11 / DX12 / several different drivers.  Nothing fixed it - just kept happening.  Sometimes frequently sometimes only once every couple days. 

The problem persisted for several weeks and then stopped occurring and has never reoccurred.  I did nothing to try to resolve it. 

Edited March 31, 2023 by TacomaSailor

[WestAir 2,533]

Just had this error for the first time. Super frustrating, because I get the free time to play MSFS once every month or so. We'll see if it happens again in May... 😒

High end system, no overclocking. It's lying about running out of memory.

[40track 80]

Deleted.

Edited April 1, 2023 by 40track
Doesn't work.

[Christopher Low 5,523]

20 hours ago, wim123 said:

and did they all do a clean install, important !!! leftovers of drivers can cause problems too.

but there has been too many issues with nvidia drivers lately

I think he means that some of his friends were already using the 531.29 drivers, and had not installed the new ones.

[wim123 769]

1 hour ago, Christopher Low said:

I think he means that some of his friends were already using the 531.29 drivers, and had not installed the new ones.

i got that yes...still could be leftover stuff, but it seems it is something very random, not everyone has got it.

[WestAir 2,533]

10 hours ago, WestAir said:

Just had this error for the first time. Super frustrating, because I get the free time to play MSFS once every month or so. We'll see if it happens again in May... 😒

High end system, no overclocking. It's lying about running out of memory.

I took a personal day from work today and tried again.

This time I rolled back to 531.29. Then I upped my graphics settings to Ultra everything, 4K. As high as the bars let me go.

Flew the same flight / route as before, except made it to my destination without any issues. I'm going to take a shot in the dark and say the latest NVidia Driver is the cause of this crash.

[altenae 172]

19 minutes ago, WestAir said:

I took a personal day from work today and tried again.

This time I rolled back to 531.29. Then I upped my graphics settings to Ultra everything, 4K. As high as the bars let me go.

Flew the same flight / route as before, except made it to my destination without any issues. I'm going to take a shot in the dark and say the latest NVidia Driver is the cause of this crash.

Look at he date when this issue started !!

https://forums.flightsimulator.com/t/warning-your-graphics-device-has-encountered-a-problem/541301/2573

Before 531.xx was there.
I had the error with 531.29 so ?? How can that be ?
It's not only an issue with the lastes Nvidia Drivers.

Edited April 1, 2023 by altenae

[WestAir 2,533]

1 hour ago, altenae said:

Look at he date when this issue started !!

https://forums.flightsimulator.com/t/warning-your-graphics-device-has-encountered-a-problem/541301/2573

Before 531.xx was there.
I had the error with 531.29 so ?? How can that be ?
It's not only an issue with the lastes Nvidia Drivers.

It could be there is more than one event that can cause this particular CTD, but to an individual user there is almost always only one cause. I mean the number of people who suddenly got this for the first time with this driver, and then could not reproduce after rolling back, is not a minor thing that can be brushed off as coincidence. Though of course I am only guessing and have no evidence to back up my presumption.

I would ask: If anyone who got this for the first time after updating to the latest driver, then gets this again after having rolled back, it would be great if they could post here.

[Jeff Nielsen 1,440]

I just got it yesterday for the first time as well.  Reverted back to the previous driver and no issues.

[DMullert 220]

I never had this issue until yesterday when it happened twice.  I also had upgraded to the latest driver, but oddly enough..........it happened while I was taking off from KDFW, Runway 35L and during takeoff roll I hit some invisible object and CRASH.  I have taken off from this runway countless times since this is my home airport, and never had this issue.  I wonder if it's an Asobo server / scenery loading issue??  My specs are below - I never had an issue until now.

Dennis

[bofhlusr 471]

12 hours ago, WestAir said:

...

I would ask: If anyone who got this for the first time after updating to the latest driver, then gets this again after having rolled back, it would be great if they could post here.

Old Nvidia driver (version unknown) working for months (maybe even a year) and after the last SU update  ---> error 
Upgraded to version 531.41 ---> error
Downgraded to version 528.49 ---> worked a couple of times and now getting the same graphics related error again

Result: CTD before MSFS completely loads and MSFS is now unavailable to me.  A re-install may not be an option if it automatically updates and if the update is what is causing the error.  P3D and DCS flightsims working fine.

Edited April 2, 2023 by bofhlusr

[Rocky_53 1,637]

On 3/31/2023 at 4:30 AM, polosim said:

Remove addons that could be causing this error

I've never heard this one before! 

[Reader 2,049]

14 minutes ago, Rockliffe said:

I've never heard this one before! 

Every day, there is something new to be learned.
There are three pages of guesses, so far.
The reason for this is clearly that no one knows the answer and as well as that,
it is highly likely that there is not one answer, but several.
The easiest trap to fall into is to make the assumption that the last thing that was done must be the cause of a problem.

The quickest way to rule out all Community addons is to rename the Community folder and restart MSFS.
The quickest way to rule out a driver is to "roll back" to the version that was there before.
Ruling out Marketplace addons is a far more lengthy process that is probably not necessary in any case.
Then there is the vast array of hardware combinations and the even more vast array of possible user-induced errors to be considered.