How to: No longer getting pixellation and potato-ing of my PC

BLUF: Gamebar and GameDVR services were, unknown to me, jacking up my PC, so I learned some stuff and did some stuff and it's no longer happening. I don't even own an Xbox, so why TF was it happening?

One word: Microsoft

What worked for me:
1) Settings>Gaming>Game Bar - Set to off.
2) Settings>Gaming>Game Bar - Allow your controller to open Game Bar unchecked.
3) Settings>Gaming>Captures - Everything set to off.
4) Settings>Gaming>Game Mode - On
5) Control Panel>Hardware and Sound>Power Options - High Performance
6) Services - Disable anything that starts with Xbox
7) (At your own risk) REGEDIT>Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\GameBar - UseNexusForGameBarEnabled set to 0. Should look like 0x00000000 (0) after changing it.
7) Restart PC
8) Rejoice

Will all of that work for you? I hope so, but I really don't know.

Longer version follows...

Disclaimer: Prior to OCT2023, I knew neither jack nor shit about things like this. I'm writing this after four months of doing different things to try to get my PC back to how it was prior to October 2023. Turns out, Microsoft decided to give us an update with a bunch of stuff we (me) did not want or need, and also gave us no option for turning some of it off via services. That said, I still know neither jack nor shit about things like this.

My PC: AMD Ryzen 9 5950X 16-Core Processor 3.70 GHz

64-bit operating system, x64-based processor
Windows 10 Pro

Version: 22H2

Video: Radeon RX 6800 XT

Genesis: Starting back in October, while playing PoE, my computer screens would randomly lock up. I could still hear audio from the game and any other audio running at time of lock up. All motherboard LEDs remained green with no errors. Video streaming would still be playing and could be heard. No amount of key smashing or anything else would free up the screen and there was no key sequence that would allow for system shut down. The only way I could restart my PC was to either shut it off at the power supply or hold down the power button on the front of the PC.

Also starting in October was random pixelizationalizing (my word) and big slow down in game performance, but only while playing PoE. Any other game worked fine with no hiccups and no PC video lock ups. If you ever played PoE on a PS4, it was just like that.

Going through event logs, I was seeing a bunch of stuff I knew nothing about, but there were a few errors and warnings popping up in the same sequence just prior to lock up.

This error was received twice in short order between 5 to 15 seconds apart from one another.

Error 10010: "The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout."

There were two other warnings preceding Error 10010.

Warning The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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.

and....

Warning The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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.

CLSID and APPID would change from time to time, but both warnings would be just prior to receiving the errors. There were other warnings coming in just prior to lock up, but from what I've gathered, they were random and not associated.

Did either warning have anything to do with error 10010? F if I know, but they all were happening in the same sequence each time.

After reading through many many posts about error 10010, I was really no closer to understanding what was really causing it. Everything from "don't worry about it because it doesn't mean anything" to "it could mean something sinister" to even "you need to reload your PC OS and install new drivers".

It's almost like asking google if my headache is caused by a hangover or a brain tumor.

Turns out, for me it was all boiling down to "GameDVR and BroadcastUser Service_85ae1" and not being able to disable it. When attempting to disable, or change anything for GameDVR service, is attempted you will receive "The parameter is incorrect". Well crap.

Game Bar and all of the associated services that enable it can and will record in the background without you knowing it. The reason for this is MS thinks people are really wanting to know what happened just prior to dying in a game. So, you just hit the correct windows key combination and you can view the previous two hours of gameplay. Yup, two hours. You can change it to whatever you want, but two hours is the default.

Also turns out that all two hours are stored and held in whatever memory allows for quick access, most likely RAM. Correct me on that, because I am paraphrasing comments made by people that actually know what they are talking about.

If you've bothered to read this far, you've earned a cookie.

There was a bunch of other stuff that I did and tried with no effect to the original problem, so I won't bother mentioning them.

I hope this helps someone out there as much as it did me.

Game on!

Links that helped me understand what was going on:

https://obsproject.com/kb/windows-gaming-features-troubleshooting

https://www.reddit.com/r/pcgamingtechsupport/comments/hhnsfw/service_host_game_dvr_and_broadcast_takes_70/

https://www.youtube.com/watch?v=DdNFo0A54vg

https://www.howtogeek.com/325292/what-is-broadcast-dvr-server-and-why-is-it-running-on-my-pc/

https://www.addictivetips.com/windows-tips/how-to-fix-high-ram-usage-by-game-dvr-server-in-windows-10/