Hello all,

I'm currently running 6.12.15 with the following hardware: intel i5-12600k, z690 asrock m-itx, 32gb dr4 3200mhz ram, in a DS380 case. Don't have many plugins: (appdata backup, CA, Fix common probs, GPU stats, GUI search, Intel GPU TOP, Unassigned devices, UD+, UD preclear, unbalance, and unraid patch).

What I'm encountering is this: At seemingly random, the system will crash and boot back into Unraid with the array not started. This started around when I needed to replace a failing parity HDD (I have dual parity) and I noticed that when I let it run Parity-sync overnight that I would come back to it in the morning with the array not started and the warning that the parity drive would be overwritten still present. Sometimes it takes hours for it to crash, sometimes minutes, I can't understand it! I have done the following:

Replaced the PSU

Attempted to run Memtest86+ testing for 24 hours (this also either crashed sometime overnight or stopped itself after running for hours, though did initially pass)

Changed UPS that it was plugged into

Changed motherboard UEFI to defaults (though all that I had changed was enabling SR-IOV and setting the XMP of the ram from 2400MHZ to 3200MHZ)

This system had been running just fine up until this last month. I notice that sometimes when I try to mess with the UPS Daemon that the GUI in my web browser will freeze or stop working. As it is randomly crashing I haven't been able to find a log that persists or points to anything obvious causing it despite copying the logs to the flash for the syslog server. I've attached the last 4 diags of the last 4 times I've attempted to change things and run Parity sync. Any and all help is appreciated, and if I haven't given enough information or context please let me know! My apologies for the vagueness, I'm somewhat computer literate but this really has me stumped. I'm more a hardware person than a software person.

tower-diagnostics-20250617-1346.zip tower-diagnostics-20250616-2027 (1).zip tower-diagnostics-20250607-1129.zip tower-diagnostics-20250617-1356.zip

Edited June 17, 20251 yr by Kmon
changing reboot to crash for clarity

11 hours ago, Kmon said:

this also either crashed sometime overnight or stopped itself after running for hours

That basically confirms it's a hardware issue.