Repeat System Crashes - Kernel Tainted

spencerskinner

New Member
Apr 17, 2023
5
1
3
Hi,

I have been having pretty major stability issues with my Proxmox issues.

Here is an image of the local console during a crash, the error will repeatedly change to a different CPU core, this console data also never gets added to the proxmox system log. The hardware im running is a Ryzen 3600 on an ASRock X470 D4U, latest BIOS and microcode (I have CBP, PBO and C-States disabled as they are known to cause instability in these boards).


QbrPbYHzn8sProL0IjCc-egYadJTCMopzcSXc-AdNl8wBdLSH6IbaXIOMd9St_Cq_qy5sKazuHUIalw99srcadZuC-yASsPp2LKHP8bIYkbE8qAEMWO8FsPi4vgfYCyEZy50T5mC1UaVNoJpHbVHB9CCSfSWcHz3qFQC_WE2CLsHhuGkKt6i-3Teu9o80HaS2IwnkeQS-tAM8kDXSUujMIRK0mXoChCgmAZn7m4rJOmrC-zBfza2WDpNZz-gEkSfog1y6DNk3MokvtqXZgElUXmqKUGg67-WGFyvUn4y6M_a5sQiuPVptEKJ88KVG_j9ptLZagGLlf33l2lRZf1gfun82JK-nOxa5OCM6liSnTnwrvXSEhi3HZr4aYNGJlIQ4VSjTeZyXDeuZBd551Wofaoa1phDSMajp_dBZhScb-Fo_RWMMpZ72fqZ5W4UcNycXsngpVIV1HJLcUVY7QXTRhOoPOWxa-0Z-Nvdg97AdAYvsUC5JXVqh0xs_CTeRfMCAjGdADVKJtjJoj743jVIYis-DcOGeaU1n9ypVWliHJoczy-AxRdZDHfS8IxHmNC8vIH4zfi1f2KFB7Ot2vjREpZMbFdH4YMOk6GT5s7Di_nMulBcfI3xuuyCtnDiKCJnN9c_T8m0NplOF21XxalPKRdp6Wi7tq7-XOAkApVhVQEUtlWdBt67hd-16fd0q6P0VDAU85-fecFqKZRGBQnSLUGwcJcGL9IA6dKcmLa-k1W1WdFrXfLShC1IJ1ADYoD6iWRW_rzZ6Q0zPvFRZBs7860_AtHiy8h4c2sJolDzwjPGKVIPyNFSqNScNOw37ewHsGR2--G_ynwha1dEihk08c_3Glk3RGRnRld7oyL_s5NRasvcTYxRCJ5JNtKLrlekuLtaorbDljHM9f35iYz0iI82-z5zoRtY5XeNHoecP29soL489A=w1244-h937-s-no


In terms of what im running on the server its just an LXC Container with Plex and Docker installed on it, I have a 3060 Ti passed through to the container, I have tried removing this but its not helped.

Any ideas of what could be causing this/what could be done to resolve this?

Many Thanks
Spencer
 
Last edited:
Hi,

Thought I would update this, so after trying just about everything software side, started doing hardware stability checks, turns out I just had a bad CPU, swapped out for a new 3600 and its been up for 5 days solidly now with default BIOS settings.

Spencer
 
I'm glad you found a solution for this one, identifying a bad CPU is particularly hard. Was there a particular thing that you spotted in the logs, or was it a matter of swapping components until the problem went away?