Also using this driver version helped me…
What did you put in the graphics settings on the radeon software ?
I use the default settings. I average about 32FPS except places like LAX (22FPS) like everyone else.
.
Most of my setting on MSFS are Ultra and 100 LOD at 1440.
1 Like
I want to remind people that nothing indicates the AMD drivers are the direct cause.
9 out of 10 CTDs I have are caused by a null pointer exception in MSFS - more specifically, in their Renoir library (provided by a 3rd party).
I had very few cases directly cause by the Radeon software directly.
My developer’s instinct tell me this issue could be caused by a threading synchronization issue. This kind of error, often hard to pinpoint, tend to have variable occurrence attributes depending on factors like the amount of cores or the processor speed.
Hear me well, I’m not saying AMD has no responsibility here. I’m saying the crash is in MSFS and this is where it should be fixed. Weather or not AMD drivers contribute to the issue is a far more complicated thing to prove.
BTW, my system never crashed on anything else - including finishing Half-Life:Alyx (VR) 3 times at very high frame rates and resolution.
** ADDENDUM **
One more thing…
There is an external MSFS component named “SpeechRuntime” that keeps crashing, at least once every 3 days on my system. Luckily, it causes no visible issues.
The point here is that nobody’s talking about it because it has no major negative effects on the game.
The component crashes because of a unhandled exception in the handling of a speech grammar or in the disposal its process.
This is preventable with proper coding. It hasn’t been done. Neither fixed yet.
This being said, don’t be surprised to see code weaknesses elsewhere.
3 Likes
Updated to 21.5.1. I’ve been in cruise for about 1.5hrs+ Not overclocking ATM and FPS is good on my 5700XT between 60 and 70FPS at high to ultra settings. So far so good…The flight it about 3.5 hours so I’ll let you know the result.
EDIT Literally right after posting this I decided to descend below a cloud layer and my system froze. Don’t waste your time… Not fixed
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6087d3ea
Faulting module name: VCRUNTIME140.dll, version: 14.28.29231.0, time stamp: 0x5f4c66c9
Exception code: 0xc0000005
Fault offset: 0x00000000000014b4
Faulting process id: 0xa7c
Faulting application start time: 0x01d7435987904105
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.15.10.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: 440cbf0a-7fda-438d-a8a4-2995bca8063a
Faulting package full name: Microsoft.FlightSimulator_1.15.10.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Faulting application name: GameBar.exe, version: 5.621.4222.0, time stamp: 0x60818071
Faulting module name: KERNELBASE.dll, version: 10.0.19041.964, time stamp: 0x812662a7
Exception code: 0xc0000409
Fault offset: 0x000000000010b39c
Faulting process id: 0x2cc8
Faulting application start time: 0x01d7435a8303585b
Faulting application path: C:\Program Files\WindowsApps\Microsoft.XboxGamingOverlay_5.621.4222.0_x64__8wekyb3d8bbwe\GameBar.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 15048a0f-24b9-4035-9f1d-ba93a578f9a0
Faulting package full name: Microsoft.XboxGamingOverlay_5.621.4222.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
1 Like
I see nothing in that bug report that has anything to do with the GPU drivers. I really think MSFS is buggier than AMD’s drivers.
Thank you for being this release’s guinea pig! You saved me at least a few hours!!!
No problem. I’m in the process of rolling back now. Something between MSFS and the newer drivers do not like each other. Every other game seems stable with newer drivers and I get improved frame rate with the new releases as well. Maybe next time …
If they work for every other game what makes you think the drivers are the problem? Just because the problem started after installing the driver?
I don’t think I said the drivers were the problem. Only that the newer versions cause MSFS to crash. Could be either for all I know.
Yes i understand but how do you know this driver version causes MSFS to crash and not something else like the last MSFS updates or Windows update or some addon or aircraft type?
It doesn’t seem te reliably crash after a set amount of time so it’s hard to consider this issue fixed when it can crash after 1, 2 3 or 4 hours.
This has been discussed a zillion times on here if you do a search. All I know is the newer drivers AND MSFS2020 are incompatible for some reason for many RT5700XT owners and seems many RT6800XT owners too.
2 Likes
Yes but a lot of nvidia users have CTDs too and a lot of AMD users have no CTDs.
I did your search but no proof anywhere.
Because it is a reproducible crash that only occurs past driver v20.10.1. Like clockwork. If I run an old driver it works fine for hours and hours of flight. If I run a newer version it crashes in a random amount of time… Typically less than 2 hours.
Why do you even care if it’s not affecting you?
less than 2 hours is not clockwork. There are many CTD issues in MSFS, how do you know which one you are having without log file?
Dude why are you arguing with me? I don’t care. Listen I can fly MSFS flawlessly with older drivers for MANY MANY HOURS without CTD. New drivers always crash predictably!
2 Likes
I’m not arguing, don’t get angry haha. I am asking what method you use to determine what the problem is without log file. I am having CTDs myself and i am trying to figure out what the problem is.
The sim crashes after some hours sometimes, so it’s very hard to test over and over, it will take me weeks to come to a conclusion.
It’s definitely been a common thing since last year. I remember updating beyond 20.10.1 and all of a sudden the sim wasn’t usable for any length of time. So when I finally saw the discussions on the forum I decided to roll back and issue gone. Cross our fingers that the submitted bug reports to both Asobo and AMD get noticed and addressed one of these days.
The MSFS crash is a null pointer exception. I don’t have my dumps at the moment but, from memory, the offset matches the memcpy fault in VCRUNTIME. This is the typical crash caused by the Renoir library - the Path::Create method, the 90% of my CTDs. This exception is manageable with proper code. Nothing directly attributable to AMD here.
For the second one, it’s your Windows Game Bar. If I remember well, this exception code is a stack overflow. This exception is harder to handle. Nothing directly pointing to AMD here neither.
1 Like
I saw a video last night that recommended taking the AMD driver out of game mode and selecting Normal instead. Haven’t had a driver timeout since.
I’ve been without CTD since the moment I kept my 21.3.2 driver for my RX5700XT Nitro +. But what improved a lot was to put DRIVE C: (where the windows is installed and only it ) “WITHOUT VIRTUAL MEMORY PAGE”. The windows got much faster if without problems to manage MSFS. It may be a placedo effect, but for me it worked perfectly and the CTDS are gone …
Tip: This is the way in windows:
- 1st. Right-click on the start menu;
- 2nd. Select “System” and in the right side menu of windows select “ADVANCED SYSTEM SETTINGS”; (you can try to search for win only on this and go straight to it.
- 3rd. The system properties box will open;
- 4th. Select the “ADVANCED” tab;
- 5º In the “PERFORMANCE” menu, click on the “CONFIGURATIONS” box;
- 6th. Another box called “PERFORMANCE OPTIONS” will open;
- 7th. Again select the “ADVANCED” tab in this box;
- 8th. In the “VIRTUAL MEMORY” menu, select the change box;
- 9th. He had opened a new and last box;
- 10th. Remove the Flag from the option "automatically manage the size of the paging file;
- 11th. In the box below * just * select the Drive where your WINDOWS system is installed;
- 12th. Check the balls below “WITHOUT PAGINATION FILE” and click on DEFINE;
Then just click ok and leaving the boxes click OK too.
Restart and machine and test!
This helps to make the WIN faster and MSFS is no longer failing due to system events. I believe that just like it happened to me. It has greatly improved the experience of not obtaining any more CTD.
I hope it helps! 