Mad Man with a Blue Box

It seems that a setting in bios something to do with overclocking the memory to full spec, was set and when unset the memory test stopped giving errors and the login worked again. My issue now is that a Windows 10 VM I have running in Unraid gets some unknown error every so often. Usually when I'm not around. Causing the VM to shut off.

I'm away from the server right now but will try that when I get home and see what that says and report back. It's been working fine for a few years now. All top quality new stuff when purchased. And I'm super careful when handling the internal component, no static, etc., so don't think I could have damaged anything during the replacement. But since it did only start happening after opening it up and tinkering inside, that has to be a possibility even if a slim one.

Thanks. Totally English here, checked the password in plain text view and it is typing correctly.

So, I shut down the server for several minutes while replacing the power supply. Just upgrading it to a more powerful higher quality model. Upon turning it back on and logging into unraid everything works just fine. As usual at the bottom of the main tab it says missing key and waits for me to type in my password to decrypt the array. However this time it comes up with wrong key every time I try to start the array. I have triple checked my password and it is 100% accurate and I have been using it for quite a while without any issues even earlier that day. What could have happened and how do I fix it without losing access to all my stuff on the array.