Server crashing CPU PID tainted/ call trace

[joeyrock13]

 This started a few days ago, server stays up up for less than an hour before receiving these messages in the logs. Unable to access server GUI unless i physically shut down the system. Someone pls help

Edited April 8 by joeyrock13
Screenshots

[JorgeB]

Enable the syslog server and post that after a crash together with fresh diagnostics.

[joeyrock13]

7 hours ago, JorgeB said:

Enable the syslog server and post that after a crash together with fresh diagnostics.

Okay will do

[joeyrock13]

21 hours ago, JorgeB said:

Enable the syslog server and post that after a crash together with fresh diagnostics.

 

Unconfirmed 612505.crdownload

[JorgeB]

And the persistent syslog?

[joeyrock13]

8 hours ago, JorgeB said:

And the persistent syslog?

alfred-syslog-20240409-1630.zip sorry had to do a lot of unclean restarts for the server to stay up long enough to download them, ended up going into safe mode

[JorgeB]

That's not the persisting syslog, but looking at the one posted before, there are already a lot of crashes, one even before starting the array, looks more like a hardware issue to me, start by running memtest.

[joeyrock13]

How do I get the persistent syslog? I enabled it in settings 

[JorgeB]

Post a screenshot of the syslolg server settings, there's a common mistake users do.