reading about all the people suffering with NVidia drivers currently it seems like both sides are suffering some issues there.
Anyways, for the 5700XT; yep, the october driver seems to be most reliable. Newer versions mostly bring optimizations for the 6000 series, and in all the patch notes of later versions there hasn’t been a single mention of MSFS. So if you’re not having issues, stick with the most stable version of the drivers (as seems to be the case for NVidia drivers as well).
I’ve been having this problem for months, and I’ve been trying every suggestion I find in these forums, thinking it is related to my Radeon RX 5700 XT graphics drivers because of the Radeon message that appears on the screen after FS crashes. However, when checking the event viewer, it isn’t actually the graphics driver causing these crashes. The event for FS crashes references “Faulting module path: C:\Windows\SYSTEM32\VCRUNTIME140.dll”.
I found another discussion of these crashes in this forum that focuses on this error, instead of the graphics drivers, and there’s suggestion that this event and these problems are related to the cloud data in the game. I’ve followed suggestions to limit the data bandwidth from unlimited to 40Mb/s and I’ve disabled the Azure text to speech and use local Windows text to speech. I’ve also disabled live traffic and weather. When I played for almost an hour yesterday in various locations, I didn’t have any crashes. I decided to re-enable Azure text to speech while in the middle of a flight, and within a minute or two of doing that the game crashed to desktop. I restarted the game and disabled Azure text to speech again and loaded the same flight plan and started flying again, with no crashes again.
Has anyone else following this topic tried this yet? I’m curious if it is just me observing this or if others may have.
I think you might be on to something. I have a newer drivers and not had any issues with 5700xt but not doing anything long at all just a few 1 hour hope here and their. I did a long time ago turn of some of the settings you were talking about. I think is sometimes comes back to NAT and data traffic between the Computer and Azure servers. Check the event logs are always a great help.
I’ve been flip flopping between v20.9.2 and 21.3.2 with little to no success. I’ll try your suggestions about bandwidth etc and see what happens.
EDIT: So I got a crash almost instantly. But I was using live weather.
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x607064d1
Faulting module name: VCRUNTIME140.dll, version: 14.28.29231.0, time stamp: 0x5f4c66c9
Exception code: 0xc0000005
Fault offset: 0x00000000000014b4
Faulting process id: 0x3c68
Faulting application start time: 0x01d7321320e45a74
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.15.7.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.29231.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll
Report Id: 245a187d-f631-4797-a3b3-8ace91f849b0
Faulting package full name: Microsoft.FlightSimulator_1.15.7.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Now trying REX Weatherforce to see if there is any CTD. If it does I will run another test with clear sky.
I’ve had that disabled for months. That helped - but did not entirely solve - the CTD events.
I’ve pretty much accepted that I should just set the game aside and wait until Microsoft fixes it. I’m tired of trying to figure out how to fix it myself, and I’m in IT because I love to fix these types of things. With the amount of time that I and everyone in these forums has spent trying to fix this, it seem like a problem that users can’t fix and shouldn’t have to fix.
Maybe by the the time it gets fixed I’ll be able to find a Radeon RX 6800 XT to replace my RX 5700 XT so I can also increase the quality in my Reverb G2, because when the game isn’t crashing, the VR as so much fun and something I couldn’t have dreamed of doing when I was a kid playing FS 98.
I use the latest driver and I have no CTD problems. I increased the virtual memory and everything is going well. For now the perception was only about the performance that is very low after the WU4. The average FPS before was 40 and now drops below 32. With the same configuration sets.
R5 3600x RX 5700XT Nitro+ 16G 3000Mhz on 4k downscale 80% (3072x1828)
I’m using a WQHL driver from 16 September 2020 - version 20.9.1
You can also try 20.10.1 - I’ve heard that driver is quite stable too.
I have tried various versions of the drivers, but I try to avoid any older than December 2020 because I also play Cyberpunk 2077, and any drivers released before then cause CP 2077 to crash regularly.
I’d been trying every suggestions I find in these forums and other tips on the internet as well, but CTDs were still there until I got down to its science with the following settings, and I haven’t had a single CTD since. Knock on wood 
So, instead of adjusting one setting at a time, I combined everything together and flew from KJFK to EIDW for 7 hours without a hiccup; hopefully, these settings would help someone. Thanks to all in the forums.
Bios Settings (Asus Crosshair VIII Hero WiFi)
XMP enabled
Core Performance Boost ENABLE
PCIe x16 GEN 3 on all of them
3 Gigabyte G32QC 32" Monitors
7680 x 1440 at 120 Hz
Windows 10 (latest update)
Game Mode OFF
XBOX Capture DISABLE
Page File MIN 49152 (1.5 x 1024 x 32 RAM) MAX 98304 (3.0 x 1024 x 32 RAM)
Asus ROG Strixx 5700XT
Driver v21.3.1
Graphic STANDARD
Performance DEFAULT
Vsync OFF
MSFS 2020 v1.15.7.0
VFR Map OFF
Vsync OFF
Graphic Setting HIGH
Render Scale 80
Terrain Level 125
Objects Level 150
Anisotropic Filtering 16X
Texture Supersampling 4X4
With these settings, I can get around 28 FPS during takeoff and cruising and around 24 FPS during landing and no CTD’s, and I can live with that.
The Terrain and Object LOD being over 100 is killing your fps. The performance hit is way too big for the small amount of fidelity you get with the sliders over 100.
Awesome setup btw
Thank you, DecentAngle. I read somewhere online that says Object LOD does not affect much on CPU and GPU, but i will test it out to see if there is any discrepancy.
I have rt5700xt and i had driver timeout when i play msfs2020, I tried everything since december, then i saw on this forum that i should install octobar driver 20.10.1 . I did that and from that moment i dont have problems! anymore! Thank you so much!
New driver 21.4.1 released! I will test ASAP, although I didn’t have crashes with last driver version.
No mention of MSFS in the release notes again. https://www.amd.com/en/support/kb/release-notes/rn-rad-win-21-4-1
Nice I’ll try this one too after cleaning up the old one via DDU. Not that I expect anything to change but you never know…
This keep baffling me to be honest. MSFS is easily the most complex “game” of its generation, on par with Cyberpunk2077 while everything else is light years apart. Even so I’ve yet to see an AMD driver changelog mentioning anything about MSFS, with the exception perhaps of 20.8.2 which was made available around the time the sim was released and of course doesn’t support 6000 GPUs. I may be missing something but in any case MSFS doesn’t seem to be very high in their list of priorities, perhaps because its fan base is potentially smaller than the other games listed.
If you have 5700 XT and experience a “driver timeout” try this Registry REG. I got this tip from a user by the name of Emerson67 at AVSIM website.
Open a plain text editor, like Microsoft Notepad (Windows accessories->Notepad) or Notepad++.
Copy and paste the following text into the editor:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers]
“TdrDelay”=dword:0000000a
“TdrDdiDelay”=dword:00000019
Save as “vaccine.reg” file, and close the editor.
Double click on “vaccine.reg” file, and then choose “Yes”.
Restart the computer.
Run MSFS.
Give feedback.
“What this tweak does? It increases (5 times) the values of two Windows 10 GPU scheduler timeout parameters.”
UPDATE: I can confirm that this method works well with the new AMD driver Adrenalin 21.4.1 Recommended (WHQL). Been flying for 2 days and not a single CTD
This is probably due to a recent Windows update a few days ago.
I tested the last driver. It really is very good, it gives more performance to MSFS (increase from 2 to 3 FPS). However, as not everything is flowers, there is one annoying thing that I was unable to solve. The screen flashing from full screen to window mode. I tried various situations like refresh rate, color depth and the like. I realized that it is the windows HDR that is causing this. I have already reported to AMD.
For now I’m going to collect for 21.3.2.0
Thanks for sharing this, I have to say it worked in my case, today I let the simulator running all day long without a single “driver timeout” too.
If I don’t reply to this post in the future it will be because I haven’t any issue again.
No Problem. I’m glad it worked out for you too. I haven’t had a single CTD since the reg even with the latest Beta AMD graphic driver. Have a nice flight
