Thursday at 05:25 PM1 day Hey all! My first time asking something on these forums, so do let me know if I missed any context that might help with answering my question :)For the last few days, my server's been randomly freezing up - not quite shutting down (fans remain running and lights're on) but not responding to keyboard inputs either, with a connected monitor also freezing up. Connecting to the IP assigned to the server doesn't work either.This happens regardless of whether any docker containers are running, though I've not yet caught any freezes while all disks are spun down.Any ideas or suggestions on what to try next? I've included diagnostics and the various syslogs that were saved to the bootdrive, with syslog-5 showing an actual shutdown as triggered from the interface. syslogs.zip tower-diagnostics-20261022-1723.zip
Thursday at 05:57 PM1 day Community Expert The logs show that these are hardware-level crashes, not an Unraid software crash. After two of the freezes, the next boot reports that the previous reset happened because of "an uncorrected error caused a data fabric sync flood event", and it logs a machine check error from the CPU. Each freeze ends silently, with no errors logged before it, and two of them happened just a few minutes after boot, when the server was doing almost nothing.This is a known problem with first-generation Ryzen CPUs like your 1600: the server can hang when the CPU is idle or under very low load. Please try these BIOS changes:1. Look for "Power Supply Idle Control" and set it to "Typical Current Idle". On MSI boards it is usually under Settings > Advanced > AMD CBS > Zen Common Options.2. Make sure A-XMP is disabled and the CPU is not overclocked, so everything runs at default settings. Also, what RAM modules do you have installed? 24GB suggests mixed kits.If it freezes again with those settings, also disable "Global C-state Control" (same menu) as a test. If it still freezes after that, run Memtest86+ for a few passes. After that, the CPU itself would be the next suspect.Keep the syslog mirror to the boot drive enabled, and if it freezes again, post new diagnostics after rebooting.
22 hours ago22 hr Author Thanks for the answer!I've changed the bios-settings as you indicated in 1 & 2! Though for any future readers that might come across here, I found those settings under the overclock-settings of my BIOS.As for RAM, yeah, those are 2 different kits - one 2x8 and one 1x8. The 1x8 should've been a 2x8 as well, but those were secondhand and one of the RAM-sticks turned out to not work so I left it out.Will let you know whether it freezes again after the changes!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.