This is a slippery slope towards CPUs which are only warranted to run certain approved apps. Overclocking aside, I'd consider a CPU broken if it can't run any sequence of instructions 24/7 without damage at the stock speed and voltage.
Besides, Prime95 isn't what I'd consider a pathological case anyway --- FFTs are common in scientific computing and signal processing, and having a CPU continuously perform them is not at all an unusual workload.
It somewhat reminds me of https://news.ycombinator.com/item?id=7205759
AVX has been on a separate clock/offset for a while now, and many OC'ing motherboards will let you tweak it.
Given how much power AVX consumes I wouldn't be surprised if throttling it even let you clock the rest of the core higher.
> run prime95 small FFTs albeit at 90C for 24 hours with no issues then your OC should as well
That's nice in theory but in practice if it's gonna crash it's gonna do it quick. I doubt many CPUs are suddenly erroring out for the first time at 23 hours. So why not just test for an hour and call it good? An hour of super abnormally high stress is more than enough to validate it for standard usage in my opinion. More than OK at 30 minutes too. Usually fails within the first 5 seconds, if you make it to 1 min then you have a very solid chance of making it the whole way. 30-60m is plenty.
If your data assurance requirements exceed one "proof test" shot[0], so to speak, then you have no business using overclocked CPUs at all. Prime95 SmallFFT is way way more stress than you would ever put a CPU under in any real-world load, and like an overpressured proof shot it's not really the best thing in the world for the processor to do this nonstop. Electromigration is a thing that exists.
Wait, SmallFFT? Isn't that the test that focuses heavily on CPU and very little on the memory?
Since this news is about memory timings/overclocking, I'd rather put much more focus on tools like Memtest86+, running that for a few hours to be sure that it touches all the addressable regions and uses various access patterns.
Whatever test you do, you want to exercise all the memory, or else you'll end up with a computer that always seems fine after boot, but accumulates errors and crashes based on uptime and how much concurrent work you throw at it.
Is it because the question is not whether or not a particular bit of RAM is damaged and rather whether or not the overclock to the communications bus between CPU and RAM is affected?
Obviously you want to focus your testing on whatever subsystem you're trying to OC. I was just giving generic advice on overclocking. There is pretty broad consensus that Prime95 is a good stability test for CPUs.
Someone also suggested Intel Burn Test as a test that might catch some instabilities that Prime95 misses in a reply and then deleted it for some reason (why?).
In particular though, it's not just the memory subsystem you're overclocking here, you're really overclocking the interconnect as well. It will have its own "silicon lottery" and a particular point of instability, in addition to your individual memory kit's own stability characteristics. There are a lot of moving parts here.
I do wonder how much of this is getting the memory controller stable versus getting the interconnect stable. It seems possible they may have knobs they can twiddle on the interconnect as well.
[Serious question here:] I wonder if Prime95 or burn-test type tools would stress the interconnect with enough cross-core communication to be worth running.
The combination of instructions it used meant that even if, under sustained 100% CPU load with a normal benchmark, your cooling solution was sufficient, within 30 seconds the CPU would hit 100° and activate it's thermal protection before a shutdown.
I went through 3 water cooling setups and numerous thermal paste reapplications before I realized, since I was driving the CPU hard (4690k at 4.9Ghz with a high overvoltage I recall being considered at the limit for non-LN2 setups, 1.4?) and thought that cooling was the issue
Do they have anything in their contracts telling you not to do that?
You mean 'really sensitive'. 'real' is the adjective form - 'really' is the adverb submodifier form, which is the one you want in this case.
Beyond that, just pick your burner application of choice and let it run for an hour while you go watch a movie. The rest are all kinda interchangeable as far as I'm concerned. Aida64 maybe?
(one note: I would not leave Prime95 running for prolonged periods of time. Modern CPUs are not designed for a program that is so small it fits into uop cache and runs AVX nonstop. With a heavy overclock it can pull 300W+ (potentially above 400W) on HEDT processors and OEMs like Asus have warned that it may cause damage[0]. Electromigration seems like a likely culprit meaning time is a key factor. Running Prime95 for like a half hour is fine and a great stability test, but 24H+ runs are extremely unnecessary and potentially damaging.)
[0] https://rog.asus.com/articles/overclocking/rog-overclocking-...
(Note that while this article is regarding Haswell-E, the same logic really applies to Broadwell-E as well as Ryzen 5 and 7. Running a processor at triple its nominal TDP nonstop for a prolonged period with most of that power going though a few specific execution units simply cannot be healthy for it.)