CTR 2.1 RC4 - announce

Yuri Bubliy

Did you turn on the SAFE Diagnostic? Also, changing the temperature of the processor can radically affect the result.

Tom DePaolo

The RC3 diagnostic I just ran gave a PX high safe result 4975, then the fast result was 4925. Any idea why that would happen?

Yuri Bubliy

Zen 2 is a different architecture and this architecture does not have the sensors that I use for Zen 3. I am not stopping the development of the PX for Zen 2, but the possibilities and functionality are unfortunately limited.

Yuri Bubliy

Solved in RC4 ;)

Please make sure all the profiles are restored after the sleep mode. Currently none are restored for me in 2.1 RC3 (no hybrid mode, tried to activate and save under P2 and P1). I have to re-apply profiles several times per day or restart the app. It's really annoying. Thanks!

Riwwelorsch

If you invest a bit time in manual tweaking and finding stable profiles you will discover that you at least can match CO performance. But with much lower voltage / heat / power consumption.

Xdrqgol

With 5950x / dark hero ( followed the guide , bios preparation ( not even tweaking ram) CTR runs, diagnostic is done , i get platinum sample , but the system is not stable. Maybe I need to spend more time in tweaking it but , i prefer for now to use BIOS OC/ CO as i get much better performance and stability. I will continue support but for me, since last month stability and performance decreased a lot with CTR. After your public release, the beta versions were more stable and worked as intended to a certain extent. On all forums ( overclok etc ) everyone speaks about CTR but no one seems ti believe that it can be better than PBO + CO ... i really care about stability and for me to spend extra time as in BiOS for CTR is not really making sense. Will try it again when it will become more mature!

Ricky Campbell

so no zen 2 why so ?

Henry Curtis Pelgrift

I think I’ll wait for AGESA 1.2.0.2 next month... 😅

PewWORKS TV

I can confirm new AGESA 1.2.0.1 Beta patch A ("USB fix" BIOS) is not compatible with CTR RC3, computer get black screen and restart when run diagnostic, I downgraded to normal AGESA 1.2.0.1 and RC3 works fine again, using an ASUS x570-E. Also I tried replace CB20 files for CB23 and CTR is not getting the scores from R23, I guess this is normal but I wanted try Cinebench R23 anyways.

Henry Curtis Pelgrift

Yeah, is that something for when you have Radeon 6000 series GPUs? Cuz I remember rage mode was a built-in overclock. Not that anyone has 6000 series GPUs....

Rage idle state? What is it ?

Yuri Bubliy

I'm very curious if Patch A works with CTR 2.1 RC3.

Yuri Bubliy

Yes, it's scheduled for this month.

Henry Curtis Pelgrift

Woot! Big changes! And Gigabyte has just implemented 1.2.0.1 Patch A, so I can download that! 😬 Also, it’ll be nice to have this utilise my AORUS Master’s fancy VRMs.

PewWORKS TV

Just try tweak 3600 CL14 or 3800 CL16, you can push DRAM voltage until 1.5v, SOC 1.15v-1.2v, VDDG and VDDP 1.05v max if you need it, GDM always on. It's very hard tweak the RAM with GDM off, mostly of people only get it stable until 3200 with GDM off. Use also DRAM calculator values even if it's outdated, it works. more Mhz have higher priority until 3800-4000, soo 3800 CL16 will be better than 3600 CL14.

Ryan A

2.1RC3 was a huge improvement. My pc was benchmarked for gaming and cane back without outstanding single and multicore performance using safe diag( I typically tested as Plat/gold). I'm with you to the end brotha. The one thing I need to work on is my 4x 8gb gskill trident 3600CL15 mhz is on its XMP cert profile. GDM brings it to 16CL. Turn GDM off and I bsod. Dram calc tends to aim for 14CL, should I go for the CL14 Latency or maybe up the MHZ. Calc says I can do up to 4kmhz I could give another try with this new revision. Any help is appreciated

Nice!

This is huge! I’m excited!!

Andrea Squadrani

Will be PX profile for Zen 2 ready in this new release? Because in RC3 release notes you wrote ''Zen 2 and PX are under development. I advise you to refrain from the experiments'' so i'm still keeping it deactivated for safety.