Hey all.

Stability testing my 13600K OC/undervolt. Primarily use my PC for gaming but also occasionally use Handbrake to re-endcode video.

Would large files, extreme, variable, AVX2 for 24 hours be sufficient to test stability, or should I be running other tests/programs?

Also in case the developer is reading, thanks so much for a great utility.

Hello, I have a few questions about OCCT as a stability test. How reliable are these tests? I was testing my GPU overclock using the 3D Adaptive "extreme" test, testing various overclocks. I set +200 on core clock and +1500 on memory clock in MSI Afterburner. Other benchmarks and games were always stable but as soon as I ran the OCCT test it showed me a lot of errors. So I decreased core clock to +150 and left memory clock at +2000 and let it run for another half hour. This time I had no errors. Does this mean that my first overclock despite being stable in games was indeed NOT stable? And does that mean that my second overclock now should be in fact stable as there were no errors?

I mainly game, do art and model with blender on my computer. I want to know do I need to use Extreme with Large Data Set? Should I enable Avx2? I'm going to be running it overnight to test my 6700k OC. I cant find any info on what I should be using and I don't want to degrade the chip.

I need help with stability check for my undervolt r5 7500F People have said to try occt with core cycling method sse and av... Something but the setting I have is unmatched

On cpu tab it has mode and etc but not dataset size setting. on the other hand the cpu+ram tab has one but no snall dataset setting like everyone recommended. only large and medium...

So what should I do? Cpu tab?? Or cpu+ram tab?

For everyone messing around with PBO2 Curve Optimiser to undervolt & OC their CPU's, here is a stability test I have found useful. OCCT using Small Data Set, SSE instructions, 1T. This will find bad offsets usually within seconds, but I would let it run for 5min before considering a setting potentially stable.

Your OCCT settings should look like this: https://ibb.co/56fbrQm

When I was first testing I was trying things like -20 all core offset, and it was passing regular stress tests like OCCT all-core for 30+ minutes. OCCT small 1T would fail instantly. Because the curve optimiser is reducing by more voltage at lower workloads we need a less-heavy stress test to engage those conditions; this seems to do the job quite well. Note that some people currently have issues with OCCT causing WHEA errors so you may need to set your ram to 3200 or lower while using this method to validate your curve offset.

Currently I have my 5600x running at -45,-20,-15,-20,-7,-7, +175mhz, auto scalar. which passes 6min OCCT 1t, but I need to test it a bit more. The -45 is suspiciously high. CPU-Z single core is around 666, cinebench r20 is 614. Stock PPT/EDC/TDC.

If anyone has any other tips for testing/validating curve optimiser OC's let me know.

EDIT: Thanks to everyone pointing out that you should set OCCT affinity to the specific core you want to test. The process should look like:

1. Set a baseline undervolt for your core. You could start at the highest value (30) for completeness.

2. Test cores in sequential order in OCCT by setting its affinity to that core. (Task Manager -> Details -> Affinity). Do that before beginning the test, if it doesn't crash in 3-5min consider that good enough for now.

3. If that core passes, test next core until a failure. Use Task Manager to verify the affinity is working.

4. Upon failure, lower your undervolt and retest until all pass.

For CPU is it pretty much large data set / extreme mod / variable load / and avx2 instruction set? How about thread settings, leave on auto?

For memory its just 100% / avx2 / and leave threads on auto right? Or there is no need for this as the test for CPU with large extreme avx2 should also work for memory errors too?

Title speaks for itself.

My friend gave me an insane deal for a 9900KS. But now I don’t know what settings to use on OCCT anymore since they updated it.

Need the AVX stability so Prime95 is out. Will test on realbench and cinebench after.

Can someone please explain why am I crashing on the CPU test with small dataset with all cores no matter the LLC and voltage?

Started to manually tune my r7 5700x, getting to 4.8GHz, no BSODs, games running, cinebench results (R23) satisfying at around 16500, so once I started decreasing voltage I'm now down to 1.3v drooping to 1.275-1.28v (LLC lv3) and it's passing everything except all core small dataset stress test.. Currently cycling cores with small dataset for 10 mins now, no errors so far. LLC LV2 with 1.325 set voltage gave 1.269 in cinebench but it crashed, 1.3 with llc 3 gives 1.275 and its not crashing.

So am I supposed to make it droop more? Or is it okay to just use small data set for single core and cycle them and use all core for medium/large dataset test?

Set parameters are small/extreme/variable/AVX2.

Motherboard I'm using is ASUS X470 prime pro, cooling the CPU with NH D15

I assume it shutdowns on account of thermals, since I can start the test with 8 threads fixed but once it reports close to 95° it just shuts down.

Is that a realistic workload, if thermals are the only problem and I KNOW I will never hammer the CPU with such a workload in real life, is it fine to ignore that test, or just to test up to a certain amount of cores?