• I ran Memtest86 on the RAM sticks (Crucial Pro 128GB Kit (2x64GB) DDR5 RAM, 5600MHz) when I purchased them roughly 6 months ago for 2 passes, no errors.

• Crash occurred around 16:09, wasn't doing anything heavy on the server, all drives were spun down I believe.

• The previous crash I attributed to a docker container being in a restart loop, I have since removed the container. Not sure what could be causing this crash.

• Attached diagnostics zip to post. Appreciate any help.

This is a snippet of my syslog for the 12 hours before the crash, not shore what the x86/split lock detection or the Server kernel: traps: chromium[3052958] trap int3 is about.

Mar 22 04:34:42 Server kernel: traps: chromium[2268916] trap int3 ip:55d2328dca0b sp:7ffe9c2921b0 error:0 in chromium[6118a0b,55d22d695000+c0b6000]
Mar 22 04:42:41 Server emhttpd: read SMART /dev/sdc
Mar 22 04:43:10 Server emhttpd: read SMART /dev/sdb
Mar 22 04:50:01 Server rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="16905" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
Mar 22 04:59:00 Server emhttpd: spinning down /dev/sdb
Mar 22 04:59:00 Server emhttpd: spinning down /dev/sdc
Mar 22 06:56:35 Server kernel: traps: chromium[3052958] trap int3 ip:5569565c8a0b sp:7ffff5b3cb90 error:0 in chromium[6118a0b,556951381000+c0b6000]
Mar 22 07:03:49 Server kernel: traps: chromium[3090581] trap int3 ip:556ada948a0b sp:7ffdc19262d0 error:0 in chromium[6118a0b,556ad5701000+c0b6000]
Mar 22 08:17:08 Server kernel: x86/split lock detection: #AC: CPU 1/KVM/45742 took a split_lock trap at address: 0xfffff8037c650d8d
Mar 22 09:56:36 Server kernel: traps: chromium[4040633] trap int3 ip:5636f0cc2a0b sp:7fff6f81c810 error:0 in chromium[6118a0b,5636eba7b000+c0b6000]
Mar 22 10:03:49 Server kernel: traps: chromium[4078120] trap int3 ip:556432aa0a0b sp:7fff5fb89cd0 error:0 in chromium[6118a0b,55642d859000+c0b6000]
Mar 22 10:34:41 Server kernel: traps: chromium[55077] trap int3 ip:55cd3603ba0b sp:7ffe98dcc760 error:0 in chromium[6118a0b,55cd30df4000+c0b6000]
Mar 22 12:56:36 Server kernel: traps: chromium[856187] trap int3 ip:557abffc4a0b sp:7ffec6474450 error:0 in chromium[6118a0b,557abad7d000+c0b6000]
Mar 22 13:03:50 Server kernel: traps: chromium[893618] trap int3 ip:555c4654aa0b sp:7ffc403d0780 error:0 in chromium[6118a0b,555c41303000+c0b6000]
Mar 22 14:40:53 Server kernel: x86/split lock detection: #AC: CPU 3/KVM/45744 took a split_lock trap at address: 0xfffff8037c650d8d
Mar 22 15:14:33 Server kernel: hrtimer: interrupt took 17448 ns
Mar 22 15:56:37 Server kernel: traps: chromium[1926269] trap int3 ip:5563cb6f8a0b sp:7fff46e32ff0 error:0 in chromium[6118a0b,5563c64b1000+c0b6000]
Mar 22 16:03:50 Server kernel: traps: chromium[1974396] trap int3 ip:55bb54104a0b sp:7ffe8eeb83b0 error:0 in chromium[6118a0b,55bb4eebd000+c0b6000]
Mar 22 16:10:03 Server rc.rsyslogd: Syslog server daemon...  Started.

server-diagnostics-20260322-1624.zip

Edited March 22Mar 22 by unraid_user11
syslog details

Regarding the chromium traps, I get them while running changedetection in docker which uses Chromium. Guessing it's probably not your issue, but it's good to note that some docker errors get logged to syslog.

Because memtest is only definitive if it finds errors, since you have multiple RAM sticks, try using the server with just one, if the same try with the other one, that will basically rule out bad RAM.

21 hours ago, JorgeB said:

Because memtest is only definitive if it finds errors, since you have multiple RAM sticks, try using the server with just one, if the same try with the other one, that will basically rule out bad RAM.

Appreciate the advice, any time frame I should run the server on one stick for it to be definitive?

I would say double the time it typically takes to crash.