Definitely, I had also done a lot of investigation and assumed that when I isolated the problem to the RAM there was almost nothing more I could do expect cry and wait for the inevitable torturous moment I’d have to open my wallet amid sky high prices.
The server has now been running non-stop without an issue for 30 days, so I assume the problem was fixed by the suggestion!
It feels like history is repeating itself. The movie Amsterdam made me aware of the Business Plot of 1933 and I was surprised about how much it mirrors the political landscape in the US today.
Update, kernel panic happened today, so I updated the BIOS settings:
All the initial values were Auto values. I’ll let it sit for at least a month with no reboots before calling it fixed. I’ll set a reminder
I’ll try to remember to update you in 1-2 months then!
I’ll try that next time it dies, see if it helps
Only thing I wish for Christmas is to be able to replace the RAM and mobo in one of my servers. It is failing with a kernel panic about once a week and it is an old DDR3 platform I planned to upgrade back in January. I have isolated the issue to a hardware fault but left without a solution…
The trick is to find something that uniquely identifies the cancer cells and tell the immune system to attack that. If it says “attack everyone in a red shirt” but some normal liver cells have a red shirt, then you got a problem. But if only the cancer cells are wearing khakis, then you just identify that. It’s the same principle as normal vaccines except that for cancers there’s no single identifying trait for all people getting the cancer (even if it’s the same type). For a virus it has the exact same trait across everyone who catches it until the virus itself mutates (which is why the flu gets a new vaccine each year to fight the most common mutation).