digital_alchemy

Memtest was ran for multiple passes and passed with no errors. That was my first thought also, since I had swapped out the RAM, but that doesn't seem to be the issue.

I put a system together to play around with Unraid back in 2017. This system has performed great with no issues and would stay on with no crashes at all with only being randomly rebooted a couple of times per year maybe. I recently upgraded from 6.9 to 6.10 and subsequently to 6.12.2. I made 1 other change by replacing the RAM with the same RAM brand and line but higher capacity. Suddenly after upgrading to 6.10 and replacing the RAM it started crashing randomly but typically within 24 hours of startup. I believe it is a C State issue based on the syslog and the know issues. The thing I find puzzling is why it worked fine for 6 years and now suddenly started. I'll attach the syslog I was able to get after one of the crashes just to see if someone else may see a different issue. These entries are what leads me to believe it's the C-State issues. Jul 5 01:49:19 Tower kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0) Jul 5 01:49:19 Tower kernel: ACPI: \_PR_.C000: Found 2 idle states HW Components: CPU: Ryzen 1600 MB: PRIME B350-PLUS BIOS: 6042 I've got a spare 2700X that I think I'm gonna throw in it and see if that resolves the issue. syslog

I had the same issue after updating my credentials in the docker config and then manually in the credentials.conf file within the docker. The file kept getting overwritten with the previous values. For some reason even though we updated the environment variable in the docker configuration it's keeping the old credentials and using those to overwrite the creds in the credentials.conf file. Ensure you have the NordVPN service credentials entered into the docker configuration the go to the docker tab in Unraid and do a force update. That should fix the issue if you haven't resolved it already.