Home Artists Posts Import Register

Downloads

Content

HYDRA 1.3C PRO is required to install the patch. Just replace the .exe.
Profiles with 1.3C are fully compatible.

Why is the patch called a test patch?
Full-fledged testing takes several weeks or even months. I determine its quality as a candidate for release.

CHANGELOG:

* New presets and configuration files for CPU diagnostics.
* Now there is a separate target temp to diagnostic the core, and a separate target temp to diagnostic all cores.
* Fixes some problems with inability to activate RMP on some cards. Nevertheless, I observe a strange behavior of RX graphics cards on W11, they have much worse performance than on W10.
* Improved granularity of some RMP settings.
* The conflict check button is on the LOGGING page.
* The PCI-mutex related problem will also go away. Significant improvement in the stability of the application and all modes if you use third-party monitoring software, RGB control and so on. I think many of you don't know that you have third party software installed that can slow down HYDRA's processes and crash the system.
* Checking Windows timers for correct operation of HYDRA. If something is wrong, the corresponding information will appear in the log.

VIRUSTOTAL:

https://www.virustotal.com/gui/file-analysis/N2I0YTRhNGQzMThmOGRjNDRkZjkwNWJmMmYyNDMwNGI6MTY3ODIyMzA0Mw==

Comments

Anonymous

Does anyone else have problem with the RX tuner? It seems to me that hydra will not recognize my GPU (6800XT)

Tyler Wilson

i too am experiencing RX tuner problems. with the patch i cant use the slider to go beyond 2660MHz for my 6900XT. prior i was able to go to 3000MHz

Tyler Wilson

im having problems but it recognizes mine just wont let me increase the core freq. past 2660MHz

Tyler Wilson

Verified that Hydra 1.3A allows me to set 2800mhz where the 1.3D will not let me set it past the 2660MHz i stated above. it is verified when running 3d mark time spy extreme and it effective speed is 2735MHz

Lloyd

This program is so weird!.. It crashed the other day - then I just happened to notice that some CO numbers were off, and that it was on an old profile, so there was no way to know if it is my new profile that is unstable or it’s just hydra sabotaging my efforts by automatically changing my profile... And it just did the same things again. Crashed, and it’s auto-changed the profile. It's completely out of order... Overclocking is hard enough without a program meddling with your profiles, and gaslighting you!... The only possible reason I can think of why it would do this is, I set it to auto-start when it was on that older profile, and that is somehow stuck in it's memory now?… Or it's written something in the registry that it shouldn't have?.. I can understand if it just turned the active profile off after a crash, but to just pick a seemingly random old profile to switch to (and leave on) is absurd.