CTR 2.1 RC6 (ver.8) - READY! (Patreon)

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.

How to make a diagnosis & profile creation (VIDEO)
How to activate profiles + quick performance test for PX and P1 profiles  (VIDEO)

_______

The program is in a 7-ZIP archive.  Download the archiver
.NET Framework to 4.8. Download
_______

What's new? Please read the PDF document attached to this message.

• Prime95 30.6 build 4. Fixing Prime errors.

• Updated more accurate OB diagnostics, you don't have to adjust anything. The OB values will be set for each profile + saved automatically.

• During the OB diagnostics information about CO (Curve Optimizer) coefficients is presented to the user. If for some reason you can not use CTR HYBRID OC - you have an alternative. Simply enter these CO coefficients in the BIOS. I know that there are some scripts that help find the CO. My solution is simpler, faster and more accurate. Why? I get an answer from SMU, i.e. the processor tells me which base curve it has and what it likes and what it doesn't like. For testing I also use AVX multi-core load. This allows me to get optimal results not only for each core individually, but also the result of interaction of all cores simultaneously. There are no alternatives to this function.

• Automatic update for CTR. Every time, when you start CTR, a secure TSL connection will be made to the github server where updates are stored. If an update is found, you will be notified. The process is fully automatic. After confirmation, the files are updated and the CTR is started.
About the github server. It is protected from hacker attacks and also has anti-virus software. Your system will always be safe.

• Load type detection system. This system allows real-time dynamic profiles to change their settings for maximum stability and performance. Now you can find out which application uses FMA3 and which uses AVX1 (for example).

• The response speed of dynamic profiles has doubled. That is, the frequency change speed is 8ms instead of the usual 16ms. This allows you to increase or decrease the frequency faster in relation to load and conditions.

• Windows notification. If the CTR is minimized or minimized to the tray you will not miss important messages. In the bottom right corner you will receive different kinds of notifications. In most cases this information is not critical, but it is worth writing to Discord about it. At the moment there are compatibility problems with the following programs: AIDA 64 (blocks global PCI mutex), Aquaero(does not allow for the use of global PCI mutex), Corsair iCUE (does not allow for the use of global PCI mutex) and AMD Ryzen Master (does not use a secure connection to the SMU).

• EXTRA BOOST - superstructure for OB, which allows dynamic profiles to run at higher frequencies in SSE - AVX1 loads. On average this is an extra 25-50 MHz without increasing the voltages.

• Full adaptation to CPU LLC (Load Line Calibration) Auto. More stability and more performance if you use CPU LLC Auto. This is my new recommendation for RC6.

• This build also contains a huge number of stability fixes and improvements.

_______

I want to share the good news with you. There is a new project in development (no it is not CTR PRO). Its purpose is to automatically optimize Zen 3 and Zen 3+ processors. It will include all the most important and unique things that has CTR as well as get new features. This is a work on bugs and new more usable interface. CTR is a successful product and I do not want to stop there. I think that the community deserves to get more. Thanks to you I got a chance to develop CTR and I really hope that you will stay with me. I know that $15 is a significant amount of money for some users, so I have added a new early access plan for $10.

Roughly the alpha version you will be able to see in the last days of June. CTR support is not finished and I plan to release a few updates (video too).

Thank you for your support :)

_______

Special thanks to @Riwwelorsch, @Ann Martiné, @ACE, @arcanazen, @DayDreamer, @Gadfly, @rizlah , @&&Devin, @Bloax , @RdWing and @wanderinarcheologist  for help with development and testing RC6.