Random kernel loop-crashes

The kernel seems to crash loop randomly. Audio logs loop at a 2 second interval (approximate). It doesn't happen very often, but it is often enough that it has an impact. I will not post journalctl or systemmd because there is no useful information there. If there were, I would not be posting this.

Here is some info on my overall build

CurrentDmesg: https://launchpadlibrarian.net/568643403/CurrentDmesg.txt.txt

Dependencies: https://launchpadlibrarian.net/568643404/Dependencies.txt

CPU Proc Info: https://launchpadlibrarian.net/568643405/ProcCpuinfoMinimal.txt

• DistroRelease: Ubuntu 21.10

• Package: ubuntu-release-upgrader-core 1:21.10.8 [Refer to the varlogs below]

• ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19

• Uname: Linux 5.13.0-22-generic x86_64

• ApportVersion: 2.20.11-0ubuntu71

• Architecture: amd64

• CasperMD5CheckResult: Unknown [system gave me an error]

• CrashDB: ubuntu

• CurrentDesktop: ubuntu:GNOME

• InstallationDate: Installed on 2017-03-09 (1709 days ago)

ProcEnviron:

PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
SHELL=/bin/bash

Don't know if there's anything of note in there, but it's there for anyone to look at.

Temporary solution: I used timeshift to restore to my factory kernel. Dunno what the kernel I was using did, but it somehow completely or partially corrupted nearly all my backups.

PRESUMED SYMPTOM - While browsing the varfiles that could potentially cause this, The release upgrader didn't look right to me. I'm not a code genius, but I think this may be a bug (Reported to launchpad already, no response so far). With that said, here are the logs.

VarLogDistUpgradeAptHistory Log: https://launchpadlibrarian.net/568643406/VarLogDistupgradeAptHistorylog.txt

VarLogDistupgradeAptlog: https://launchpadlibrarian.net/568643408/VarLogDistupgradeAptlog.txt

Apttmerlog: https://launchpadlibrarian.net/568643409/VarLogDistupgradeApttermlog.txt

Lspci Log: https://launchpadlibrarian.net/568643410/VarLogDistupgradeLspcitxt.txt

Hopefully the good folks at Launchpad can confirm whether this is a bug or not. Until then, I can hope to get this sorted here. Will update via comments.