New MSFS error in graphics

[DAD 2,667]

1 minute ago, orchestra_nl said:

I quickly reverted back to my old drivers

which one do you use now? Did you revert via DDU?

[altenae 171]

The Asobo story is not correct at all. 

Neither memory RAM or VRAM is the iissue. 

It just started. 

Just like other friends of my who had this message for the first time at almost the same time as I had. 

This is very coincidental!!!!

This is also another Asobo issue 

 

I also read reverting back drivers. Well I think that is also nonsense.  With the current driver it worked for months and all of a sudden it is a problem??? 

And other friends with different driver version had this error to yesterday around the same time!

Figure it out and stop changing everything on your computer when this is also actually an Asobo issue 

 

Edited March 31, 2023 by altenae

[DAD 2,667]

2 hours ago, phmcr said:

I went back to 531.29 and all is fine.

ok, will try that one again, too. did not have any issues with it before

[phmcr 95]

34 minutes ago, DAD said:

ok, will try that one again, too. did not have any issues with it before

I made three identical flights. Two with 531.41 that crashed at just about the same location with said error message. And one after I reinstalled 531.29 without a problem. So to me the problem is the driver. I guess 531.41 does overheat the card but obviously not all cards suffer from it. I have an RX3070 which I would expect to be able to handle it.

Edited March 31, 2023 by phmcr

[altenae 171]

1 minute ago, phmcr said:

I made three identical flights. Two with 531.41 that crashed at just about the same location with said error message. And one after I reinstalled 531.29 without a problem. So to me the problem is the driver. I guess it does overheat the card but obviously not all cards suffer from it. I have an RX3070 which I would expect to be able to handle it.

Then you are lucky with this flight. 

4 online friends got the error at almost the same time all different drivers etc!!

This can never be an issue on its own.  Never!!!

Temp gpu 50 degrees. 

 

[bobcat999 8,536]

7 minutes ago, phmcr said:

I made three similar flights. Two with 531.41 that crashed at just about the same location with said error message. And one after I reinstalled 531.29 without a problem. So to me the problem is the driver. I guess it does overheat the card but obviously not all cards suffer from it. I have an RX3070 which I would expect to be able to handle it.

It does not overheat the card Menno.  This is just a bug for Asobo or Nvidia to sort out. 

I have had the error message with various drivers, and after monitoring my CPU and GPU temperatures with the 'Core Temp' program, there was nothing out of place.
On the last two crashes, the GPU was showing a temperature of around 68 C, which is nothing out of the ordinary.  I run DLSS now so this lowers the load on the card substantially.

This started for me during the Anniversary update beta, last Autumn.

They really need to jump on this bug, alongside the texture popping, and the broken water exclude bug.  Maybe they are working on them all, who knows?  And that is the problem - who knows?  Feedback and communication would be good, other than just the usual weekly update full of pretty screenshots and the marketplace activity.

Edited March 31, 2023 by bobcat999

[KL Oo 708]

I get this message maybe once in every 15 or so flights. It occurs in the most benign of circumstances, like loading up the 172 at my local airport. It has nothing to do with graphics card being overclocked (mine isn't) or running hot (I track the GPU temp and on my water cooled loop it never gets over 55c). Its got to be some sort of MSFS issue. 

[DAD 2,667]

1 hour ago, DAD said:

ok, will try that one again, too. did not have any issues with it before

reverted back and just doing the very same flight again NZQN NZWN in the FBW, will see what happens...

[DAD 2,667]

So far all fine, landing shortly in NZWN

In the meantime also MS answered my zendesk ticket which I opened some hour ago (fast, thanks for that!):

Thank you for contacting Microsoft Flight Simulator Support today.
 
Nvidia has reported that they are having some issues with the latest drivers when it comes to MSFS. We recommend going back to older driver until Nvidia releases new driver update. 
 
Kind regards,
Microsoft Flight Simulator Support Team

 

[altenae 171]

1 minute ago, DAD said:

So far all fine, landing shortly in NZWN

In the meantime also MS answered my zendesk ticket which I opened some hour ago (fast, thanks for that!):

Thank you for contacting Microsoft Flight Simulator Support today.
 
Nvidia has reported that they are having some issues with the latest drivers when it comes to MSFS. We recommend going back to older driver until Nvidia releases new driver update. 
 
Kind regards,
Microsoft Flight Simulator Support Team

 

Well I was already on the older drivers.
I hope not more issues are coming soon.
Otherwise the "uninsall" option will be the solution for me

[DAD 2,667]

12 minutes ago, altenae said:

Well I was already on the older drivers.
I hope not more issues are coming soon.
Otherwise the "uninsall" option will be the solution for me

worked fine here, just landed successfully at NZWN. So I will stick with the 531.29 for a while now

[iliasr 41]

its a driver issue , tested again and got the same message , fixed  with 531.29 driver

[orchestra_nl 973]

2 hours ago, DAD said:

which one do you use now? Did you revert via DDU?

 531.29, which seems to be a popular version by lots of others as well.

[altenae 171]

54 minutes ago, iliasr said:

its a driver issue , tested again and got the same message , fixed  with 531.29 driver

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

Edited March 31, 2023 by altenae

[Noel 4,572]

Been happening here very rarely and randomly for a few months now...