4 minutes ago, F737MAX said:

This is a Nvidia problem. I had multiple CTDs after SU12 was released where the error was due to this.

Updating the driver with a Nvidia 'clean install' didn't fix it, so I cheated and used a download site to find the latest version of the file. No issues since.

The safer way is to perform a DDU or CCleaner removal of the driver, restart, then perform a fresh driver install.

That's what I guess. As a first attempt, I downgraded with a clean install to an earlier driver (531.18) which I knew was safe. No issue anymore, but too early for final judgement.

Kind regards, Michael

Oh, even something I forgot to mention.

USB power settings. I am sure this has been discussed but after months of dealing with CTD's that were my own fault with addons or traffic....I found that my USB power settings changed as well. This was causing recent CTD's a few weeks back. Apparently, a windows update changed a lot of my settings and allowed some of my peripherals to power off or idle when not in use. I didn't realize it at the time but when I tried to change the altitude with my Honeycomb Bravo, I'd get a CTD. When my crummy bluetooth headpones cut out, I got a CTD. This happened a few times. When my toddler decided to unplug everything from my computer mid-flight of course nothing happened.

TLDR: make sure your USB power settings in the Device Manager NEVER turn off while the computer is runny.

9 hours ago, pmb said:

That's what I guess. As a first attempt, I downgraded with a clean install to an earlier driver (531.18) which I knew was safe. No issue anymore, but too early for final judgement.

Kind regards, Michael

I wish changing drivers was the solution, but it isn't. The device manager "error" CTD happens with the latest driver installed (531.41) as well as earlier ones. As said repeatedly on this forum, this is an SU12-caused issue.

38 minutes ago, cobalt said:

I wish changing drivers was the solution, but it isn't. The device manager "error" CTD happens with the latest driver installed (531.41) as well as earlier ones. As said repeatedly on this forum, this is an SU12-caused issue.

I was in SU12 from the first beta and never had a CTD, only since a few days ago, when I installed the latest (two) drivers in a row. Of course, something might have crept in upon SU12 release, who knows.

I still lean towards a driver issue, though, or something combined, but I'll reserve any definite statements until I (or someone else) really isolated the issue.

Kind regards, Michael

In many years of flight simming, if I had a driver that worked, I didn't try to fix it by installing the latest driver. The result, I have never had a driver issue. 

Edited April 6, 20233 yr by Bobsk8

Based on what I've read in this forum (in at least two threads), it seems that the "graphics error" CTD problem was experienced by some folks prior to SU12, but this must have been relatively rare. I never heard of it being mentioned before SU12, and it was only after this update that I along with many others suddenly started seeing it. Clearly, even if the problem existed earlier for some, it is only since SU12 appeared that it has become a large-scale issue. For me at least, I can rule out drivers and add-ons as a factor here. Something in SU12 needs correcting.