"graphics error" CTD's and the latest update

[cobalt 774]

OK, with today's mandatory update we appear to have entered a new phase, which has not solved the problem but may possibly move toward a solution. I am one of those MSFS users who never encountered the "graphics error" followed by a CTD, until SU12 came along, and since then they have been constant. I and others have concluded that it is NOT a graphics driver problem: old drivers, latest drivers, it makes no difference. (I am using DX11). Today's update changes the wording in the graphics error to provide some new information -- it says "you are using an unsupported driver (531.29). Please update your graphics driver using a version greater than 535.79".  Well, I installed 535.98 (I believe the latest available) and the same old thing happens, i.e., the graphics error and a hangup. They provide a link to zendesk which I have not yet tried, but I am more convinced than ever that this will be solved only by Asobo correcting whatever was done in SU12 that caused the problem in the first place. Hope springs eternal ...

Edited June 23 by cobalt
clarification

[NismoRR 190]

I’m on an older driver version (517. xx) and got the message to update and continued the flight. The only anomaly I noticed was the outer square portion of the PFD showed a white, thickish line around the border depending on the angle it was being viewed at with TrackIR. This was the 737-900. Otherwise, all looked ok. I’ll update tomorrow. Just downloaded 536.xx to update. 

[somiller 694]

On 6/22/2023 at 9:46 PM, NismoRR said:

I’m on an older driver version (517. xx) and got the message to update and continued the flight. The only anomaly I noticed was the outer square portion of the PFD showed a white, thickish line around the border depending on the angle it was being viewed at with TrackIR. This was the 737-900. Otherwise, all looked ok. I’ll update tomorrow. Just downloaded 536.xx to update. 

You may want to review the AAU2 update thread as it appears the avionics display white border has unfortunately been gifted to some that never experienced it before (not happened to me...yet), and it's unrelated to graphics driver.

EDIT: the white border on the PFD and MFD now affects my system

[Sky_Pilot071 557]

Check your graphics settings.  Mine all reverted to default.

sp

[Adamski_NZ 867]

I'm also getting the deaded white boxes - albeit intermittently. Epic fail.

Since this "update" I'm also getting much more stuttering and my ATR72-600 PFDs freeze (permanently) if the sim is paused for any length of time. Grrrrrr ....

[cobalt 774]

Sorry to say, things are worse following this week's update. I now get the so-called "graphics error" message and CTD even on startup, if I fail to click on the world map within a few seconds! Setting my graphics to a lower quality makes no difference, nor does loading in safe mode (or changing drivers). Flights, if they can be started, last at most a few minutes before the CTD happens, with no warning. To repeat, none of this happened before SU12. I have run out of ideas and can only wait for SU13. 

Edited June 24 by cobalt

[Sky_Pilot071 557]

Make sure the latest nVidia driver is installed.  No CTDS here since the update but I don't fly the affected planes or have them installed.

sp

[cobalt 774]

Latest Nvidia driver makes no difference, at least for me. Still get "graphics error" followed by CTD. Also, as far as I can tell the choice of plane makes no difference either. To repeat, no problems whatsoever prior to SU12.

Alienware Aurora R11, 32 GB ram, Intel i7-10700F, GeForce RTX 2080 Super, Ultra graphics settings

Edited June 25 by cobalt

[1st fltsimguy 465]

I did the update, got the same error, went to get the latest drivers for my GTX1080Ti.  Went for a flight out of Calgary...everything seems to be working.  More testing required and for a longer duration, but all seems OK.

 

[marangog 6]

I also got that message about updating my GPU driver to 535.79.0 or better.  I continued to load the game and flew for a couple of minutes before CTD. I updated the driver to the latest (536.23 for my RTX 2070 super) but the relaunch crashed after only a few seconds (the black screen before the splash screens start). I tried to get help from Steam but got fobbed off. I followed the cleanup process to get a plain vanilla version, but the graphics just won't kick in.  No problems with other Steam games or anything else on my PC.

It's very annoying. I have 1400 hours flying in this game and now am locked out. I have used Stem diagnostics to check the integrity of my installed files. Do you think reinstalling would help?

[Reader 1,889]

2 minutes ago, marangog said:

Do you think reinstalling would help?

Highly unlikely, the same files that seem to have introduced this error will be replaced.

[JiBrady 20]

I have the latest driver and see the following:

1) Whitw lines aroung the PFD (sometimes)

2) CTD whenever i select DX12.

So I just use DX11 and put up with the sometimes seen white outline.

Jim Brady

[marangog 6]

Just sharing my delight in getting MSFS to work again. I installed a slightly earlier driver (535.98) but that didn't make a difference. Then I stumbled on a file called RUNNER.LOCK dated 19.6.23 (when I crashed). I don't know how I didn't see it earlier. I disabled it,  and BINGO! the splash screen appeared and Mandatory Update 1.33.8.0 popped up. The update began as about 134Mb I think, but quickly ballooned to 104 Gb - reinstalling all the Official Packages folder that I had disabled in order to get a plain vanilla version. Everything is more or less back to normal now, happily.

I believe that the runner.lock file was the sole cause of my failure to launch and that there was no need to follow Asobo's "plain vanilla" advice. Please correct me if you know I am wrong. 

I wish that the use of a lock file was more public knowledge, either in Asobo's FAQs or perhaps as a forum sticky. Maybe it is, and if so I'd be grateful if someone here can show me where and how to look for that sort of thing.

[fppilot 4,256]

5 minutes ago, marangog said:

Then I stumbled on a file called RUNNER.LOCK dated 19.6.23 (when I crashed).

Please mention where on your system you found it located.

 

[newtie 463]

And what it does :>)