Side observations:
are these on for a reason
18:57:36.713: Windows 10 Gaming Features:
18:57:36.713: Game Bar: On
18:57:36.713: Game DVR: On
Did you review your log? did you check OBS' log analyzer?
18:57:40.055: obs-browser: URL
https://obs.blerp.com/pwn/ocnzf6usi-rk Mon Apr 25 2022 18:57:40 GMT-0400 (Eastern Daylight Time) (source:
https://obs.blerp.com/pwn/ocnzf6usi-rk:429)
18:57:40.058: obs-browser: SOCKET_BLERP_VERSION 23 "5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 OBS/27.2.4 Safari/537.36" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 OBS/27.2.4 Safari/537.36" (source:
https://obs.blerp.com/pwn/ocnzf6usi-rk:500)
18:57:40.431: obs-browser: CONNECTION_SUCCESS OBoRIGA9HS3LLQZPGrzj ocnzf6usi-rk (source:
https://obs.blerp.com/pwn/ocnzf6usi-rk:504)
18:57:40.743: obs-browser: Uncaught (in promise) AbortError: The play() request was interrupted by a new load request.
https://goo.gl/LdLk22 (source:
https://streamelements.com/overlay/scripts/vendor.js:25242)
streamelements correlates with more errors than I can count.. so I stopped trying... streamelements code is worse than bad. so I'll stop there.
so not sure if you intended to use both blerp and streamelements, or ??
without knowing better, I'd advise attempting a test stream without either. that will hopefully lock down if issue is their crap code, or something with the frame capture of aces, or possibly one of your other plugins
oh, and a year ago, it was well-documented that streamelements so messed with core OBS functionality, that the fix was a wipe and fresh-install of OBS. I have no idea whether such would be required for you or not.
Hopefully you are only connecting via OBS browser, and didn't install streamelements plugin? [not my area, don't know if that is even possible/practical]
Good luck