Like others, I’ve used Y-Cruncher (both the full battery, but mainly **VST**, **C17**, and **VT3**) to be effective in finding CPU-RAM-IF errors in my AM5 system.
However, I’ve noticed that C17 tends to have higher computational volatility, i.e. one iteration can have a different value +/- 2% than the previous. When tested, the system is at idle and is otherwise Y-cruncher stable (8hrs+).
I’m aware that Ryzen 7000 has some [error correction](https://twitter.com/Buildzoid1/status/1587811939484577793), and I’m curious if iteration-to-iteration fluctuation is a symptom of that — and that the calculation fluctuation indicates that my system cosmetically appears stable but isn’t really