There's a common "fix" for many issues regarding the RX 5600 XT/RX 5700 XT and some others that have crash, black screen, game issues, etc. that relate to certain driver packages. There's a whole other part to it that concerns setting the 3 clocks to within 100Mhz of each other toward the max clock(~1700,1800,1900-1950Mhz), undervolting the GPU (~960-1.050mv), setting the power limit to max, adjusting VRAM +12Mhz, turning off the zero RPM fan function to lower initial temps and lastly a possible a more aggressive fan curve.
I posted it back in October or so and since then a few others did as well. Basically trial and error found the driver's that weren't stable and we that OC found the clock issue causing some crashes due to the rapid frequency and voltage swing the cards do during operation. When browsing one might not notice a problem but gaming is a different story since some scenes might lower the GPU clock as though it's a regular video than ramp up quickly as action starts, causing problems. That's the "back story" to that.
As far as the driver download goes, yes download it to wherever you want to save it first. Install DDU, but before you reboot to safe mode, disconnect the internet so no drivers get installed automatically but the basic display driver Windows uses by default after DDU runs. While still disconnected, install the older driver and remain offline. Once the reboot is done, go into the Radeon settings and disable the automatic driver update feature. This will prevent the software from automatically installing newer drivers until you read the "release notes" and determine if there's anything new or a fix for something that affects you. With the 5000 series, there shouldn't be since AMD is done with "fixing" those drivers with the newer 6000 series cards being pushed out.
Sort of a bad thing for AMD to make the 5000 series EOL like this since they weren't out long and there's still plenty using or buying them. In rare cases they might come out with a fix for a certain game but I don't see it happening for the 5000 series.
To check what is crashing, look in "Event Viewer", "System" or "Application" list for the error code and reason. It might not line up exactly to the minute of the failure, usually it's a few errors slightly before the CTD.
Steam is simply the "launcher" for the game, it's "back bone" is Microsoft based, usually off the "Store". You can repair the "Store" in "settings"/"apps", find the "Microsoft Store", right click it, "advanced properties", "reset". To update it just open the "Microsoft Store" app and click the 3 dots at the upper right and choose "downloads and updates", if there are any it will list them there including the store app. If it doesn't work or asks you to sign in, then follow the instructions to reset the store above.
FYI, you can also have Steam be the default "launcher" for nearly any game, like EA based, Epic, etc. It will invoke the proper client like for EA=Origin and I don't bother because then you're running 2 launcher's, waste of resources but "convenient".
"It worked before you broke it!"
