9 hours ago, hhbrbg said:

I assume the CTD happens when the windows power save function kicks in.

Interesting idea. I may turn off power saving and see if monitor-off CTDs continue or not. They are not all that frequent so it will be hard to be absolutely xertain.

 

Just had another CTD whilst moving AVI files from memory card to HDD (not one MSFS uses at all).😶

1 hour ago, 109Sqn said:

Just had another CTD

Can I ask you to check something, right click on the Sound and see if your spatial is ticked off

22 hours ago, FPStewy said:

Can I ask you to check something, right click on the Sound and see if your spatial is ticked off

It is ticked off, yes. Do you think there's a connection there?

4 hours ago, 109Sqn said:

It is ticked off, yes. Do you think there's a connection there?

I use to experience hard locks and CTD's with spatial on but not since I've left it unselected. In six months I think I had one CTD.

On 1/29/2021 at 10:14 AM, 109Sqn said:

Are the more recent AMD drivers less stable in MSFS?

The last couple of updates seem to be for me, especially on long flights 4/5 hours or more). My GPU is regularly running at 100% according to Xbox Game Bar, not a problem in itself until recently. But I now get CTDs with a 'driver timeout'. I'm wondering now if I should roll back 2 or 3 driver releases to see if that fixes things. Has anyone had similar problems with the AMD Adrenaline drivers lately? And what is your solution, if any? Buying a different GPU is not an option!

I just updated a new PC AMD latest driver today. Next three flights, CTD, and the last one gave me a driver timeout warning. I just rolled back to the previous driver that came with the PC that is just over a week old. I used to avoid updating to latest driver like the plague, for decades, but I figured a brand new PC, what could go wrong  .  LOL

I was going to install the August/Sep driver on MY new PC, but it doesn't say it supports my card (I ordered a RX 6800 in my new PC) - afraid to try a driver that doesn't list that it supports my card at all?

In any case, despite the occasional driver timeout CTD I'm STILL sort of glad I went with the AMD card vs. Nvidia as in P3D and XP11 have both used 10.8GB of VRAM on my (non-4K) settings at times - it's very nice to have that 16GB of VRAM without spending a fortune for 24GB (but I do hope AMD fixes the driver issue - incidentally I had the driver timeout on me when running P3Dv5.1 also.

Steve

I am no longer using the September driver and I am using the current one with no problems, so far!! 😅

I downloaded the latest driver last night and yet was still having a CTD! Has anyone found a viable solution yet?? Is there a particular driver which stops this from happening? 

1 hour ago, Seatbose80 said:

I downloaded the latest driver last night and yet was still having a CTD! Has anyone found a viable solution yet?? Is there a particular driver which stops this from happening? 

I had ben running the latest version for a few days, but then without any changes to the system the dreaded Driver time out yet again !  I am now back to the only version that gave any form decent flight time without a CTD which is by rolling back to 20.8.3

Now trying to find the culprit for the secongd issue which rears  it's ugly head Vcc Runtime dll which occurs now and again. Currently working through all the advice from the MSFS forum.

One thing i have learnt from the whole fiasco.... AMD can stick their 6800 and 6900 cards where the sun don't shine.... i'll never buy another card of theirs... absolutely no back up!

36 minutes ago, Car147 said:

I had ben running the latest version for a few days, but then without any changes to the system the dreaded Driver time out yet again !  I am now back to the only version that gave any form decent flight time without a CTD which is by rolling back to 20.8.3

Now trying to find the culprit for the secongd issue which rears  it's ugly head Vcc Runtime dll which occurs now and again. Currently working through all the advice from the MSFS forum.

One thing i have learnt from the whole fiasco.... AMD can stick their 6800 and 6900 cards where the sun don't shine.... i'll never buy another card of theirs... absolutely no back up!

Have you noticed any FPS drops using that driver at all as compared to the latest one? I'm worried about getting much less performance when rolling back to previous drivers.

1 hour ago, Seatbose80 said:

Have you noticed any FPS drops using that driver at all as compared to the latest one? I'm worried about getting much less performance when rolling back to previous drivers.

No, not so far, and just completed a 3hr flight with no issues using the above driver version. I also did a couple of changes that hopefully cure the Vcc Runtime dll issues.

1 Was to run MSFS from the Xbox APP and not the normal launch.

2 And only do this if you are confident in changing Bios settings. Some think it could be down to the new Pcie Gen 4, and to try dropping down to Gen 3.which may loose you a couple of fps

3 I ran a Scannow in command promp to check there were no corrupted files in the Vcc Redistributables all checked out Ok

So back to flying and seeing if any issues re-occur

 

5 hours ago, Seatbose80 said:

Is there a particular driver which stops this from happening? 

Like @Car147, I'm back to using 20.8.3. CTDs haven't been entirely eliminated, but they are noticeably reduced. I had another overnight. For me, it still seems restricted almost entirely to long flights (3 hours plus and mostly8 hours plus). I switched off all power saving apart from still allowing hard disks to turn off after 20 minutes as is standard on High Performance settings. But I still had a CTD after 3 1/2 hours last night. I was asleep so I don't know if it was a driver timeout (no Radeon pop-up when I switched the monitor on).

Got another driver timeout crash on starting MSfs 2020, after I rolled back driver to original version.?????

Still not sure it's correct to blame this on AMD.  I've never had an issue with my card in any other game or sim, and the event logs show MSFS crashing before the Radeon Software. 

Asobo has done a very poor job of dealing with CTDs, it's one of the top bug/wishlist items and they never talk about it in the Dev Q&As, they just pretend it doesn't exist.  

Scrap the changes i tried earlier in the thread to overcome the Runtime dll issue, failed again during a leisurely flight along the coast of NW Spain, BAm ! Ctd, Vcc runtime dll... grrrrr