Soxekaj

+1

Disabling XMP did the trick.

That is what i was assuming, but given my predicament, I just wanna get everything right. I do have a hard time seeing why XMP or any other hardware component would cause this, since it happens pretty tight around 15 min after parity check finishes. If it was hardware related, wouldn't it also happen during the check, or is the hardware being hit differently after the check?

Are you recommending running with XMP active? Will get a hold of a gpu, so that i can access BIOS and check settings for power savings.

RAM is runnuing at base clock speed (2666), don't think i have XMP active, but not sure, been a while since i was in bios and i don't have a graphics card in the machine (model F i3, so no on chip graphics). I have not done intentional reboots for a while, so if you look at April that is probably only crashes for that period.

Here we go, complete syslog file. I made a copy of the content while i had it in my pc as you sugested. Ran chkdsk, nothing found: syslog

It is set up correctly, these are just grabs from putty because i had problems transfering the file off the machine. I can try again if you want the entire log.

The crash doesn't happen instantly when the parity check stops, but usually withing 30min or so (it varies) I managed to get syslog of what is happening just before the crash and after. These are for the last 2 times it happened (early this morning and this afternoon) Also attached is the diagnostics as requested. tower-diagnostics-20200427-1608.zip syslog1.txt syslog2.txt

I have been experiencing a weird issue for the past couple of months. Shortly after a parity check finishes or i cancel the check, the server reboots. This of course triggers a new parity check and so the circle is complete. I have syslog setup to mirror to flash, and when checking with cat, it runs through a bunch of log, but once it finishes, I can only access the logs from after the crash. Anyone have any input on why the crashes might be happening or maybe a way to see the logs from before the crash, so that might bring answers to light.