Home Artists Posts Import Register
Gumroad has gone full retard. While we watch it sink, check out the archive password sharing.

Downloads

Content

A new document has been added which explains how BOOST works and the benefits of FREQUENCY LOCK mode. Updated the main guide. Please read all of the information in this post or you will run into problems. In particular I am talking about profile and settings compatibility.

_____________________

CHANGELOG:
_____________________

1. Total calibration of settings. Do not try to use old settings! The only thing that build C is compatible with is CO values. Once you have manually entered them, do the profile creation.

2. HEAVY MODE - HYBRID OC mode with increased stability. The ideal solution for users who require high fault tolerance during AVX2/FMA3 "calculations".

3. Redesigned mechanism for creating profiles. Profiles are now created based on CO tables. That is, the base frequencies of the profiles are higher, and HYDRA does not spend cycles to ramp frequencies. This has a significant impact on performance and reducing the CPU usage of the HYDRA application. This operation is extremely important and necessary after a change of voltage or CO.

4. Each profile has 3 base frequencies for each CCD. Since the base frequency of the profiles will increase significantly we have a problem and what happens if the profile base frequency is oriented to AVX1 load and we include AVX2 or FMA3. This is why I implement the "sandwich" mechanism. Each profile in addition to the base AVX1 frequency will have a frequency for the extra light load SSE and for the extra heavy load AVX2-FMA3. But most importantly, the user does not have to do anything, no new settings are added (I know some of you are intimidated by the complexity of the project), all offsets are controlled automatically.

5. Frequency state memory for each load type. This means that HYDRA remembers frequencies for different load types and can quickly return to the saved value if the load conditions are similar to the load conditions during which the "save" was created. This has a significant impact on performance and reducing the CPU usage of the HYDRA application.

6 .Stability for mixed load. I know that some of you have complained about stability problems in LinX and other applications that alternate between super light and super heavy workloads. Crashes occurred because HYDRA did not have time to reduce the frequency (which was obtained with SSE load) when switching to AVX2/FMA3 state. Now during the presence of SSE load, HYDRA has a hard limit on the frequency increase, which allows a smoother transition to the AVX2/FMA3 state.

7. Added CO "alignment" function. Frequency lock mode is a new mode (for HYBRID OC) that may require a CO alignment operation to improve stability. What it means. After diagnostics, you get a report about CO and result frequencies that cores reach. Alignment mode allows you to find an overall satisfactory safe frequency for all cores in the CCD complex as well as recalculate CO. That is, we create a rule in which the best cores will not use a frequency that is unsafe for neighboring weaker cores in the CCD complex.

8. Checking Updates. In the presence of the Internet will prompt the user about the availability of updates, as well as display important information that I want you to quickly bring to you.

9. Find best voltages. This function has been redesigned and is able to provide the user with information about the best voltages and optimal voltages at which the processor operates with maximum energy efficiency. The user will also have energy efficiency metrics (MHz per 1mV and MHz per 1W for each CCD) available for each of the steps.

10. Information about HYDRA response speed during tasks (LOGGING page).

11. The GAME profile will automatically shut down if a serious load is detected in the system (AVX2/FMA3).

12. Improvement of the overheat protection system and fixing a number of bugs.

13. Reduced probability of 2T switching on when there is no load. Power saving has been improved.

14. Changed the system of profiles priority during holding. Has a serious effect on stability.

_____________________


Thank you for your patience and support!

Files

Comments

Anonymous

thanks Yuri, several of us are still with you, keep your head up. Keep doing your work, you are doing great. I appreciate the release. Thank You much. Keep at it friend.

Anonymous

Testing tomorrow morning. Have to get to sleep sometime.

Anonymous

Would you recommend doing a full clean test with this version? Cause in that case I gotta plan in some time! ^^

Anonymous

Just started the boost test and i think the frequencies might be slightly off ***HYDRA 1.0C PRO by 1usmus*** 10/31/2021 11:21:46 Microsoft Windows NT 6.2.9200.0 AMD Ryzen 5 5600X 6-Core Processor MSI MAG B550 TOMAHAWK (MS-7C91) BIOS ver. A.50 SMU ver. 56.44.00 TABLE ver. 3672324 DRAM speed 3800 MHz Creating a basic configuration file for settings... Creating a basic configuration file for profiles... 11:22:35: Boost testing started! You have unique processor, 2 CCD's! 11:23:07: Boost testing finished! HYDRA BOOST TESTER RESULTS CORE / FREQUENCY / VID / POWER / TEMP C01 F 4746 V 1.426 W 12.19 T 56.33 C02 F 100000 V 1.424 W 5.3 T 16.1 C03 F 0 V 1.424 W 0 T 0 C04 F 0 V 1.424 W 0 T 0 C05 F 97333 V 1.424 W 3.6 T 14.5 C06 F 100000 V 1.424 W 4.2 T 15.5

Anonymous

***HYDRA 1.0C PRO by 1usmus*** 10/31/2021 10:33:52 Microsoft Windows NT 6.2.9200.0 AMD Ryzen 9 5950X 16-Core Processor GIGABYTE X570 AORUS MASTER BIOS ver. F34 SMU ver. 56.53.00 TABLE ver. 3672069 DRAM speed 3600 MHz Creating a basic configuration file for settings... Creating a basic configuration file for profiles... Phoenix ready! 10:35:44: CO (CORE) test started! 10:35:57: Step: 1 CORE#1 BASE FREQ: 4700MHz REAL FREQ: 4700MHz 10:35:57: Saving intermediate values... 10:36:06: Test#1 CORE#1 CO: -27 DELTA: -2 TEMPERATURE: 69°C 10:36:13: Stress test stopped. Phoenix deactivated! Phoenix ready! 10:36:35: CO (CORE) test started! 10:36:47: Step: 1 CORE#1 BASE FREQ: 4725MHz REAL FREQ: 4725MHz 10:36:47: Saving intermediate values... 10:36:56: Test#1 CORE#1 CO: -3 DELTA: -1 TEMPERATURE: 68°C 10:37:37: Saving intermediate values... 10:37:48: Test#2 10:38:29: Saving intermediate values... 10:38:40: Test#3 10:39:26: Step: 2 CORE#1 BASE FREQ: 4725MHz REAL FREQ: 4750MHz 10:39:26: Saving intermediate values... 10:39:35: Test#1 CORE#1 CO: 33 DELTA: 36 TEMPERATURE: 69°C 10:40:16: Saving intermediate values... 10:40:27: Test#2 10:41:09: Saving intermediate values... 10:41:20: Test#3

Anonymous

...may have discovered an issue - I began diagnostic and stopped, then restarted - it looks like the diag started from 4725MHz rather than 4700MHz - See logs above

1usmus

Your bios is pretty old. Try restarting the application now, if the problem persists, message me in private.

Anonymous

Can anyone tell me what CO value is? And what is the effect if i reduce it or increase it manually after diagnostic. Thanks in advance

1usmus

This is the offset of the volts with respect to AMD's standard V/F curve. It is measured in millivolts. It is a calculated value and does not affect the actual volts. To put it simply. We tell the processor that we supply more volts (we cheat it, in fact it gets as much as it is prescribed in the profile) and it increases the frequency. The higher the CO value, the higher the frequency. Of course, the lower the CO, the lower the resulting frequency.

Anonymous

Thank you very much for your effort & the incredible work, Yuri! I also have a question: Do I have to increase the max EDC, max TDC and max PPT limits in the settings tab by 30-40 when on air cooling, or are these values filled in by default alright (170, 170, 140)?

Anonymous

I have the same question, I have a 5900x with an Arctic Freeze 360mm, do I use the recommended values?

Anonymous

Perfect timing for Halloween. It's like I knocked on your door in my costume and you dropped a new hydra build into my candy bag.

Anonymous

***HYDRA 1.0C PRO by 1usmus*** 10/31/2021 14:13:51 Microsoft Windows NT 6.2.9200.0 AMD Ryzen 9 5950X 16-Core Processor ASRock X570 Taichi BIOS ver. P4.60 SMU ver. 56.53.00 TABLE ver. 3672069 DRAM speed 3600 MHz

Anonymous

Results CO testing 16:27:30: Saving intermediate values... 16:27:30: Saving intermediate values... 16:27:30: Saving intermediate values... CORE| CPPC | BASE | RES | TEMP | CO C01 | 208 | 4775 | 4900 | 63 | 143 C02 | 199 | 4750 | 4850 | 62 | 105 C03 | 190 | 4700 | 4875 | 64 | 202 C04 | 185 | 4700 | 4850 | 63 | 193 C05 | 212 | 4825 | 4925 | 65 | 79 C06 | 203 | 4725 | 4875 | 64 | 139 C07 | 212 | 4825 | 4875 | 70 | 29 C08 | 194 | 4725 | 4875 | 67 | 192 C09 | 172 | 4625 | 4800 | 63 | 203 C10 | 167 | 4600 | 4750 | 61 | 149 C11 | 149 | 4550 | 4775 | 64 | 241 C12 | 163 | 4600 | 4800 | 62 | 216 C13 | 176 | 4625 | 4825 | 62 | 214 C14 | 181 | 4625 | 4800 | 61 | 170 C15 | 154 | 4575 | 4750 | 66 | 201 C16 | 158 | 4575 | 4750 | 65 | 207 The quality evaluation of cores has been successfully completed! Final ranking of cores: by AMD (CPPC) | by real frequency C07 212 4875MHz | C05 4925MHz C05 212 4925MHz | C01 4900MHz C01 208 4900MHz | C08 4875MHz C06 203 4875MHz | C07 4875MHz C02 199 4850MHz | C06 4875MHz C08 194 4875MHz | C03 4875MHz C03 190 4875MHz | C04 4850MHz C04 185 4850MHz | C02 4850MHz C14 181 4800MHz | C13 4825MHz C13 176 4825MHz | C14 4800MHz C09 172 4800MHz | C12 4800MHz C10 167 4750MHz | C09 4800MHz C12 163 4800MHz | C11 4775MHz C16 158 4750MHz | C16 4750MHz C15 154 4750MHz | C15 4750MHz C11 149 4775MHz | C10 4750MHz

Anonymous

I noticed several things. During multi-thread testing the CCD1 under-performed compared to the CCD2. This was the opposite with the previous version. I also have the feeling that the test didn't get as much out of the CPU as the previous version, this also reflects back when it is stating that I have a Bronze/Bronze CPU whereas the previous version mentioned I had a Golden/Silver CPU. Last point is that it was eventually stuck at 0% at Test 2: 16:58:57: Test 2 started! 16:58:57: 9T-16T 17:11:44: Cinebench stopped!

Anonymous

With a boost test I also noticed that it's only testing at 3500 max.

Anonymous

edited. test result too long.

Anonymous

Yuri, pre-Hydra back when we were using CTR the PDF had a lot of instructions for things to enable in the BIOS such as global C-state control, CPPC, CPPC preferred cores, etc. The new Hydra PDF is way simpler (which is good) in terms of what it tells you to set in the BIOS. For those of us that are making the first jump from CTR to Hydra (I've been waiting for 1.0C before switching), should we reset our BIOS and just make the changes the Hydra PDF says to? Or is it totally fine to leave the settings that we were told to use for CTR and that worked for our system?

Anonymous

Yes, I'm curious if there are further optimal BIOS settings beyond the few mandatory changes.

Anonymous

Just wanted to say , so far so good ! I ran 1C diagnostics for the first time last night and it completed without the constant freezes and reboots ! This iteration, at least for me, seems FAR smoother and polished. Ive done absolutely no tweaking beyond the profile creation and activation and was able to run Folding home nearly all night. With 1B the crash was immediate. My CPU-Z multicore score saw a thousand point increase but my single core score was relatively unchanged. 694 before and 696 after. Of course the energy reduction and heat reduction benefit is the icing on the cake ! GREAT job Yuri ! EDIT: After just a small amount of tweaking I am completely stable thru 24 hours of Folding Home @ 100% usage. Windows 11 Pro-64. CPU_Z Single core score- 698-699 consistently and multicore 13,324 With far less heat and power , VERY impressed with this iteration 5950X. Taichi X570, 16G-3600,6900XT

Anonymous

Ya this build is so much more stable for diagnostics. It was the one I waited for. I tried A and B and they'd reboot very soon into the testing and wouldn't relaunch Hydra to continue. With this, I've run it twice now (once overnight) and it only reboots when checking CO values for my worst core on my second CCD and then faithfully picks right back up where it left off. So I can actually set this thing to run a full diagnostic and walk away knowing it'll fully complete on its own. A good thing since a full diag takes 7 hours on my 5950x hahaha

Anonymous

Has anyone tried hydra+win11? I want to upgrade since all problems solved but im not sure if compatibility hydra+win11 is 100% ok

Anonymous

For what purpose are the profiles (UV, normal, etc.) used? After the diagnostic, the voltages are adjusted, right?

Anonymous

This is the first Time for me to hit 19860 Points on TimeSpy in 3DMark. This is great. Also first time that i see frequencies from 4'915Mhz. Also peaks single core in game from 4900mhz - runs like never before! And i'm on AIO. i wonder what could i reach with a custom watter loop :D https://www.3dmark.com/3dm/67927451

Anonymous

What is an example of sse,avx1 and avx2/fma3 ? how i can choose AVX1 CO offset ? i rember that with pbo i was able to arrive to 5150 mhz on my 5900x in more than 2-3 cores and other cores not were under 5000-4950 mhz . How i can reach maximum stability/boost with hydra ?

Anonymous

You could use them w/out a diagnostic but I don't think you'd have very accurate results, as it's just a preset: and since everyone's hardware can be different (mine for example is binned a bit weirdly), I doubt you'd get optimal results by just hitting this. What you want to do is hit one of the profiles for what you desire (undervolting for power saving, normal for stock cooling, OC/XOC if you know your cooling can actually handle it) and then run a diagnostic and it'll use the VIDs set by the preset during some of the diagnostic phases to find optimal values (CO/base freq for example) for your specific chip that are stable. On page 11 of the PDF it says that the voltage hunting is in regards to AVX2/FMA3 loads: it's not hunting for voltages for all the profiles like 1t-2t etc, it's for the heavier workload tasks which can be tricky to figure out a voltage on your own. Since I'm writing this pre-coffee and not quite lucid, tl;dr: auto voltage change is for AVX2/FMA3 (and I believe game) profiles, not the others

Anonymous

Is it compatible with Win 11?

Anonymous

I'm not on Windows 11 but page 7 of the PDF says "Windows 11 fully spported". Another user commented that it worked for them too.

Anonymous

does anyone have an idea what could be the problem here? Phoenix ready! Microsoft Windows NT 6.2.9200.0 AMD Ryzen 9 5900X 12-Core Processor MSI MPG B550 GAMING CARBON WIFI (MS-7C90) BIOS ver. 1.70 SMU ver. 56.53.00 TABLE ver. 3672069 DRAM speed 3600 MHz AIO cooler 23:33:24: CO (CORE) test started! 23:33:36: Step: 1 CORE#1 BASE FREQ: 4650MHz REAL FREQ: 4650MHz 23:33:36: Saving intermediate values... 23:33:43: Stress test stopped. Temperature limit reached! 95,2° 23:33:45: Test#1 Phoenix deactivated!

Anonymous

Cooler... "Temperature limit reached! 95,2°" undoubtedly means that your CPU is overheating. See that you have AIO, but you need to check is it properly setup: thermal paste, tighten up, cooling profile maybe...

Anonymous

yes i tried. In normal Cinebench it holds 90 ° ". The processor normally takes the maximum Mhz until it reaches 90 °". In the Hydra, however, it goes beyond that in the benchmark. It keeps the 4700 mhz constant until it gets too warm. O.o Which settings do you use for the limit values? I have now set that according to AMD: PPT 142, TDC 95, EDC 140 ... temperature 95 ..... Is that not enough? Yesterday a test was canceled because of the PPT value. Anyone have an idea what I could change in the bios? Before that I had - 0.1V in the CPU offset. It ran up to 81 ° when gaming ". Thank you in advance for your help!

Anonymous

Hmm I'm not sure my profiles were created right. Not sure how to paste a screenshot here but the CCD1 and CCD2 values for all profiles are set to 3500.. Results CO testing 07:56:41: Saving intermediate values... 07:56:41: Saving intermediate values... 07:56:41: Saving intermediate values... CORE| CPPC | BASE | RES | TEMP | CO C01 | 174 | 4700 | 4900 | 81 | 141 C02 | 174 | 4775 | 4900 | 81 | 88 C03 | 166 | 4675 | 4875 | 79 | 280 C04 | 170 | 4700 | 4825 | 78 | 173 C05 | 158 | 4650 | 4850 | 83 | 284 C06 | 162 | 4625 | 4675 | 84 | 44 C07 | 150 | 4675 | 4675 | 74 | 12 C08 | 141 | 4650 | 4700 | 73 | 61 C09 | 145 | 4675 | 4700 | 74 | 46 C10 | 154 | 4675 | 4650 | 73 | -27 C11 | 137 | 4650 | 4700 | 77 | 90 C12 | 133 | 4625 | 4725 | 76 | 119 The quality evaluation of cores has been successfully completed! Final ranking of cores: by AMD (CPPC) | by real frequency C02 174 4900MHz | C02 4900MHz C01 174 4900MHz | C01 4900MHz C04 170 4825MHz | C03 4875MHz C03 166 4875MHz | C05 4850MHz C06 162 4675MHz | C04 4825MHz C05 158 4850MHz | C12 4725MHz C10 154 4650MHz | C11 4700MHz C07 150 4675MHz | C09 4700MHz C09 145 4700MHz | C08 4700MHz C08 141 4700MHz | C07 4675MHz C11 137 4700MHz | C06 4675MHz C12 133 4725MHz | C10 4650MHz Unreceived frequency due to incorrect CPPC tags 1T 0MHz 2T 0MHz 3T 50MHz 4T 25MHz 5T 150MHz 6T 50MHz 7T 50MHz 8T 50MHz 9T 50MHz 10T 25MHz 11T 25MHz 12T 0MHz CURVE OPTIMIZER values for BIOS (If you do not plan to use HYDRA) C01 SAFE CO: -23 FAST CO: -30 C02 SAFE CO: -14 FAST CO: -29 C03 SAFE CO: -30 FAST CO: -30 C04 SAFE CO: -28 FAST CO: -30 C05 SAFE CO: -30 FAST CO: -30 C06 SAFE CO: -7 FAST CO: -22 C07 SAFE CO: -2 FAST CO: -17 C08 SAFE CO: -10 FAST CO: -25 C09 SAFE CO: -7 FAST CO: -22 C10 SAFE CO: 4 FAST CO: -11 C11 SAFE CO: -15 FAST CO: -30 C12 SAFE CO: -19 FAST CO: -30 Max CPU Boost Clock Override: 250MHz 07:56:45: CO smoothing started! Phoenix deactivated! Phoenix ready! 07:56:45: CO (CCD) test started! 07:57:02: Step: 1 CCD#1 FREQ 4400MHz CCD#2 FREQ 4425MHz 07:57:02: Saving intermediate values... 07:57:05: Test#1 CORE#1 CO: -50 CORE#7 CO: -36 CORE#2 CO: -56 CORE#8 CO: -32 CORE#3 CO: -34 CORE#9 CO: -36 CORE#4 CO: -38 CORE#10 CO: -33 CORE#5 CO: -32 CORE#11 CO: -28 CORE#6 CO: -28 CORE#12 CO: -30 SVI2: 1152mV 07:57:19: CCD#2 instability detected! 07:57:19: Thread# 14 dropped! 07:57:19: Stress test stopped. CCD#1 FREQ 4400MHz CCD#2 FREQ 4400MHz 07:57:20: Saving intermediate values... 07:57:23: Test#1 CORE#1 CO: -49 CORE#7 CO: -43 CORE#2 CO: -55 CORE#8 CO: -41 CORE#3 CO: -32 CORE#9 CO: -45 CORE#4 CO: -35 CORE#10 CO: -41 CORE#5 CO: -29 CORE#11 CO: -37 CORE#6 CO: -27 CORE#12 CO: -38 SVI2: 1151mV 07:58:27: Saving intermediate values... 07:58:30: Test#2 07:58:32: CCD#2 instability detected! 07:58:32: Thread# 15 dropped! 07:58:32: Stress test stopped. CCD#1 FREQ 4400MHz CCD#2 FREQ 4375MHz 07:58:32: Saving intermediate values... 07:58:36: Test#1 CORE#1 CO: -42 CORE#7 CO: -46 CORE#2 CO: -50 CORE#8 CO: -42 CORE#3 CO: -25 CORE#9 CO: -48 CORE#4 CO: -26 CORE#10 CO: -42 CORE#5 CO: -22 CORE#11 CO: -38 CORE#6 CO: -18 CORE#12 CO: -41 SVI2: 1150mV 07:59:40: Saving intermediate values... 07:59:43: Test#2 07:59:46: CCD#2 instability detected! 07:59:46: Thread# 15 dropped! 07:59:46: Stress test stopped. CCD#1 FREQ 4400MHz CCD#2 FREQ 4350MHz 07:59:46: Saving intermediate values... 07:59:49: Test#1 CORE#1 CO: -39 CORE#7 CO: -53 CORE#2 CO: -47 CORE#8 CO: -51 CORE#3 CO: -24 CORE#9 CO: -55 CORE#4 CO: -26 CORE#10 CO: -51 CORE#5 CO: -21 CORE#11 CO: -46 CORE#6 CO: -17 CORE#12 CO: -47 SVI2: 1150mV 08:00:54: Saving intermediate values... 08:00:57: Test#2 08:02:03: Step: 2 CCD#1 FREQ 4425MHz CCD#2 FREQ 4350MHz 08:02:03: Saving intermediate values... 08:02:06: Test#1 CORE#1 CO: -30 CORE#7 CO: -50 CORE#2 CO: -38 CORE#8 CO: -48 CORE#3 CO: -13 CORE#9 CO: -52 CORE#4 CO: -16 CORE#10 CO: -48 CORE#5 CO: -10 CORE#11 CO: -44 CORE#6 CO: -6 CORE#12 CO: -46 SVI2: 1150mV 08:03:11: Saving intermediate values... 08:03:14: Test#2 08:04:21: Step: 3 CCD#1 FREQ 4450MHz CCD#2 FREQ 4350MHz 08:04:21: Saving intermediate values... 08:04:24: Test#1 CORE#1 CO: -25 CORE#7 CO: -52 CORE#2 CO: -32 CORE#8 CO: -50 CORE#3 CO: -7 CORE#9 CO: -53 CORE#4 CO: -8 CORE#10 CO: -49 CORE#5 CO: -5 CORE#11 CO: -45 CORE#6 CO: 2 CORE#12 CO: -47 SVI2: 1148mV 08:05:27: Saving intermediate values... 08:05:30: Test#2 08:06:37: Step: 4 CCD#1 FREQ 4475MHz CCD#2 FREQ 4350MHz 08:06:37: Saving intermediate values... 08:06:40: Test#1 CORE#1 CO: -18 CORE#7 CO: -51 CORE#2 CO: -26 CORE#8 CO: -50 CORE#3 CO: 4 CORE#9 CO: -54 CORE#4 CO: -4 CORE#10 CO: -50 CORE#5 CO: 9 CORE#11 CO: -44 CORE#6 CO: 14 CORE#12 CO: -46 SVI2: 1150mV 08:06:59: CCD#2 instability detected! 08:06:59: Thread# 14 dropped! 08:06:59: Stress test stopped. CCD#1 FREQ 4475MHz CCD#2 FREQ 4325MHz 08:06:59: Saving intermediate values... 08:07:02: Test#1 CORE#1 CO: -18 CORE#7 CO: -58 CORE#2 CO: -25 CORE#8 CO: -58 CORE#3 CO: 6 CORE#9 CO: -61 CORE#4 CO: -4 CORE#10 CO: -58 CORE#5 CO: 10 CORE#11 CO: -54 CORE#6 CO: 12 CORE#12 CO: -54 SVI2: 1150mV 08:08:06: Saving intermediate values... 08:08:09: Test#2 08:09:16: Step: 5 CCD#1 FREQ 4500MHz CCD#2 FREQ 4325MHz 08:09:16: Saving intermediate values... 08:09:19: Test#1 CORE#1 CO: -9 CORE#7 CO: -58 CORE#2 CO: -18 CORE#8 CO: -58 CORE#3 CO: 22 CORE#9 CO: -60 CORE#4 CO: 10 CORE#10 CO: -58 CORE#5 CO: 28 CORE#11 CO: -52 CORE#6 CO: 32 CORE#12 CO: -54 SVI2: 1150mV 08:10:23: Saving intermediate values... 08:10:26: Test#2 08:11:33: Step: 6 CCD#1 FREQ 4525MHz CCD#2 FREQ 4325MHz 08:11:33: Saving intermediate values... 08:11:36: Test#1 CORE#1 CO: 1 CORE#7 CO: -59 CORE#2 CO: -13 CORE#8 CO: -58 CORE#3 CO: 39 CORE#9 CO: -61 CORE#4 CO: 28 CORE#10 CO: -58 CORE#5 CO: 43 CORE#11 CO: -54 CORE#6 CO: 49 CORE#12 CO: -55 SVI2: 1149mV 08:12:14: CCD#1 instability detected! 08:12:14: Thread# 6 dropped! 08:12:14: Stress test stopped. CCD#1 FREQ 4500MHz CCD#2 FREQ 4325MHz 08:12:14: Saving intermediate values... 08:12:17: Test#1 CORE#1 CO: -9 CORE#7 CO: -57 CORE#2 CO: -19 CORE#8 CO: -55 CORE#3 CO: 24 CORE#9 CO: -59 CORE#4 CO: 12 CORE#10 CO: -55 CORE#5 CO: 27 CORE#11 CO: -52 CORE#6 CO: 33 CORE#12 CO: -53 SVI2: 1150mV 08:13:21: Saving intermediate values... 08:13:24: Test#2 CCD quality evaluation has been successfully completed! Results CCD testing CORE#1 CO: -9 CORE#7 CO: -57 CORE#2 CO: -19 CORE#8 CO: -55 CORE#3 CO: 24 CORE#9 CO: -59 CORE#4 CO: 12 CORE#10 CO: -55 CORE#5 CO: 27 CORE#11 CO: -52 CORE#6 CO: 33 CORE#12 CO: -53 Energy Efficiency CCD#1 3.91 | BRONZE sample Energy Efficiency CCD#2 3.76 | BRONZE sample Phoenix deactivated! 08:14:31: Test 1 started! -= PROFILE: 1T-2T =- VID: 1375mV CCD1 FREQUENCY AVX1: 4675MHz FMA3: 4600MHz CCD2 FREQUENCY AVX1: 4650MHz FMA3: 4575MHz -= PROFILE: 3T-4T =- VID: 1375mV CCD1 FREQUENCY AVX1: 4650MHz FMA3: 4575MHz CCD2 FREQUENCY AVX1: 4625MHz FMA3: 4550MHz -= PROFILE: 5T-6T =- VID: 1325mV CCD1 FREQUENCY AVX1: 4600MHz FMA3: 4500MHz CCD2 FREQUENCY AVX1: 4575MHz FMA3: 4475MHz 08:15:18: Test 1 finished! 08:15:18: Test 2 started! 08:15:18: 7T-12T DEBUG INFO: Start VID: 1275mV Start CCD#1 FREQ: 4125MHz Start CCD#2 FREQ: 4050MHz Vdroop: 2.43% CO reserve: -18 / -19 08:15:44: Cinebench stopped! -= PROFILE: 7T-9T =- VID: 1325mV CCD#1 FREQUENCY AVX1: 4650MHz FMA3: 4550MHz CCD#2 FREQUENCY AVX1: 4575MHz FMA3: 4475MHz -= PROFILE: 10T-12T =- VID: 1275mV CCD#1 FREQUENCY AVX1: 4575MHz FMA3: 4475MHz CCD#2 FREQUENCY AVX1: 4500MHz FMA3: 4400MHz 08:15:44: Test 2 finished! 08:15:44: Test 3 started! 08:15:44: ALL THREADS (AVX2) DEBUG INFO: Start VID: 1150mV Start CCD#1 FREQ: 3850MHz Start CCD#2 FREQ: 3800MHz Vdroop: 2.7% CO reserve: -12 / -10 08:16:05: Cinebench stopped! -= PROFILE: ALL (AVX2) =- VID: 1150mV CCD#1 FREQUENCY AVX1: 4325MHz AVX2: 4275MHz CCD#2 FREQUENCY AVX1: 4175MHz AVX2: 4125MHz 08:16:05: Test 3 finished! 08:16:05: Test 4 started! 08:16:05: ALL THREADS (FMA3) 8:16:08 AM: Stress test stopped. PPT limit reached! 234.6W 08:16:10: Test 4 finished!

Anonymous

Read the pdf included which explains how to achieve that?

Anonymous

@Yuri after optimisation my apps were lil bit laggy. I noted always when i start an app or install one the task gets mostly the C07 CCD2 on my 5900x. I just went to C07 and reduced CO Value for C01 on CCD2 by 20. Now opening the apps feels much smoother and without a delay. Can you double-check this?

1usmus

The instructions (pdf) have step-by-step steps. The user must set the maximum limits of PPT, EDC and TDC. If he doesn't do this the protection system will stop diagnostics if one of the limits has been exceeded. Either the user needs to reduce the voltages for the profile where the limit is exceeded.

1usmus

The HYDRA process is always bound to the second CCD, the core with the lowest CPPC. This is normal if it is active, it is the way it is designed.

Anonymous

Yuri Quick question. Read all the new info on the pdf,, did a diag but had to go to work so did not finish, decided was about to do it now, so I re-read, I noticed 1 thing By default for the diag Freq Lock is enabled, I was reading all the little pop up info msgs and noticed the under the Equilize CO in CCD it mentions we should first use it before using the Freq lock. So I guess the question is which do I use for the Diag? The ECC first then the FL or just run as is with FL already on?

1usmus

CO alignment is an optional action that you can perform after diagnostic if the FREQUENCY LOCK mode is unstable in a low-thread load

Anonymous

Thanks for the great tool! a small issue I found out, HYDRA runs at normal CPU usage, at around 0.5% for my 5900x if I just launch it and keep it in the background, but once I opened it up and it will jump to 4-5% even I tried to minimize it again. I have to relaunch the app to get it back down to less than 1%. The usage goes back down too if I disable hybrid oc with the app opened in the foreground, do you know what might cause that to happen?

Anonymous

Hi, Newcomer question, what about Ryzen Master ? Can cohabit, must desinstall ? Thx guy for awesome job.

Anonymous

If you use Hydra, it must be your only overclocking tool.

Anonymous

After some time with the program on, the numerical values output strange values and are not updated. And during the diagnosis, the work was stopped due to an error like CMD_REJECTED_PREREQUISITE 93, and I wonder if it is related to the current situation and I want to know what kind of error it is. http://drive.google.com/uc?export=view&id=1rboOpDSCagoIcy_9qEG9WARKWbHJrf4Y

Anonymous

@Yuri i just managed to hit my first "Legendary" Firestrike Result hiting 40420 Pts with max. 4'947Mhz on 5900x haha This is so crazy!! Holly! And that with an AIO Cooling. https://ibb.co/nw916Cf https://www.3dmark.com/3dm/68091389 Really great. And stable, really stable. Prozessor AMD Ryzen 9 5900X Prozessortakt 4.947 MHz Physische/logische Prozessoren 1 / 24 Anzahl der Cores 12 Package AM4 Herstellungsprozess 7 nm TDP 105 W

Anonymous

https://www.3dmark.com/search#advanced?test=fs%20P&cpuId=2758&gpuId=1389&gpuCount=0&deviceType=ALL&memoryChannels=0&country=&scoreType=overallScore&hofMode=false&showInvalidResults=false&freeParams=&minGpuCoreClock=&maxGpuCoreClock=&minGpuMemClock=&maxGpuMemClock=&minCpuClock=&maxCpuClock= current 8th on 3d mark list with 5900x and 3080Ti ☺️😁

Anonymous

In the future, please don't post your entire test results to a top-level comment, it's annoying to have to scroll multiple pages to the next comment! I recommend that you post a short initial comment, then reply to yourself with the results. Thanks!

Anonymous

you mentioned the Bios so just wanted to draw your attention to what it says on the PDF and i quote "CPU Voltage - Auto (in BIOS). Offset is FORBIDDEN." not sure is your problem but figured i'll post jic as i saw that you mentioned you had before the -0.1 offset.

Anonymous

hi guys, can you please tell me how to run diagnostics higher than at a voltage of 1.375? LLC at the Turbo level. in BIOS everything is automatic. 5900x processor. Motherboard: gigabyte b550 master. I tried to set the OC overclocking mode in Hydra, but when I start diagnostics, the test starts at a voltage of 1.37 or lower

Anonymous

Hi, Yuri, hydra 1.0c for game is great, but when run blender, the logs always show below message, any ideas? PCI-MUTEX holding time has expired! Retrying to send a command! . . . more and more . PCI-MUTEX holding time has expired! Retrying to send a command! AM 10:39:55: CMD_FAILED 5 https://i.imgur.com/xQMUziZ.png

Anonymous

Hi, Yuri! I seem to have a problem with Hydra 1.0C - when running diagnostics, the final test stops with either "PPT Limit reached" or "Temperature limit reached" - no profiles are being created: 05:32:10: Test 3 started! 05:32:10: ALL THREADS (AVX2) DEBUG INFO: Start VID: 1362mV Start CCD#1 FREQ: 4200MHz Start CCD#2 FREQ: 4150MHz 5:32:24: Cinebench stopped! PPT limit reached! 209,8W 05:32:25: Test 3 finished! I fail to grasp the logic here - if the limit is reached, why not use the previous values?

Anonymous

Hi Yuri, I have done some testing again between 10B and 10C. See the comments for the results. Btw, at 10C the 9T-16T test failed again. It does run 10 minutes, but Hydra doesn't process it. It simply stays at 0%. (Ps. I can share the text files if you want all the detailed info as well)

Anonymous

11/10/2021 19:25:16 Microsoft Windows NT 6.2.9200.0 AMD Ryzen 9 5950X 16-Core Processor ASRock X570 Taichi BIOS ver. P4.60 SMU ver. 56.53.00 TABLE ver. 3672069 DRAM speed 3600 MHz Hydra 10B - Results Results CO testing 17:10:33: Saving intermediate values... 17:10:33: Saving intermediate values... 17:10:33: Saving intermediate values... CORE| CPPC | BASE | RES | TEMP | CO C01 | 208 | 4750 | 4950 | 62 | 190 C02 | 199 | 4775 | 4850 | 62 | 97 C03 | 190 | 4725 | 4900 | 63 | 230 C04 | 185 | 4700 | 4875 | 62 | 200 C05 | 212 | 4850 | 4950 | 63 | 94 C06 | 203 | 4725 | 4875 | 62 | 142 C07 | 212 | 4825 | 4875 | 69 | 33 C08 | 194 | 4725 | 4900 | 68 | 222 C09 | 172 | 4625 | 4825 | 64 | 233 C10 | 167 | 4600 | 4750 | 62 | 155 C11 | 149 | 4550 | 4775 | 64 | 241 C12 | 163 | 4600 | 4825 | 63 | 246 C13 | 176 | 4625 | 4800 | 63 | 190 C14 | 181 | 4625 | 4775 | 61 | 141 C15 | 154 | 4575 | 4775 | 64 | 229 C16 | 158 | 4575 | 4750 | 66 | 206 Hydra 10C - Results Results CO testing 18:52:16: Saving intermediate values... 18:52:16: Saving intermediate values... 18:52:16: Saving intermediate values... CORE| CPPC | BASE | RES | TEMP | CO C01 | 208 | 4775 | 4900 | 64 | 151 C02 | 199 | 4750 | 4875 | 64 | 132 C03 | 190 | 4700 | 4900 | 66 | 253 C04 | 185 | 4700 | 4875 | 61 | 216 C05 | 212 | 4850 | 4925 | 62 | 64 C06 | 203 | 4725 | 4875 | 62 | 136 C07 | 212 | 4825 | 4900 | 68 | 42 C08 | 194 | 4725 | 4875 | 67 | 185 C09 | 172 | 4625 | 4825 | 63 | 206 C10 | 167 | 4600 | 4750 | 62 | 148 C11 | 149 | 4575 | 4800 | 62 | 259 C12 | 163 | 4575 | 4800 | 62 | 222 C13 | 176 | 4625 | 4800 | 62 | 176 C14 | 181 | 4650 | 4800 | 61 | 173 C15 | 154 | 4575 | 4800 | 63 | 236 C16 | 158 | 4575 | 4750 | 63 | 191

Anonymous

Same here. Tuning etc. works perfect but if the app is opened in the foreground cpu usage on a single core goes to approx. 5% and minimizing doesn't fix. If opening and goes straight to taskbar then cpu usage is < 0.5%. But if maximized, cpu usage on same single core is back to 5%.

Anonymous

Maybe it's a collision with hwinfo. It's been about a day since I stopped hwinfo, but there's no problem.

Anonymous

I have the same problem. During the diagnosis, the voltage does not rise further to the maximum value of 1.375 It is applied by manually setting the cpu voltage in the profile. I use asus b550 tuf pro.

Anonymous

So guessing by the silence, the bug that does not finish the diag test won't get fixed until next month release right? Just asking because when you have to wait a month to use the program because of a bug that needs fixing after they told you to erase all settings as they are no good any longer... well it does start getting annoying to spend hrs to repeat the diag for old version, to then spend another few hrs to re run on the fixed version. Communication, a little info goes a long way but so far since release the bug is out there but no official word as to what, why, when, or how? so yeah a little info would be good...

Anonymous

i am getting an error when testing CO (CCD) 18:51:30: CO (CCD) test started! 18:51:40: CMD_FAILED 93 Phoenix deactivated!

Anonymous

Is there a reason a 5900x shows core quality all at 100?

Anonymous

Since the "FREQUENCY LOCK mode" is enabled by default, I just run the diagnostics. At the end I reached the PPT limit, which I just slighty raised to 180 W. So here are my results:

Anonymous

ве бест!!!

Anonymous

майнит рапториум на водянке до 9000 H/s :)

Anonymous

R5950X

Anonymous

правда на охлаждении стоит 6 нукт по 3000 оборота каждый и холодно уже...

Anonymous

I want to shob my Rozen 5950x raised to 1000000000 H/s Raptorum can you?

Anonymous

Couple of quick questions now that I'm more familiar with the interface. 1- In CTR, I was able to plug in a voltage for P1 / P2 / PX HIGH etc and have the system calculate the CCD1 and CCD2 frequencies - how can I accomplish the same in Hydra? Would be nice to have a "?" within each row button to quickly find it. One for 1T-2T, another for 3T-4T etc 2 - Irrespective of whatever voltages/frequencies I have - I assume my calculated CO is primarily determined by my individual CPU and cooling setup - I should be able to alter my voltages in point 1 (either up or down) and still use the same CO ?

Anonymous

Юрий, можно русифицировать интерфейс? И будете ли делать тюнинг памяти для apu, 5600G/5700G? Попались настолько дубовые плашки дуалранки,что не работают на своём xmp. Сделайте пожалуйста русский мануал!