ThatRustyBust

Well, the bad module doesn't seem to be detect no matter what I try, so...

Already tried reseating and changing slots, clearing CMOS didn't seem to help either

Also that whoever designed my BIOS thought SPD write protection wasn't a necessary setting to include.

I already disabled EXPO and tried to boot so I'm not sure what else I could do jn the BIOS that's RAM-related, but I'll see if it boots on a default bios.

Yep, I did. It didn't work though, which I explained in my post

Apart from normal system updates (which, on Linux, shouldn't affect much as I don't recall an update related to SPD occurring, unless a kernel update caused it), I don't recall doing anything recently. A few days ago I installed OpenRGB, then the next day I happened to notice while playing a game that RAM was out of 16 GB instead of 32 GB. I'd been using these sticks for about half a year without issue- I don't know if they can be RMA'd. If it comes to buying new RAM, I guess I'll just have to.

I'd prefer not to disclose for the same reason people don't disclose what company they were working at at the time.

Nope.

Yeah, I saw a post in this sub about someone's printer not turning on because the power was out

Nope, I just happened to be on the Discord when the user asked for help.

Exactly. Another time, another user had a similar issue, terminal popped up for a second then closed and I instructed them to run from terminal and we were able to figure out what the issue was. I later ended up adding a "pause" command to the Windows batch script, so the terminal wouldn't instantly close if there was an error.