HYDRA 1.8H PRO (BIG UPDATE) - RELEASED!

Hey, everybody! :)
Glad to present the biggest monthly update ever. Thousands of lines of code and hundreds of hours of testing. The list of changes is over 50 items and I'm sure I've forgotten something.

So, let's get started.

1. DRAM diagnostics for DDR5 have significantly evolved. Tables and guidelines have been developed that provide users with starting values for a range of settings. For example, for timings, there is a dependency on the DRAM IC, MT/s, and DRAM VDD. By changing one of these settings, HYDRA offers suggestions on which settings to begin searching for optimal timings. Additionally, HYDRA knows the theoretical limits of the timings based on the currently selected DRAM VDD. By adjusting the MT/s, you can see how the FCLK frequency and Nitro values change. This highly flexible system is designed to simplify the lives of both novice and experienced overclockers.

Never done timing optimization? With HYDRA, it will be simple. Reset the BIOS settings to Auto and disable Context Restore. Then, in the HYDRA main menu, navigate to SCAN (where diagnostics for various system components are located). Select the DRAM IC (the type of chips in your memory), set the desired MT/s, and choose the DRAM VDD. Everything else will be handled automatically.

During the timing optimization process, the system will continuously reboot. This is normal. In case of instability, HYDRA will revert to stable values and continue the optimization process for the next group of timings.

As a result of the procedure, all components of the memory subsystem will undergo undervolting, provided you have not disabled this feature in the diagnostics settings.

2. Have you completed DRAM diagnostics or found a new preset on the forum? Great, then let's test its effectiveness. To do this, I have updated the built-in benchmark called DRAM BENCH (located on the TESTS page of the main menu). Unlike AIDA and other benchmarks we are accustomed to using, the set of tests in DRAM BENCH is capable of assessing real performance, not just theoretical.

Let me give you an example. I had an tweaked EXPO, but I became curious whether performance would change if I further tuned the timings. Running tests in AIDA, I obtained identical latency and bandwidth, which might disappoint anyone. But is that really the case? By benchmarking two presets in HYDRA, I achieved results that were actually surprising.

MemBench demonstrated a 6.75% performance increase, meaning that certain sequences of tasks executed by the processor were faster.

Bandwidth metrics for a single core improved slightly, but the copy value for an entire CCD changed significantly. Will this affect games? Absolutely.

You can also see a substantial change in Random Access Rd/Wr metrics, which will also impact, for example, frame rate smoothness in games. By the way, this is a new benchmark that evaluates the performance of random accesses to DRAM when working with data volumes that exceed the cache memory.

A few words about the interface. In the center of the screen is a graph showing the core's access time to different memory regions, ranging from cache memory to DRAM. For ease of understanding, the regions are separated by different colors. At the top of the page are the current memory settings. At the bottom of the page are the test results. If you see a value filled with color, it means you have entered the comparison mode between the current and selected experiment. If desired, you can scroll through experiments using the up and down arrows. Alternatively, you can simply delete the experiment data by clicking on the trash can icon. It's all quite simple—just give it a try.

3. Another equally interesting test suite introduced in this update is PING PONG. It is designed to evaluate inter-core communication, specifically how quickly a core from one CCD can communicate with a neighboring core or with a core residing on another CCD. This test suite can highlight architectural weaknesses that affect the utilization of all cores under high-intensity workloads or simply the quality of FCLK-CPU overclocking.

The interface is very similar to DRAM BENCH, but in this case, instead of selecting an expert, you can select metrics.

4. A significant amount of time has been spent improving existing modules and functions; you can find the complete list in the changelog. From this list, I would like to highlight that NVIDIA GPU diagnostics have received an improved algorithm that generates curves more accurately. APPE now features multilingual localization, a conflict search function with PCI mutex, and enhanced file storage. Consequently, due to the improved file integrity of Phoenix, diagnostics for any component have become more reliable.

CPU/GPU PROFILE COMPATIBILITY WITH THE PREVIOUS VERSION?

- YES, ANY VERSION

ONLINE-GUIDE (1.6A) :

LINK

CHANGELOG:

* "Check conflict" ("LOGGING" tab) now detects more processes and services blocking the "PCI mutex".
* Experimental support for RTX 5000 series.
* Added "Nitro" control on the "DCFR" page for DDR5.
* Improved the storage system for all types of HYDRA files, including "phoenix".
* Added "Performance Bias" control via Windows (on the "Settings" page).
* HYDRA has removed a number of drivers written by third-party developers (now using only its own).
* CPU diagnostics: "Target VID" does not want to accept the value.
* CPU diagnostics: Fixed a rare bug that could cause a boot loop.
* CPU diagnostics: Some CPU were not allowed to be diagnosed. Fixed.
* GPU diagnostics (NVIDIA): Added a dual "non-RT/RT" test with automatic resolution adaptation to the main screen for more accurate results.
* GPU diagnostics (NVIDIA): Various improvements related to curve building.
* GPU diagnostics (AMD/NVIDIA): Fixed a bug where user changes in "GPU DIAGNOSTIC CENTER" could be ignored.
* CPU and DRAM (DDR5/DDR4) diagnostics: Improved system for pausing/resuming diagnostic processes.
* CPU and DRAM (DDR4/DDR5) diagnostics: Improved recovery of processes from "phoenix" files.
* CPU and DRAM (DDR4/DDR5) diagnostics: Improved failure type detection and "phoenix" branching after different types of failures.
* DRAM (DDR4/DDR5) diagnostics: Added "VT3" test to diagnostics for more accurate results.
* DRAM (DDR4/DDR5) diagnostics: Fixed a bug where diagnostics could end prematurely.
* DRAM (DDR4/DDR5) diagnostics: Fixed a bug where the HCI test completion percentage was displayed incorrectly.
* DRAM (DDR5) diagnostics: Added an automatic tuning option for "ProcODT" and "DramDqDs".
* DRAM (DDR5) diagnostics: Added an undervolting option for "MC VDDIO".
* DRAM (DDR5) diagnostics: Extended "DRAM MT/s" range to 8800 in 1:2 mode and 6800 in 1:1 mode.
* DRAM (DDR5) diagnostics: Extended "MEM VDD" range to 1.55V.
* DRAM (DDR5) diagnostics: Extended "MEM VDDQ" range to 1.45V.
* DRAM (DDR5) diagnostics: Extended "SOC VDDCR" range to 1.3V.
* DRAM (DDR5) diagnostics: Extended "MC VDDIO" range to 1.4V.
* DRAM (DDR5) diagnostics: Extended "CLDO VDDP" range to 1.15V.
* DRAM (DDR5) diagnostics: Added "Nitro" settings (presets for best performance/latency or stability).
* DRAM (DDR5) diagnostics: Added automatic "ODT" search (ProcODT/ProcODT PU and DramDqDs).
* DRAM (DDR5) diagnostics: Automatic adjustment of start timings for any "DRAM MT/s", "MEM VDD", and "DRAM IC" (all dependencies are taken into account).
* DRAM (DDR5) diagnostics: Updated performance tests for each tuning step (optional).
* DRAM (DDR5) diagnostics: A number of bug fixes and start value adjustments.
* DRAM (DDR5) diagnostics: Added new tips.
* DRAM (DDR5) diagnostics: When the user selects "DRAM MT/s", a number of additional settings affecting stability are also changed (HYDRA suggestion).
* DRAM (DDR5) diagnostics: Modified UI for faster selection of new values and settings.
* DRAM (DDR5) diagnostics: Warning system for unsafe voltage use.
* DRAM BENCH: Added infinite history (file-based storage).
* DRAM BENCH: Added timing and configuration information.
* DRAM BENCH: Added the ability to compare settings and results between different experiments (user selects from a dropdown list).
* DRAM BENCH: Added the ability to browse experiment history and delete selected entries.
* DRAM BENCH: Added the "Random Access Rd/Wr" sub-test.
* DRAM BENCH: Added the "CCD DRAM Rd/Wr/Cp" sub-test.
* DRAM BENCH: Adjusted the "MemBench" sub-test starting values for 12-core and 6-core processors.
* Added the "PING PONG" test ("TESTS" page) with various metrics (MIN/MED/AVG/P95/P99/MAX), which measures the real latency of communication between cores.
* "CHECK MY MEM" ("TESTS" page) received an additional "VT3" test for DRAM stability checking.
* "CORE C6" and "PACKAGE C6" settings ("Settings" page) no longer require restarting the application.
* "T-CONTROL" now also manages the C6 state of cores, improving performance and particularly reducing P95/P99 events.
* Added an alternative method for determining CPPC core labels for Zen 3.
* "HYBRID OC" received minor stability improvements.
* Fixed a bug that prevented HYDRA from launching if there were no dGPU in the system aside from iGPU.
* "APPE" now has multilingual support.
* Added support for 4-byte settings in "APPE".
* Other minor fixes, stability improvements, and refactoring.
* "CMD_FAILED 51 0" - you will still see this message, but it will not stop any process.
* CPU monitoring on some systems did not work properly and therefore everything broke down because of it. Fixed.
* Increased the maximum "VID" threshold for the 9800X3D, it is now 1325 for the "LT profile" and 1225 for the "MT profile". The reason for such a strict limitation is that I don't consider AMD's standard limit to be safe.
* Further protects "Profiles Table" from a user attempting to enter a "VID" value that is too high.

KNOWN ISSUES:

* False positive of antivirus (like always).

DOWNLOAD:

LINK  (only an early access plan)

Since piracy in recent months has become widespread early access will be in Discord. If you do not have access to Discord, make sure your Patreon profile is complete. The process of granting access is automated. Also note that pirate resources may add malicious software to the archive. Use only a proven resource.

VIRUSTOTAL:

LINK