Repairing has seemed to work since, though it didn't the first time I had tried it (there were also GadgetBridge updates though)

It's been fine since! I should probably update it again, but that's another task's task.

I was about to be like "well this has been working fine for ages now, time to close this task!" and then I noticed my comment above and yeah, /etc/cron.hourly/kludge is still marked executable. So uhh lets disable that and see if things remain stable before I hang up the Mission Accomplished banner...

I should work https://daniel.haxx.se/blog/2023/03/02/the-curl-nuget-story/ in here

Sounds like it has been solid ever since, so that must have been it? Or perhaps something else coincidentally changed, I suppose. But for now this awaits a newer firmware version to try and see if it resolves or resurrects the problem.

https://jointakahe.org/ might be worth checking out

Video testing using YouTube mostly in Chrome but also a bit in Firefox hasn't crashed it on @pwrightlindl's PC yet since downgrading to firmware version 2803 . . .

As @pwrightlindl noted in chat, it's a real crapshoot of solutions out there. For example:

This worked for me! I was able to fix it increasing my DRAM voltage by a little (0.3), not the full 0.05 as recommended in the post.

https://linustechtips.com/topic/1409230-pc-hard-reset-on-both-windows-and-linux-error-type-cache-hierarchy-error-solved-rma/ does mention having the problem occur on Linux as well, and also mentions, intriguingly,

I have disabled Core Performance Boost(CPB) which "solved" my issue.

https://www.asus.com/motherboards-components/motherboards/prime/prime-b550m-a/helpdesk_bios/?model2Name=PRIME-B550M-A lists the most recent firmware versions as

Keeps dying; checking the Pleroma service log via journalctl gives me

Keeps dying; checking the Pleroma service log via journalctl gives me

Rebooting the entire system worked, which . . . oof. I don't like that one bit.

Haven't seen it go as bad as that again, but I'm still getting the

Well damn

Everything seems fine so far? Closing this issue again, but warily . . .

wait nevermind it's done already, guess my extreme upgrade last time gave me the wrong impression about how long it'd take haha

Alrighty, got the pleroma and nginx (just because I like shutting that fucker down) services stopped and I'm running the database upgrade from https://docs.pleroma.social/backend/administration/updating/#for-otp-installations now . . .