CTR 2.1 RC4 + hotfix (HYBRID OC crash fix)
Added 2021-04-02 18:45:22 +0000 UTCCinebench R20 included. Before you use the new smart diagnostic, make sure you have curve disabled in the BIOS and DRAM OC must be stable. The rest of the settings are not that critical.
_______
The program is in a 7-ZIP archive. Download the archiver.
.NET Framework to 4.8. Download.
_______
What's new?
- HYBRID OC improved stability (hotfix!)
- AGESA 1.2.0.1 and newer fully supported.
- PX PROFILE for Zen 2 fully supported.
- New! Profiler for Zen 2 and Zen 3 (5 levels; 0 - safe values , 4 - extreme values). Allows each user to find the most stable values.
- Recovery after sleep. Both for HYBRID OC and manual profiles. Improvements and bug fixes.
- New! TO TRAY - individual button. The user can choose how he wants to minimize CTR.
- New! CALCULATE button for PX, P2 and P1. If you need to recalculate the profile, you don't need to restart the diagnostics (Zen 3 and Renoir).
- New! RAGE IDLE STATE - HYBRID OC uses P2 instead of IDLE profile. Allows to improve performance in a number of programs which do not use CPPC (for Zen 2 and Zen 3).
- Improve the stability and safety of diagnostic processes.
- PX LOW now reacts more aggressively to suboptimal load (for programs that do not use CPPC).
- New! The log records information about all profiles, as well as about all steps of creating PX/P2/P1 profiles.Easier control and debugging.
- Test #5 , which creates P1 during diagnostics/calculation, now uses Prime95 instead of Cinebench R20. Now the user will always get an adequate result.
- P1 / P2 recalculation crash fix.
- Fixed P2 sticking (HYDRID OC).
- Numerous minor bug fixes.
_______
My recommendations for working with CTR 2.1 RC4 (easy guide)
1. BIOS. CPU LLC is at your discretion (VRM settings). All other settings should be the default.
2. Stable OC DRAM (memory must be stable and overclocked).
2. Click Diagnostic.
3. (Zen 3 or Renoir) Activate the received profiles and save all activated profiles.
3. (Zen 2) Copy the P2/P1 settings from previous versions of CTR or perform tuning. Activate the received profiles and save all activated profiles.
4. Share the results :)
_______
CTR 2.1 RC5 INFO
The next major update - dynamic profiles(!) . CTR will be able to increase or decrease frequency of each profile in real time, depending on load. So you will get extra stability in heavy loads and extra frequency in games. This feature will unfortunately only be available for Zen 3 processors and Renoir.
Work will also continue on improving PX for Zen 2 and Zen 3. Release date - mid April. Also at the beginning of the month I will demonstrate how this technology works.
_______
Special thanks to @Riwwelorsch, @Ann Martiné, @ACE, @arcanazen, @DayDreamer, @Gadfly, @rizlah and @Vi for help with development and testing RC4.
Comments
Hi Yuri, first of all thanks for your great work! I have a problem with RC4 atm. A few seconds after I start the tuning process I always get a WHEA error. I would really like to fix. Please let me know what kind of information you need from. PS: and of course I did everything acording to your guide
darokka
2021-04-18 08:02:51 +0000 UTCI haven't seen much talk about bios settings from fmax enhancer and asus performance enhancement ( on Asus Boards ofc) how should they ideally be set to ?
Danut Rotaru
2021-04-16 05:43:14 +0000 UTCpx profile one core = 4950. Score in Cinebench = 622 pts it is lower than default (only 4750-4800) why ?
Sisay
2021-04-14 22:12:54 +0000 UTCHello, So i'v joined the patreon and downl.oaded CTR RC4 + hotfix. My memory is 32 GB Gskill Trident 3600 MHZ 16-19-19-39-58 with 5900X @ Mag X570 Tomahawk. No matter what i try, CTR always crashes during the diagnostic at stress test 2 during manual overclock part, example Manual overclocking mode enabled 13:56:03: Saving temporary settings... 13:56:07: CCX1 (158): 4375 MHz, 1187 mV 13:56:07: CCX2 (133): 4375 MHz, 1187 mV 13:56:07: Step# 1. Diagnostic VID: 1187 mV 13:56:08: Stress test 1 started... The ram has been stablily tested as recommended in the guide, on XMP as well as Manual settings, seems fine. Anything else i can do? Love the program BTW. All the bios settings have been set as recommended in the guide, LLC 5, Vdroop between 1,7 and 3,2 % Help would be much appreciated.
Sander Peetoom
2021-04-13 12:13:14 +0000 UTCHey First of all, a big thank you for this brilliant programme. As soon as the diagnosis has run through and I click on Tune with the P1, the tuning starts and after 2 seconds the pc starts at. Exactly the same happens with the recommended values of p2. What is the reason for this?
KvN Rave
2021-04-10 15:50:41 +0000 UTCNope,it’s very very bad for CPU
Yuri Bubliy
2021-04-08 05:39:29 +0000 UTCCan set max temperature over 90℃?
newlibrarian
2021-04-08 05:39:01 +0000 UTCWhen I try to enter into the diagnostic R20 isn’t recognised and I get sent to Maxon website to down;old r23
BlackHat
2021-04-07 06:56:10 +0000 UTCI passed stability test but a shutdown occured while using the computer . I checked to find out which core crashed in the event viewer. The problem is which profile it is that I need to reduce the frequency.(using hybrid-oc) So will you consider in the next update letting it leave the log which profile it was before crashed?
STGG
2021-04-05 14:39:23 +0000 UTCI love the new build! With more new features added in this one update than we have gotten in the last few combined this one really shines. I don't understand why none of the builds recommend a ccx1 delta over 25mhz. Diagnostic results always give me a silver sample with a recommend 25 and a max theoretical of 50. I know the best performance for my chip comes at 75. My chip has the following cppc tags. CCX1-177,164,181,181,168,173 CCX2-147,160,139,152,143,156.
Tom DePaolo
2021-04-05 12:17:29 +0000 UTC@Yuri - this has been definitely the better of the releases so far. it shows that as a community we can go very far together and DO PLEASE always use us more for tests so we can make releases TOP QUALITY . It was again MUCH better than anything released so far in terms of stability. Great work!
Xdrqgol
2021-04-04 19:27:38 +0000 UTCI will chime in as well. This build has been a knock out of the park. Actually the first build that has worked flawlessly across everything I do without a crash. Fantastic work. FAN-FRIGGIN-TASTIC!1
James Tiller
2021-04-04 16:34:11 +0000 UTCThis has been the most stable for me yet. Although I can get slightly more speed from undervolt/PBO2, the tiny increase of speed does make my system more unstable, my games crash where as using CRT, Ive not had a crash yet and my temps are slightly lower too, my PC just seems to prefer it.
Morgan Ring
2021-04-03 20:27:34 +0000 UTCI thought the whole reason we have 32 GB of RAM is to feed Origin’s desktop client + 4 tabs of Chrome.
Henry Curtis Pelgrift
2021-04-03 18:44:41 +0000 UTCChrome is using EVERYTHING. I like a lot of its features, but I only have it installed on certain systems for that reason. Typical Google audacity: It will decide what you want for you, and any attempt to object on your part will be met with a second helping of shit you didnt ask for. I don't know a whole lot of Powershell, but I have actually never been able to *completely* remove Edge. The best you can do is uninstall its updates and keep it crippled. Chrome, luckily is removable...unless you're one a Chromebook. That I have no insight on, as I have never owned one.
Krewd
2021-04-03 16:08:16 +0000 UTCWhy is Chrome/Edge (based on Chromium) using PX profiles mostly of time, I use 6 windows with around 30 tabs distributed and CTR is enabling PX profiles all time using browser tabs.
PewWORKS TV
2021-04-03 15:03:42 +0000 UTCAh damn. Here I thought I was being helpful in identifying a bug. 😞 Hmmm, bandwidth is below XMP rating, but timings are much tighter.
Henry Curtis Pelgrift
2021-04-03 13:50:34 +0000 UTCP1 stats on my (so far stable, still testing) configuration: 1050 VID, vdroop: 2.9%, CCX1 4225mhz, CCX2: 4100mhz. The lowest my droop gets is 0.8% at PX High (4875mhz safe) but Im still able to stay about 1.48v peak. Is that cutting it too close? Its the one outlier in what seems to me to be an otherwise predictable vdroop cycle that stays within the 1.5-3.5% range that was outlined in the guides. I can maybe increase the negative offset but LLC is at level 2 in the UEFI, which also provides settings for overvolt protection of its own. I feel like I'm sufficiently protected...but plenty of fellas said that only to end up with a herpe or a child. So i defer to your superior wisdom ;) *Also: Yeah the earlier instability turned out to be overly-optimistic RAM timings on the 4x8gb Trident Neo. Its back in for this configuration at the settings I tested via the guide, and it seems to be working well so far.
Krewd
2021-04-03 08:05:40 +0000 UTCGreat, Downloaded Again! In the preview version, i have 5200 cb20 -600 of default, i try now.
Michael Lopez
2021-04-03 07:33:34 +0000 UTCSend me the logs and I'll see what's going on in your system
Yuri Bubliy
2021-04-03 07:12:38 +0000 UTCThanks for the info. The situation you described is most likely due to insufficient overclocking of RAM. In some cases, XMP is not enough and step-by-step algorithm jumps too high.
Yuri Bubliy
2021-04-03 07:11:14 +0000 UTCThanks Buddy, I'm glad I was able to solve the problem.
Yuri Bubliy
2021-04-03 07:08:52 +0000 UTCYour board's VRM is very powerful indeed, but the Asrock programming team makes mistakes very often and it affects the power stability. What is your vdroop for the P1?
Yuri Bubliy
2021-04-03 07:07:36 +0000 UTCThis is the most amazing CTR revision yet. I have complete stability so far through extensive benchmarking and gaming loads - as well as streaming/YouTube and other random loads. Since dialing in the frequencies and voltages I haven't had any random restarts. Very stable so far. Looks like I'm coming back from PBO2/Curve/DOS OC! 5950x, Dark Hero, 3401 Bios. Amazing job, Yuri. I'll keep supporting you!
Mickey85
2021-04-03 04:25:27 +0000 UTCWell I figured out part of my issue I thin. My profile setting has always remained at zero, as I try not to change too much at once. As a workaround for the bsod issue, I ran each profile configuration individually saved and activated them with modest adjustments to lower their voltage and frequencies, then I was able to finally get through diagnostics and back on track. I also threw in different ram; I had 4x8gb Trident Z Neo (XMP: 3600 CL14, 1.45v) so I swapped out for 2x16gb GSkillz Ripjaws V (XMP: 3600 CL16, 1.35v) and was able to get through the aforementioned workaround on the first attempt. So, next Im going to try my b-die in there again (starting with 2x8) but Im wondering if the higher voltage requirement was possibly just a litttle too much given my other power settings (Im on ASRock x570 Taichi Razer Edition, which is basically the original Taichi with beefed up VRM capability. It has also been temperamental since day one, so buyer beware. There are less annoying options)
Krewd
2021-04-03 03:09:26 +0000 UTCSo, it looks like it depends a lot on the profiles you choose for Diagnostics whether there is a restart. Which probably means a quirk with the individual setup of peoples’ machines. I’m currently running mine on all five different profiles in both RC4 without the HotFix and RC4 with. I had a BSOD from RC No HotFix on Profile 1 with my changes to BIOS and a restart with HotFix on Profile 0 and Profile 4. I have not had this on any of the other profiles in either version of RC4. So if you get a BSOD or restart on one diagnostic profile, try another. I’m also spamming you with my logs, Yuri. Cuz I’m helpful and annoying like that. 😬
Henry Curtis Pelgrift
2021-04-02 23:24:11 +0000 UTCIt’s basically the entire package just with fixed. I downloaded it and put in a new folder of its own (I keep a dedicated CTR folder on my desktop).
Henry Curtis Pelgrift
2021-04-02 23:09:52 +0000 UTCI've had that happen once or twice with more extreme profiles and when I've made the LLC a bit wonky. Try Profile 0? The Platinum Sample thing amuses me too, because it's kinda a funny little bug.
Henry Curtis Pelgrift
2021-04-02 21:29:38 +0000 UTCWell now Im getting an actual bsod instead of black screen reboot during diagnostics, then logging back in to be mocked by my 5950x which has since declared itself a "Platinum sample." I'm glad it thinks so. I still have my 3800x that didn't actually need replaced; I can take this thing out skeet shooting no problem. I'd probably just miss though, piss me off more...
Krewd
2021-04-02 21:17:56 +0000 UTCAwesome :) so how do I „upgrade“ to a new version ? I obv. Delete the old one ? Do I copy over settings ? And do I need to do everything from the guide again ? Or where can I skip to ? I am sorry I am a new patreon :p I used the „normal“ RC4 and did not have any problems with it but guess it’s safer to upgrade ?
Alexander Zinke
2021-04-02 19:02:25 +0000 UTCI kinda did with the one you’d shared from GoogleDrive. I’ll give it a shot then (and reset my LLC to High).
Henry Curtis Pelgrift
2021-04-02 18:52:23 +0000 UTCThis version was tested by many users who had a problem. Try it ;)
Yuri Bubliy
2021-04-02 18:50:59 +0000 UTCDid you make changes from the version you’d shared before that was just the .exe? That wasn’t as stable, but I was also experimenting with LLC. Medium and High seem better for my computer whereas auto results in higher vdroop and WHEAs... :/
Henry Curtis Pelgrift
2021-04-02 18:49:39 +0000 UTC
