[TL;DR] This problem is a known Windows problem. It happens seemingly at random, hardware swaps are no guarantee.
Adding my two cents here, it's not the 5700xt. I've looked into the issue quite deeply, and hardware configurations of all makes are having this same issue; that being random blue/black/green screen freezes or restarts. The only common component among all reports is Windows, and the problem has been around since at least version 1903. [Plus the odd Win7 complaint]
As some users have already said, changing RAM or GPU can sometimes solve the problem, but not always. The OS's behaviour has gone right back to the 90s where some hardware components simply don't play well together. This time though, Windows has a much greater hand in causing the problems. Looking at your event viewer [under custom > administrative events] and you should find several warnings about DistrubutedCOM, which Windows professionals tell everyone to ignore. There might also be AppModel-Runtime errors, Kernel-PnP warnings etc. Most of those can be looked into to discover which programs or components cause the issues. Mostly though, if you look for Critical level Kernel-Power events, those will likely be one of the first things logged when you log in after an improper shutdown [crash]. Look at the time entries for the DistributedCOM warnings and you should see a bunch of them sprawling out right before the Critical Kernal-Power event. Even if these have nothing at all to do with the crash, they telegraph when a crash is going to happen.
If you search for this following entry in Google:
"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user MYPC\ME SID (S-1-5-21-3926987949-1147637787-569123-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."
- or smaller chunks of it, you'll be able to find a history of users having this problem. The reason I went through all of this jargon is so you can cross reference the symptoms with all of the forums the search will return. From the threads which include system specs, you'll be able to see that all brands and all speeds have suffered this problem. I first encountered it when I put my 5700xt in, but there are threads which complain of this since Windows 7. The user above in this thread who said he changed to nVidia and had no more problems made a good choice for his system, but changing GPU is not a guarantee.
I did try the suggestion of reducing features such as image sharpening, and I even attempted to use absolutely no special features at all, but I still had the crashes. After that, I got annoyed and ramped everything right up to the highest qualities, things my monitor can't even benefit from at 1080p, and it actually ran a bit better. I got a two-day run after messing around with Windows services settings but eventually it crashed again. I'm no programmer and I have no idea what most of those services actually do beyond what Google search can tell me.
My point is, the problem is Windows being difficult, and if you get this problem you're just unlucky. Windows staff are apparently trying to fix it, but compared with millions upon millions of users who have no problems, we're just not a priority. It won't be long before I move over to Linux, the only reason I haven't yet is because I have yet to learn enough to feel confident using it. AMD opened up Vulkan to enhance Linux support, so I really am running out of reasons to stick with Windows, I've just always had it on the system. I expect Linux will have some distros with GUIs which don't look like the back of a house-brand cereal box, not to mention I'll enjoy using my PC without having Cortana shove Bing's balls in my face every time I forget that the search bar has Stockholme syndrome.
