chishola1

After not being able to get windows to load I replaced the CPU and it seems to have fixed it. Time will tell but I am not seeing any errors in the log and I am able to shutdown the machine properly again. Thank you for the help.

I'm asking for a recommendation for a 13/14 gen cpu if I find that my 13900k is bad.

If the diagnostic tool shows that the processor is bad what would you recommend replacing it with without having to replace MB?

Already updated to current version

It was doing this before I pulled it but I will verify that there are no damaged pins.

I will throw a windows hdd in and run the intel Processor Diagnostic Tool

I removed it yesterday, but that was while troubleshooting this issue. The server had been up for around 30 days and then just died. No changes were made during that time, hardware or software.

I just checked my log again, Sep 29 08:31:16 Leviathan kernel: python3[28091]: segfault at 0 ip 0000000000000000 sp 00007ffc06550728 error 14 likely on CPU 6 (core 12, socket 0) Sep 29 08:31:16 Leviathan kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Sep 29 08:32:00 Leviathan kernel: .NET ThreadPool[30288]: segfault at 9 ip 0000153a4357eb88 sp 0000153a18eb50d0 error 4 in libclrjit.so[17eb88,153a43400000+322000] likely on CPU 6 (core 12, socket 0) Sep 29 08:32:00 Leviathan kernel: Code: a0 45 31 ff 41 0f b6 c1 89 45 c4 44 0f b6 6d ac 4d 85 f6 75 2d 48 8b 45 a0 4c 39 e0 44 8b 75 90 0f 84 a3 03 00 00 41 83 c7 40 <4d> 8b 74 24 08 49 83 c4 08 4d 85 f6 74 e1 66 2e 0f 1f 84 00 00 00 Sep 29 08:33:02 Leviathan kernel: python3[38176]: segfault at 0 ip 0000000000000000 sp 00007fffe0625b88 error 14 likely on CPU 6 (core 12, socket 0) Sep 29 08:33:02 Leviathan kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Sep 29 08:33:17 Leviathan kernel: deluge-console[39808]: segfault at 0 ip 0000000000000000 sp 00007fff162e8e68 error 14 likely on CPU 4 (core 8, socket 0) Sep 29 08:33:17 Leviathan kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Sep 29 08:33:17 Leviathan kernel: deluge-console[39849]: segfault at 0 ip 000014e542d799ed sp 00007ffd154f1bb0 error 4 in libpython3.13.so.1.0[1799ed,14e542c3a000+2cc000] likely on CPU 6 (core 12, socket 0) Sep 29 08:33:17 Leviathan kernel: Code: ff ff 0f b6 dc 41 89 c2 0f b6 c0 4c 63 fb ff 24 c6 f3 0f 1e fa 48 8b 85 b8 fe ff ff 49 8b 7c 24 f0 4d 8b 7c 24 f8 4c 89 68 38 <48> 8b 07 49 83 c5 02 85 c0 78 27 48 83 e8 01 48 89 07 75 1e 48 8b Sep 29 08:34:07 Leviathan kernel: python3[44547]: segfault at 0 ip 0000000000514e39 sp 00007ffff7c8a5c0 error 6 in python3.9[114e39,41f000+289000] likely on CPU 6 (core 12, socket 0) Sep 29 08:34:07 Leviathan kernel: Code: 48 85 ff 0f 84 12 6a 00 00 48 8b 47 38 48 85 c0 0f 84 05 6a 00 00 4c 89 fe 44 89 4c 24 40 4c 89 f7 ff d0 44 8b 44 24 40 89 c6 <49> 83 2f 01 0f 84 be 4d 00 00 49 83 2e 01 0f 84 f8 4c 00 00 85 f6 looks like it is not just python

Could you help me understand the output of that command?

What is the best way to find/disable that python script?

I started getting seg faults on my unraid server. I have tried replacing the ram but the faults stay the same. Another oddity, I am not able to shutdown the server. If I use the button on the GUI 90% of the time nothing happens and if i use the CLI it starts but eventually starts getting call traces and never shuts down. leviathan-diagnostics-20250928-1250.zip

I am setting up Conan Exiles and it says that it should be run in a docker container on the setup page. The only problem is when i have it set to run in a container I get this error " The user running AMP (amp) must also be a member of the 'docker' group.". What is the solution for this? Over an hour of googling and still no answer. Please help.

I am still having issues running PLEX on my server. When I run PLEX the server goes unresponsive after about an hour. The only way to recover is to do a hard reboot. There is nothing shown in the unraid error log and BIOS is current. I have ran memtest with no errors and the intel diagnostic utility with no errors. I am out of ideas.

I have reached out to GIGABYTE to ensure I get the current BIOS. @Frank1940 Does the syslog point to that being the issue?

I have tried the container support thread with little success.