I have another way to cause the error to occur.
While having the Radeon Adrenaline window open to Global Graphics > Display, I get a grey glitch bar which looks like screen tear if I click between display one and display two buttons on the Adrenaline client. Each time the glitch occurs, if I refresh my event viewer I see a new entry of "Failed with 0x57 retrieving AppModel Runtime status for package Windows" (ID 65) logged at about two or three seconds before the glitch grey-bar flashed. The bar flashes about a quater down from the top of both displays.
I've also seen that after twenty or so entries of the aforementioned error, a Distributed COM warning appears in the event log and after that the Error ID 65 stops being logged for a while, but I can still cause the grey-bar to glitch flash by doing the same thing. I'm wondering if this issue might have to do with using multiple displays and/or switching between them. I've read that some users don't get this problem, and monitor count is something which varies from PC to PC, along with whether DP or HDMI is used (I use both monitors via HDMI). I'm releived that a range of brands and models of hardware suffer this issue, it means that I probably won't need to replace any one thing or another.
Also, I have reduced the frequency of the crashes by changing a bunch of Services settings from maual to automatic, to try and make sure whichever component couldn't access/be accessed was started at the time it was needed. It's better, but I still get occasional crashes.
Hopefully this is helpful in some way.
Thanks to everyone so far. All the officials have had to say collectively is "It's not a DCOM issue, ignore the DCOM warnings." It seems like this one's up to us to figure out.
System specs:
Windows 10 version 2004
Ryzen 5 2600
Sapphire 5700xt Nitro+
MSI B450M-A Pro
16GB G.Skill Fortis 2400
OS SSD is a WD green 240GB
Monitors are BenQ RL2455 (main), Asus VE248. Both through HDMI at 1920x1080 60hz.