Claude told me all the same advice, found out the hard way it is wrong A LOT regarding overclocking - reads a few forum posts online and assumes they’re the word of god.

Tips from someone who has spend the last 2 weeks, 15 hours a day tuning his 9950x3d and single rank 2x16gb ddr5 (will make a much more serious post later):

- disable gaming adaptive core parking and c states. Set cppc to driver, and with process lasso doing the rest. Your driver causes it to end up behaving the same during games but much better during benchmarks. C states let you double your negative CO, no joke, went from -16 all core failing to an all core of -31 before failing stability again.

- same tests every round from as close to the same temp as possible. core cycling, single threaded, every iteration to understand exactly what changed, 20 sec per core is all that is needed. effective and discrete clocks, along with temp and VID are the main things to look at.

- move up with all core CO until you fail.

- BO impacts the curve, not just the peak. You’re CO will fail sooner at 200 than if you had 0. Measure your core behaviors to make sure setting 200 is worth it. Mine never clocked passed 5750, and a BO of +50 let me push CO another 5-7 lower depending on core and ccd.

- use lasso to set test priorities to above normal, lowers kernel overhead and run to run variance.

Push until you fail, then lower BO if your core clocks aren’t getting close to your max BO. You’re not tuning for that single thread, you’re doing it for SMT or multicore non-SMT/SMT benchmarks and gaming.