ZenTimings VS corecycler

Really depends from game, can you please link screenshot from https://zentimings.protonrom.com and what games you having low frames with?

Can you post a Zentimings screenshot?

Try going a bit higher on the voltage and seeing it if improves stability further then, if it doesn't you may need to adjust terminations/drive strengths/miscellaneous voltages, posting a screenshot of ZenTimings would make providing suggestions a easier

Also, will help others to give advice if you show the settings with ZenTimings. And list make of ram along with version number (Corsair) or "042" code (GSkill), unless it is just Ballistix.

Also, while you're at it, before anything, download Zen Timings https://zentimings.protonrom.com/ and use the screenshot button and post a reply with an imgur link or wherever is clever with your current settings. It might be telling on it's own and it's super quick.

Please post zentimings.

Download https://zentimings.protonrom.com/ and post a screenshot with your current memory settings. Good chance it's memory/fabric related.

This is one of the issues when running DDR5-6200 but the NB clock doesn't represent UCLK or FCLK which is why forcing the ratio doesn't make a difference. Use ZenTimings to get a better idea of what's going on.

Also in the mean time download Zen timings and post a screenshot to imgur or somewhere with your current memory settings. It could be as simple as your memory doesn't have XMP/DOCP enabled, or maybe it reset because of a power outage or a BIOS update (both things have happened to me).

getting lucky with the binning and undervolting as much as possible (+1 after last stable known value) (tested in multiple days with corecycler using Prime95 and y-cruncher)

Read the developer's statements from GitHub:

What I learned coming over from Intel is that in addition to stressing full loads on the CPU and memory systems for stability testing is that you also need to test bursty light loads as well. Corecycler uses Prime95 (default), Ycruncher, and Aida (you need to download) to test single core stability. I use OCCT & Prime95 to get a rough idea for a stable all core load, then use Corecycler with Ycruncher to test light loads.

Here's a template version of my Excel worksheet I used during my process. It's critical to tracking all your testing. https://we.tl/t-UHg9gnTNaGThe key is to ONLY test 1 core at a time with CoreCycler (https://github.com/sp00n/corecycler) until it has been validated for 12 hours. If it fails the Y-CRUNCHER test (y-cruncher error, hard reboot/freeze, BSOD) under the parameters shown in that sheet, you need to lower the CO setting on that core by 1-2 and test again until it passes for 12 hours.You want to also make sure to keep an eye on Windows Event Viewer to see if the core you are testing is producing any WHEA errors as well. That will alsocount as a FAILED validation run, and you'll need to lower it 1-2 and restart testing in Y-Cruncher again.Once it's passed for 12 hours, mark that core/line green on the sheet, 0 it out again in BIOS, and move onto the next one.Here's my CoreCycler config file. It's already setup to start at Core 0, 720m, y-cruncher, 2 threads, with all the correct testsselected. https://we.tl/t-gK3fc40BR1

You can test it extensively with corecycler ( https://github.com/sp00n/corecycler) with y-cruncher set as the stress tester.

Not all cores are equal. You could try Curve optimiser per core, test with Corecycler. Someone made an automated tool for it. Link