After many months of testing I finally found the problem affecting CTD issue in AMD configurations.
It is related to an USB instability bug in AMD chipset with the old AMD AGESA 1.1.0.0 bios, this explain also why this started for me when i switched from my old Intel i7.
This type of instability is which cause the generic error code 0xc0000005.
For all of you with AMD systems make sure to update your motherboard BIOS to a version which include the AMD AGESA 1.2.0.2 update.
In my case I’m now on bios F33 for the X570 AORUS MASTER.
Tested with a 5 hours non stop fly from Rome to Dubai, and another 1 hour in game main menu.
Runs perfect!
I saw someone talk about it on another topic a few days ago in this 1.2.0.2 update.
But I got so used to living without MSFS that I haven’t tested it yet.
Now, 5 hours is not really a lot (So to speak) I already thought I had THE solution because I had not had a single CTD for 15 hours, on several flights. BUT at 4 p.m., the CTD came back …
But there, I want to believe it
I’m not sure that solved it for me. I had CTD’s with bios F13h on a Gigabyte B550 Aorus Elite V2. That had AGESA 1.2.0.2. Now I’m back on F13g with AGESA 1.2.0.1 A and Gigabyte somehow deleted bios F13h so I can’t (re)install that one now to test. But I’ve had CTD’s pretty often with the later version.
My guess is it is a MSFS problem. They hope the new DX12 and optimized code solves it. I hope that update comes sooner rather than later. And I hope it solves it…
Yeah, I´ve had 1.2.0.2 since I upgraded to a 5600X and have those CTDs as well. I also think that it´s more of a MS/Asobo problem. Hope they do fix it.
1 Like
I know this isnt a PC diagnosing forum. But i have the ASUS ROG Strix B550-E and the bios for AGESA 1.2.0.2 is in Beta, Is that safe or should i just leave it on the current bios until Beta becomes fully released?
Beta BIOS may have some bugs, I waited for mine until it become stable version
One advice, do not use bios in beta versions. There are some people talking about very bad issues related to bios updates, most of them about betas. Just check on internet.
In my case, I only update my bios because I have a low budget x470 gaming plus max and a low mid range r7 3800X. My first bios release was causing issues with my cpu, after a update to new stable version and no more bsod. About msfs, after some time “fighting” with the Sim and amd drivers, I found that my Logitech software for my headset was the cause of my msfs ctd.
Bios updates may help or not depending your mobo, so, it’s better you check all your programs first and see if there is one causing issues.
If you’re savvy enough to update BIOS you quite likely already know this, but just in case…
Don’t forget to check/reset your XMP values after you update to a new BIOS. On my board everything started at default values, which in my case, was XMP disabled.
Cheers!
Just done another long 13 hours flight France to Seattle, no issues at all!
Long flight with the buggy B787, stressed the sim also with the MCDU and glass cockpit stuff, and my internet connection also halted. All worked nice!
The USB issue that makes MSFS crash is related to USB2 (not USB3) devices that get disconnected and reconnected repeatedly for no reason from the point of view of the OS. Most input devices, controllers, USB sound, etc. use USB2. The AGESA 1.2.0.2 update seems to only partially fix the USB2 issues. My pedals used to be gone after some random time mid-flight. That no longer happens. The audio of my HP Reverb G2 headset, however, (which is essentially a USB2 audio controller) still disconnects and reconnects every few seconds, making MSFS crash after some time. Since AMDs USB2 implementation seems to be broken, I got a USB3 controller card. I hooked up my VR headset and all my input devices to the card and had no issues since.