never heard of that happening back in the day? it was all we ever used to stress test for heat and stability upto the q6600 era.
so what actually does genuinely prove its stable these days now as I'm at a loss how something stressing the death past actual usage doesn't prove something is stable and how a Web browser doing bugger all in comparison could stress it?
https://www.ocbase.com/ This is a good piece of a software for stability testing.
To make it easy to identify where instability might sit, I generally, do the following:
- OC my ram and test and tune that with a stock cpu. To keep it simple, use the memtest in occt along with the large/avx2/normal test. 30mins for small changes, 1hr for when locking in something solid
- Then once my ram is good, I focus on the CPU aspects and use a combination of Y-Cruncher and large/avx2/extreme in occt. For YC, I'll run the following when it loads up: 0,1,7 and do about 5 cycles of that before doing an on hour of occt
http://www.numberworld.org/y-cruncher/
The above has proven to be bulletproof for me on intel and amd: z390, z690, b550 and about 5 builds total between those platforms
A big gotcha on AMD. Clock stretching on AMD is very common and greatly exaggerated by undervolting. Clock stretching means what your cpu is running otherwise knows as "effective clock" is much slower than what you see in overlays which is generally "reported clocks."
Luckily hwinfo64
https://www.hwinfo.com/download/ has a seperate section under CPU for showing effective clocks. *That's* what you need to focus on for AMD. Intel doesn't really have these issue as we don't undervolt there and boost works differently.