Home Artists Posts Import Register

Content

This video contains a detailed description of the diagnostic process for Zen 3 processors.

Files

CTR 2.1 RC5 - LESSON #1(How to make a diagnosis & profile creation). PART 1.

This video contains a detailed description of the diagnostic process for Zen 3 processors.

Comments

Anonymous

cliffhanger at the end of the video! I suppose that will be in part 2 :) Great info.

Anonymous

Followed instructions to a T, as closely as possible. I fail during test #3 of diagnostics every single time. 5800x stock, CPU LLC set to level 3 on Asus TUF x570 Plus. Followed the rest of the requirements and steps, cleared config upon launch. Using RC5 v18 on latest version of windows with all updates.

Anonymous

thx. are you missing a clip at the end?

Timo H

As soon as I run the Diagnostic my 5800x goes above 90° and the test instantly gets cancelled, if I go through calculate profile one by one I don't have issues most of the time, only sometimes in px where it overheats again. Not due to manual failure, tested fans pump etc. already and swapped thermal paste. Any clue what I could be missing?

Timo H

Also my OB value is -22 which seems kinda odd since I only saw posititve numbers so far

Doug Wilkinson

hi! love this video. Can't wait for part 2 😁 I'm wondering if on zen 3 we should stop after successful diagnostics, or we should take the "Reccomended values for overclocking" for Profile 1 and 2 and use the tune function with those? I read in the manual that its only necessary for Zen 2 but these values are still created for Zen 3 and the clocks are higher so wondering what the guidance is...

Anonymous

This doesn't open on my machine at all ... CTR Loader is listed in running programs. Nothing opens.

1usmus

You can stop the diagnostics when the OB test is finished :)

Anonymous

This doesn't open on my pc at all , CTR Loader is Listed ,will not open or load with windows even did shell:start up .no luck at all

1usmus

Lets check Ver 19. alpha https://drive.google.com/file/d/1mjqpZBr4XqCf9mFQ6Gl1wzx8Od0sdM0v/view?

Anonymous

Ran the diagnostic on my 5800 this morning and test stopped at 4.8ghz with 1325mv. Is 4.8 a limit of the software or is that what CTR determined was a limit for my CPU because of the voltage used to hit that clock (poor scalability when using higher than that)?

Anonymous

I think I will pass another month or so on the subscriptions, got inconsistent results. I got a low VID CPU and, honestly, CRT is still not better than PBO + CO, at least for me. WIth CTR I got 4800+ boost at 1.157 or so, PBO brings at 1.27 boost over 5000 on large part of the cores. PX profile still does not work as it should.. 1.27 is completely safe voltage.

1usmus

Absolutely incorrect comparison. I even made a video for this, so that people don't try to compare 200 W and 100 W, but they keep doing it for some reason. I also don't understand the reason why you don't increase the voltages? What is the point of this post? Let me explain again, the base volt is the base TDP. Many users hate 80 degrees in the game, they like 65 degrees. If you like 80, I repeat again, set the voltage to what you like. What's the problem?

1usmus

This is not a limit, it is a basic safe frequency. The OB can increase this frequency (depending on the sample and the conditions).

Doug Wilkinson

Yuri there seems to still be so much confusion about the goals of the project. It might be good to work on the branding a bit. Patreon and twitter, with the occasional youtube/guru3d article might not be enough. Of course this would distract from the development...

Anonymous

If you press calculate ob, the computer reboots and the ob value comes out to zero. Why is that? My CPU is 5900X and my main board is ASROCK Steel Legend B550M.

Anonymous

I just noticed it hit 180a EDC (limit I had set) @ 81 degrees (peak). Is it worth bumping that a little higher just to see what it can do? I'm on a custom loop (5x120mm) so I have decent cooling. I've never seen it hit 180a before, kind of surprised me. Aorus X570 Ultra motherboard. Edit: Was doing some more testing and EDC spiked at 256a with a CPU Die of 128.7 degrees (and reported core 0 clock of 74,599mhz (HWInfo 7.02). I'm assuming it's all erroneous data. https://flic.kr/p/2kW5cPB

Anonymous

I dont think the PX profile is working correctly my cpu doesnt boost anywhere higher than 4.4 but it says that its in px high right now. I have a 5950x on Asrock x570 Creator.

Anonymous

I am not getting 80C, no way.. maximum 63C with a good AIO/ Liquid Freezer 280/. BTW, the reason for my post, the point is called the DISCUSSION. I have stated that before, not everyone is a sheep following the shepherd at the end of the day. BTW the PX voltage 1.375 at the top column is a permissible voltage by CTR, right ? I did not get me anywhere near 4900+ like OC on Dark Hero did. End of story.

1usmus

That's just your guess. 1.375 is sweet-spot. The maximum allowable voltage is 1.5V (AMD). You have textbox fields in which you can set the voltages. After the new voltage has been installed, a recalculation must be performed.

Anonymous

I keep having the issue of all the media in my PC speeding up

Anonymous

I m aware of that. Is 1.5V really maximum allowable voltage by AMD ? Yesterday I tried 1.3125 or so in the BIOS @1.32 under load - Cyberpunk 5050-5100 boost . Can upload screenshots. My point being at such voltage CTR is not gonna bring me anywhere near it.

1usmus

Boost does not work with manual voltages ;) https://cdn.wccftech.com/wp-content/uploads/2020/11/AMD-Ryzen-5000-Desktop-CPUs_Temps_Overclock_Power-Limit_Profiles_2-740x416.jpg

Anonymous

Thanks for the voltage table, but honestly,after adjusting VC manually in the BIOS the voltage runs up to 1.375 not more and the cpu is running 4900-5050 range

Anonymous

https://ibb.co/xX2CgCf

1usmus

This is not a mistake, just increase your PPT and TDC limits in CTR (TUNER tab > Settings mode Advanced)

Gabriel

So after doing a manual TUNE with my own reference voltage and frequency Penalties for the final profile: level 1 11:47:40 AM: CCX1 (185): 4675 MHz, 1250 mV OC+ 11:47:40 AM: CCX2 (149): 4575 MHz, 1250 mV OC= Cinebench R20 started Cinebench R20 finished with result: 11961 Voltage: 1.25 V PPT: 220.2 W Temperature: 79.8° Phoenix deactivated! Should I be using that a P1 or P2?

Anonymous

I´m experiencing weird behaviour with CTR 2.1 RC5 (ver.18) and now also with previous RC4. Would like to see if i can have some help. After Diagnosis and tunning process all seems normal, profile creation, voltages and clock speeds, etc. All good. However, after rebooting system I encounter autoload profile is not working correctly. CTR does autoload but clockspeeds applied are wrong. Undervolt profie now is: VID: 1150mV CCX1: 4175Mhz CCX2: 4175Mhz CCX3: 4075Mhz CCX4: 4025Mhz But Instead of these, CTR is doing: VID: 1150mV CCX1: 4113Mhz CCX2: 3340Mhz CCX3: 3799Mhz CCX4: 3799Mhz This is fo Rayzen 9 3900X with mobo Asus Rog Strix B550I gaming and stable 32Gb RAM at 3200Mhz. I´ve tried clearing config and close for both RC4 and RC5 and repeated diagnosis & tunning process but is giving the same issue. First time this happened was testing latest RC5 version that´s why I wanted to check if going back to RC4 would have solve the problem but it doesn´t. One thing that seems to fix this temporary is desactivating/activating profile manually but after doing this, inspite of applying clockspeeds the right way, log is showing this message "The mutex holding time has expired!" What am I doing wrong? I didn´t find a note about something similar to this in the guides. Thanks.

Timo H

Hey, basically all the overheating problems I had disappeared after I swapped my AIO, I assume my pump was broken. Thanks for the help

Gabriel

Beta 19 finally got me scoring the same or better than my best PBO with cooler temps. For example now I match my best PCMark where before that one will always be a win for PBO+CO in terms of performance. Other REAL apps are showing the same benefits. Things are moving forward for sure

Gabriel

Nope, guess I should have said alpha 19 or whatever term the v19 got.