CTR 2.1 RC5 (ver.17) - ready for download!
Added 2021-04-28 10:46:50 +0000 UTCIt was one of the most difficult months for me. The development of the auto-boost analog proved that a unique technology is extremely difficult to recreate quickly. Next month is the calibration of the dynamic profiles. Also next month you will see dynamic voltage(!) for the P1 profile (you will be able to adjust in which VID range the P1 will work) and increased frequencies(!) for the non-AVX load. At this point, a mechanism is already being developed to effectively detect the type of load. This means that the light load has more frequency margin than AVX. More flexibility, more stability.
Perhaps you have seen the announcement of the free CTR 2.1 to the public (in my Twitter) which will take place next week. The key difference from early access remains the dynamic profiles, they remain exclusive for early access.
As for CTR PRO. This is a professional version CTR which will have up to 9 profiles for Zen 3 AM4 and up to 17 profiles for Zen 3 sTRX (all profiles are automatically created). First of all this will allow maximum performance for any load. Also OB (aka CO) for each profile and of course dynamic mode is provided. It is too early to say when this OC-moster will be released, but tentatively it will be the end of June. At the end of May, I plan to show what it will look like.
Thank you for your patience and support. Low bow, 1usmus.
_______
Cinebench R20 included. Before you use the new smart diagnostic, make sure you have curve disabled in the BIOS and DRAM OC must be stable. CPU LLC has an incredible impact on stability. At the end of the guide there is some more information about CTR 2.1 RC5.
_______
The program is in a 7-ZIP archive. Download the archiver
.NET Framework to 4.8. Download
_______
What's new?
- Fixed Phoenix (there will be no more reports about the platinum sample).
- Improved performance of PX subprofiles.
- The throttle system now has a timeout of only 105ms. Allows the processor to return to normal operation faster after catch peak PPT/TEMP/TDC/EDC.
- Smoothing the cpu usage peaks to reduce the number of profile switching.
- For dynamic profiles, the tolerances of frequency changes have been changed. Now the frequency is more stable and should not "rock the boat".
- Independent OB CALCULATION button (PROFILES tab).
- PCI mutex hold time increased to 60ms (to avoid premature unlocking).
- Small changes in OB templates and creating profiles during diagnostics.
- Improved accuracy of OB testing (now four tests instead of one).
- Fixed exception (rare bug) when closing the application.
- Dynamic PX MID profile now works.
- Doubled PX holding time.
- Improved stability for a profile with suboptimal load (non CPPC).
- Automatically save the state of the switches (CTR HYBRID OC / Autoload profile(s)).
- Fixed incorrect VID TEL recording in TEMP.ini and TEMP_BACKUP.ini.
- Improved CTR HYBRID OC support for CPU with SMT disabled.
- Other minor bug fixes.
_______
Special thanks to @Riwwelorsch, @Ann Martiné, @ACE, @arcanazen, @DayDreamer, @Gadfly, @rizlah , @&&Devin, @Bloax , @wanderinarcheologist and @Stattik for help with development and testing RC5.
Comments
Core boost performance refers to the cpu's ability to boost at all. That stays on unless doing an all core. "performance boost overdrive", however, needs to be disabled, because this feature is what CTR more effectively manages and in a different way. For SOC, best bet is experiment once you have CTR working. Start with 1.12 to 1.15v
Krewd
2021-05-01 09:15:10 +0000 UTCHmm... I think it's under the patreon settings, where you can connect patreon and discord. Take a look at the settings
Riwwelorsch
2021-04-30 14:12:59 +0000 UTCPersonally I use 1.2V on SOC for stability reasons (I Have FLCK on 1900Mhz)
Gufur
2021-04-30 10:14:31 +0000 UTCHey Guys, I got a question for you. It's about the guide(s) in the "Big Guide" it says "Core Performance Boost" on Auto (Asus Hero Board) and in the RC5 Manual it says "Core boost performance" Enable. Are we talking about the same thing here or is "Core boost performance (CBP)" called something different on asus boards? second question: VDDSOC is supposed to be between 1.15 and 1.20 how can I find out whats best? what do you use? BTW my system specs are the following: 5950x x570 asus hero(non wifi) rtx3090, 32gb gskill neo 3600 cl16 somehow I cant get my system to be stable with ctr. hopefully you guys can help me out... maybe even with some bios settings that helped you Thanks!
darokka
2021-04-30 09:06:57 +0000 UTCI would join but my time is very limited - i will and get in touch with you - maybe we can improve something. Have to get to know how I join the discord because I have no clue 😅
Xdrqgol
2021-04-30 08:20:18 +0000 UTCAnyway you should join on discord. To help with issues is way more easier
Riwwelorsch
2021-04-30 07:20:00 +0000 UTCCan only speak for myself, but Vers. 17 is more stable than 16. Aida Benchmark does not reboot anymore. 4950 Clock on 5900x without problems!
Gufur
2021-04-30 07:17:38 +0000 UTCDid you manually tweaked the OB values? Especially PX has a margin. Its strange cause I and many others can't beat CTR with CO. The gap is quite big
Riwwelorsch
2021-04-30 07:16:42 +0000 UTCUnfortunately we regress in terms of stability and even performance . My bios settings are still performing better in all workloads and are more stable. My 5900x usually runs 4975 /5025mhz effective clock on 3 cores , with CTR i am pushed back to 4875mhz... it needs lot of more work and probably testing....
Xdrqgol
2021-04-30 06:50:28 +0000 UTCYeah I keep getting reboots after using my PC for about 20 mins not sure what it could be at this point.
Brandon A. Martinez
2021-04-30 02:42:34 +0000 UTCTo those in this reply having issues, I seem to have resolved mine - took a bit of a switch in approach as to my values from previous versions of CTR. Examples are for a 5950x. - Run the Calculate OB function a few times - first run gave me values that were too high, causing instability. - Once you have a consistent result, calculate your profiles manually. Eg, I entered the voltage I'm happy with on for my P1 profile (1125) and hit calculate profile. - Stick with the default CCX1/2 values it provides, and from there, slowly bump your OB if your processor can handle it. Eg - I know I'm stable at 4.4ghz on CCX1 at this voltage, so I raised the OB to 50. You'll hit a point where raising the OB has no effect on the clock speed, so that's your cue to stop. - Rinse and repeat for each profile. Taking this approach I have comparable P1 and P2 results to my previous, but the instability has vanished.
Jake Mormile
2021-04-30 01:35:34 +0000 UTCThere is clearly something wrong with this build. 1st I tried a diagnostic run with everything set in bios and RAM on 2666Mhz went ok but got random reboots on idle. ok followed Yuri's advice to set the PX OB to the same value as P1...that worked no more reboots. CB20 temps on under 70c(66-68c) 2nd i went on and set my ram to 3600Mhz and tested for stability, everyting passed so i did a new diagnostic run but that didn't even pass because of PPT limit reached...cleared the settings and closed and did a new diagnostic run, this time it passed but when it got to stress testing i got a warnign "WARNIGN weak cooling solution....Alternative diagnostic started" WTF? but then it went on forever pushing the CPU VID mV under 900mV for over 1 hour...i finally gave up and stoped the diagnostic run... ^^ sorry but i don't really feel comfortable running this version of CTR it's doing to much funky stuff...any advice?
zeroblu3
2021-04-29 23:09:10 +0000 UTCI had the exact same problem back in version 15 and now in version 17 and nobody talks about this but Autostart with OS and start with tray is not working properly, also activation states are not saving after restart but I solved it this way: 1) after you have everything tuned and activated click "EXIT" and start CTR again, this way configuration will save. 2) for the start with tray in every restart you need add a CTR shortcut to Windows startup folder. Def this is not working and Yuri need fix this. Also Diagnostic is not working fine after autoreboot when CTR is calculating OB values, I need calculate every profile and OB separate. Tested in 2 latest BIOS 1.2.0.1 Patch A and 1.2.0.2, x570-E mobo.
PewWORKS TV
2021-04-29 21:03:07 +0000 UTChttps://gyazo.com/a58d3ff499c793c97eb5c76f67fae76d This is what I got today, after I started my PC. CTR is stuck there and it won't even let me clear the config nor does it react to anything else than ALT+F4 . Creating profiles worked fine yesterday but after dialing in everything as the Instructions told me, I was pretty unpleased when I found out, that gaming load (~10-30%) is ignored and the Processor is kept in "idle" at 3,8GHz, only when it sometimes (in loadingscreens) hits the designated load for P2, then it activates P2 and immediately goes back to idle. How can I tell CTR to hold the PX profile while gaming but STAY at 3,8GHz when I'm just browsing.
Crophixx
2021-04-29 13:24:59 +0000 UTC@STGG Go back to the Tuner tab and scroll all the way up in the log window. See if it says " OS does not see CPPC core tags!" This causes the program to not apply your profiles. Restart and it should be fine. If the problem still persists, Yuri might be able to help.
chrom
2021-04-29 10:15:54 +0000 UTCIt happens with both +100 and +125.
Jake Mormile
2021-04-29 09:22:12 +0000 UTCI already pressed "CLEAR CONFIG & CLOSE" but it didn't work out, so I deleted the whole thing from the beginning and it was solved. Just one thing I'm curious about is that the values of MAX PPT, EDC, and TDC are still initialized, is there any problem?(I was using 285, 195, 225).
STGG
2021-04-29 09:20:53 +0000 UTCI guess the settings of the previous CTR have not been removed. Before using the new version - delete the past configurations with "CLEAR CONFIG & CLOSE" button
Yuri Bubliy
2021-04-29 09:05:58 +0000 UTCI finished all the settings. But there are 3 problems when rebooting the computer. 1. CTR program does not start with tray. 2. The values of MAX PPT, EDC, TDC and the VID values of p1, p2, px are initialized(1050, 1150, 1375, 1375, 1350). 3. CTR HYBRID OC, Autoload profiles and all profiles are disabled. For your information, I've been using it since ctr 2.0 and this is the first time I've experienced this.
STGG
2021-04-29 09:01:19 +0000 UTC@Jake hich PX OB LIMIT do you use?
Yuri Bubliy
2021-04-29 08:44:51 +0000 UTCSame issue here, everything testing well but idle reboots.
Jake Mormile
2021-04-29 05:58:43 +0000 UTCI'll try this and let you know...but like i said the reboots mostly happen when the CPU is in Idle profile.
zeroblu3
2021-04-29 04:32:28 +0000 UTCSlight adjustment on that, the AVX PX preset works perfectly fine and I was able to push the OB limit from +125 to +200 without issues (4950mhz max for PX low), just seems like my 5800x doesn't like 5ghz all that much, at least in Cinebench
Jamie Godwell
2021-04-29 00:26:31 +0000 UTCThis is the most stable version of CTR for my build yet. (5800x GByte B550 Vision 32G@3800mhz mem / 1900 fabric) Everything has "just worked". This is the only time I've been able to run Diag & Tune P1 / P2 and then successfully complete every test of Cinebench for 1/2/4/6/8/16t without a black screen reboot. Every previous version I've had to tweak settings down to get stable even just running Cinebench repeatedly. Now I'm sitting stable on all settings determined by diag/tune in my testing so far. Great work Yuri, I'm feeling much happier about my support of CTR with this version!
Jamie Godwell
2021-04-28 23:46:55 +0000 UTCMy "results" section is completely empty too. Tried clearing config, delete and reinstall but to no avail
Ywc
2021-04-28 21:24:18 +0000 UTCYour solution worked for me.
Erik Storli
2021-04-28 20:52:22 +0000 UTCYou're doing fine, you don't need to touch the LLC.
Yuri Bubliy
2021-04-28 18:57:32 +0000 UTCThe "Results" section is completely empty (no R20 scores/charts at all), except Frequency per CCX - DEFAULT, and user/system info is filled.
DeeJay
2021-04-28 18:38:04 +0000 UTCI've got a question about VDROOP. I set LLC before doing anything else with CTR and was quite happy with VDROOP of 2.11 %. Just used CTR to read values of TEL and VID during Cinebench multi. Then I run the diagnostic and in the end it said VID 1105 and TEL 1092 (that is VDROOP 1,19%). Shall I fiddle with LLC again after activating the profiles, or just leave it?
Vecchio
2021-04-28 17:59:27 +0000 UTCSounds good. I have zero issues so far so I will keep using this one :)
Gabriel
2021-04-28 17:40:51 +0000 UTCMarco and Tim, did you try what it says on page 13 (note 3)?
Yuri Bubliy
2021-04-28 17:35:43 +0000 UTC1. The current version of CTR has dynamic profiles. It will be improved next month. PRO - is more control over the processor, more settings and more possibilities. 2. I'm planning the next model. Free version without dynamic profiles. A version with dynamic profiles, but with a reduced price and a professional version - the current plan. I plan to reduce the cost of early access over time. All changes will happen at the end of next month.
Yuri Bubliy
2021-04-28 17:34:23 +0000 UTC"graph not working" what do you mean?
Yuri Bubliy
2021-04-28 17:29:56 +0000 UTCI think this update can be skipped, if all fine :)
Yuri Bubliy
2021-04-28 17:29:02 +0000 UTCTwo CTRs is conflict creation. If you are doing well - I think this update can be skipped.
Yuri Bubliy
2021-04-28 17:28:26 +0000 UTCSame Problem with my setup
Tim Trahms
2021-04-28 16:48:16 +0000 UTCDiagnostic works now without problems but i get random reboots when my pc is idle with the default profiles after Diagnostic with this release. I guess i'll wait for a more stable release and use RC4 for now. Let me know if i can help with testing.
zeroblu3
2021-04-28 14:45:50 +0000 UTCQuestions on the 2.1 Free vs Pro editions: 1. Dynamic Profiles means profiles and voltages will be in Pro only? 2. What will be the business model for the latter - anticipated cost and do Patreons get some discount?
DeeJay
2021-04-28 14:40:31 +0000 UTCv17 for me works like v16 did - besides good performance and stability, this also includes the graph not working (it has neither a status quo nor a tuned value, and so no stats can be sent), forgot to bring up for v16. Anything I can do?
DeeJay
2021-04-28 14:38:21 +0000 UTCi have the previous RC5 running pretty nicely. I'm wondering if i should try this... What do you think Yuri? should i make the upgrade and use the Version 17 instead?
84wayz
2021-04-28 13:55:17 +0000 UTCI have my previous RC5 version performing great so far. If I wanted to test this one, will interfere with my other version or can I have both without issues as long as only one is running at a time?
Gabriel
2021-04-28 13:14:44 +0000 UTCSeems normal now
Korkut KAYA
2021-04-28 12:54:50 +0000 UTCCorrection. After reboot, I could have disbaled the profiles and messages are stopped.Reactivating and rebooting.
Korkut KAYA
2021-04-28 12:49:04 +0000 UTCIn this case, deactivate all profiles and then activate them.
Yuri Bubliy
2021-04-28 12:48:24 +0000 UTCCPPC labeles changes and not zero. Rebooted the PC but the issue is still there.
Korkut KAYA
2021-04-28 12:47:15 +0000 UTCNear core 0 0 0 or 121 174 etc.?
Yuri Bubliy
2021-04-28 12:45:47 +0000 UTCMonitoring in the app is ok. I see all the readings. how should I check CPPC labels?
Korkut KAYA
2021-04-28 12:45:01 +0000 UTCCheck if monitoring is working and if CPPC labels are present. Sometimes you just need to reboot the system.
Yuri Bubliy
2021-04-28 12:41:19 +0000 UTCI have a similar problem with LLC on B550 I strix. I am forced to use LLC2(instead LLC4). Try other modes.
Yuri Bubliy
2021-04-28 12:38:59 +0000 UTCAnother issue report from me. After profiles are set and activated, I have rebooted the PC. then restarted CTR but I continuously get the following messages. Any button in the app. are grayed out. P1 PROFILE restored after sleep! P2 PROFILE restored after sleep! P1 PROFILE restored after sleep! P2 PROFILE restored after sleep! P1 PROFILE restored after sleep! P2 PROFILE restored after sleep!
Korkut KAYA
2021-04-28 12:38:33 +0000 UTCmay the motherboard be damaged?
Sisay
2021-04-28 12:36:50 +0000 UTCYour LLC does not work correctly, you need to find the mode with the lowest vdroop (2% is optimal). I'm very surprised that LLC3 doesn't work as it should...
Yuri Bubliy
2021-04-28 12:32:12 +0000 UTCyeah i corrected it was smallest. In the rc4 version, the difference between the calculation and the truth is about 25-50mhz in this version the calculation is wrong about 100mhz. I do all tests on llc2 (on llc3 vdrop is about 2.5% but the ctr is completely lost and shows the other way around - this time it shows the calculation lower by about 50-75 mhz than can be set to smallest) Asus strix-e x570 - llc2, 130%, power phase extreme "If it's Zen 3, then the processor rating is lower than bronze" in llc3 with vdrop 2,5% in smallest I have a stable 4350/4225 (1100 vid) - calculation in ctr show CCX # 1: 4250MHz CCX # 2: 4150MHz Total anomaly :(
Sisay
2021-04-28 12:28:19 +0000 UTCLet's figure it out. What motherboard and what VRM settings are you using
Yuri Bubliy
2021-04-28 11:52:44 +0000 UTCYou do your best Yuri thats counts the most for me 👍
Michael Platz
2021-04-28 11:48:19 +0000 UTCYou have indicated the frequency that is typical for Zen 2 silicon or for the Small test. Small not supported, please read new manual. Don't try to destroy the processor, this preset was created for just that. Small creates an incredible load. There are no real applications with this load level. If it's Zen 3, then the processor rating is lower than bronze. Perhaps the CPU LLC is not correctly.
Yuri Bubliy
2021-04-28 11:38:16 +0000 UTCSomething is wrong, p1 profile calculate is 4350/4275 and stable in smallest fftprime is only 4250/4150
Sisay
2021-04-28 11:37:31 +0000 UTC
