Home
Creators
Search Recent Random
Posts
Search DMs Popular Hash Lookup Tags Random
Importer
Import FAQ
Filehaus
Recent
Register Favorites Keys Review DMs Logout
Home Creators Posts Import Register Favorites Logout
Click here for site announcements

HYDRA NEWS! (Patreon)

Published:
2021-08-07 21:18:01
Imported:
2026-06
haven't archived this post yet. have a subscription? use the importer!

Content

Got the 5600G today and HYDRA will get support these processors this month. Also a massive update will be released next week with all profiles (+ dynamic mode), "real-time CO bottleneck info" and "standby cache cleanup" feature. 

Files

Previews only

Comments

Tom Parkinson

Thanks for the constant updates and enthusiasm, Yuri! My 5900X is in a very happy place and has settled in nicely to Hydra so far. Looking forward to future releases!

84wayz

That sounds great :). Yuri I'm always thankful of the hard work you put in to these releases. I'm loving being along for the ride and testing this 5900X. I'll try HYDRA again on the massive update next week. For now, i was getting a lot of reboots and freezes, so I went back to CTR 2.1 V.20.

Anonymous

Looking forward to the next release! My 5900x has been running great and cooler for sure so far!

xgfancz

Has the Dram Calсulator for Ryzen stopped updating?Whether to support 5600G/5700G??

Koen Dijker
>>65394037

I would like to see an updated DRAM Calculator as well. I have troubles system (memory, CPU and mainboard) stable. I run a 5900x with b550 and 32GB Patriot Viper (B-die). Memory tests proof only stable IF @ 3733 CL16-16-16-32-2991.35 mV. Up to 4000 CL16-16-16-32-300 1.40-1.45mV did run stable except for the IF. Despite memory tests and stabilty tests run fine the system suffers from delays and caching errors in windows though. And I do find the stable IF far too low. It takes a lot of time to manually tweak this, DRAM Calculator was always nice as a reference.

derps derpington

When I run Diagnostic against my 5950X, I always get a "CORE test exception" when the test gets to C09. System.ComponentModel.Win32Exception (0x80004005): The parameter is incorrect at System.Diagnostics.Process.set_ProcessorAffinity(IntPtr value) at A.cc71f47d00b9f9b057530eb17539f5c33.cd643dc54d4404be34eb08adf49006554.MoveNext()

1usmus
>>65622442

Hi! You have SMT disabled, but I also fixed the problem in a future update.