Im hoping I can get some help with a problem I am having. My system will randomly become unresponsive and I will have to reboot it with the physical switch on the front of the PC case.

I think I have correctly setup logging so that it saves to the boot USB drive but I have no idea what im looking at when I open them.

Can someone please help me figure out what this log means and if they see something out of the ordinary?

syslog-previous

Attach Diagnostics ZIP to your NEXT post in this thread.

srmserver-diagnostics-20260813-1854.zip

Edited August 14Aug 14 by silentsnow31802

I see "rcu_preempt self-detected stall on CPU" at the end of the log. I assume this is the issue? A quick search points to possible bad RAM. Ill get a memtest done when I can.
If there is anything else please let me know.

See here firts: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

On 8/13/2026 at 11:46 PM, JorgeB said:

See here firts: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

Thank you for this. I will check this out this weekend and report back. Seems very likely that this is my issue.

I have set CPU Idle Control to Typical Current Idle in the BIOS settings. Hopefully that does the trick. If not ill work on disabling C-States.

Appreciate the help!

So is this thing still on?

This morning I was wondering why my Server wasn’t showing up within my finder on mac, since is happens from time to time that finder throws it out, I wasn’t really concerned with it - After 3 Failed reconnects I was and If it wasn’t for them, after Plex hasn‘t shown any Libraries after starting it - I was.

Quick trip to the GUI and I knew what happened: System Crashed, out of the Blue at roughly 12pm last night, right around midnight. I don’t know what happened or why it happened in the first place.

I’ve attached the diagnostics but I’d really appreciate any tips or solutions to or for fixing it. Sick of these unclean Shutdowns for months now

Cheers and Thanks in Advance

Alex

EDIT: Took the liberty to @ @JorgeB and @silentsnow31802

server-diagnostics-20260930-1345.zip

Edited September 30Sep 30 by deltaexray

EPYC CPUs should not have this issue, enable the yslog server and post that after a crash, though I would recommend starting a new thread since this one is marked as solved and it's not the same issue.

Okay, will do. And I think the yslog server is already running I might have to check

2 minutes ago, deltaexray said:

And I think the yslog server is already running I might have to check

It could be worth listing a screenshot of your syslog settings. They are frequently set incorrectly.

3 minutes ago, itimpi said:

It could be worth listing a screenshot of your syslog settings. They are frequently set incorrectly.

Thank you for pointing that out, In fact the server wasn’t running at all: Screenshot is attached, If you could provide me with the settings that works best It would be greatly appreciated!

https://docs.unraid.net/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs/#enabling-the-syslog-server

Follow the instructions for Local syslog server

35 minutes ago, trurl said:

https://docs.unraid.net/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs/#enabling-the-syslog-server

Follow the instructions for Local syslog server:

Thank you!

I have followed the instructions and set it up, after the Parity Check is done I’ll reboot the system and check if the log server works. Thank you :)

On 8/13/2026 at 11:46 PM, JorgeB said:

See here firts: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

So im back a month and a half later. Ive had 2 system crashes since. One the server rebooted and recovered on its own, the second it stayed frozen and need manual intervention.
I have not tried to disable C-States yet but that is next on my list of things to do. I just ordered a screen to hook to the server to make troubleshooting these things more convenient.
In the meantime can someone check my most current log? It was taken right after the system came back up. It crashed right after I logged out of it.
Appreciate any help I can get.

srmserver-diagnostics-20261001-2226.zip

Edited October 2Oct 2 by silentsnow31802

The logs show no software error before the crashes. What they do show points to a hardware/firmware stability problem:

- The August crash was a CPU stall: one core was waiting for another core to respond, and it never did.

- The crash where the server rebooted by itself was recorded on the next boot as an internal CPU shutdown event. That means the CPU itself triggered the reset.

- The last crash left nothing in the log. The syslog just stops, and the next boot shows the reset button was used.

Most important: your board is still on BIOS 0604 from July 2019, the first X570 BIOS, released at the Ryzen 3000 launch. There have been many AGESA updates since then, and several fixed exactly this kind of random hang and reboot. Please update to the latest BIOS for the ROG STRIX X570-E GAMING.

The update resets the BIOS settings, so afterwards:

- Set Power Supply Idle Control to Typical Current Idle again.

- Leave the CPU and RAM at stock: no PBO or overclock, and disable DOCP/XMP for now.

- Check that the Unraid flash drive is still first in the boot order.

If it still crashes after that, disable Global C-state Control. Running memtest is also a good idea, but keep in mind that a pass doesn't completely rule out the RAM.

Keep the syslog mirror to flash enabled; it's working. If it crashes again, post the diagnostics after rebooting.

1 hour ago, JorgeB said:

The logs show no software error before the crashes. What they do show points to a hardware/firmware stability problem:

- The August crash was a CPU stall: one core was waiting for another core to respond, and it never did.

- The crash where the server rebooted by itself was recorded on the next boot as an internal CPU shutdown event. That means the CPU itself triggered the reset.

- The last crash left nothing in the log. The syslog just stops, and the next boot shows the reset button was used.

Most important: your board is still on BIOS 0604 from July 2019, the first X570 BIOS, released at the Ryzen 3000 launch. There have been many AGESA updates since then, and several fixed exactly this kind of random hang and reboot. Please update to the latest BIOS for the ROG STRIX X570-E GAMING.

The update resets the BIOS settings, so afterwards:

- Set Power Supply Idle Control to Typical Current Idle again.

- Leave the CPU and RAM at stock: no PBO or overclock, and disable DOCP/XMP for now.

- Check that the Unraid flash drive is still first in the boot order.

If it still crashes after that, disable Global C-state Control. Running memtest is also a good idea, but keep in mind that a pass doesn't completely rule out the RAM.

Keep the syslog mirror to flash enabled; it's working. If it crashes again, post the diagnostics after rebooting.

I will do this and report back once done. I had no idea my bios was that old!
Really do appreciate all the help.

Just a quick update. I got all the above steps complete and am monitoring.
Will report back in a month if I have no crashes. Hopefully you don't hear from me before then!