Overclock.net banner
201 - 220 of 322 Posts
we have a new update 1.3G
CHANGELOG:

  • CHECK TIMINGS (DCFR tab) function that allows you to check the set timings or the timings you plan to change for JEDEC rules and optimal overclocking. The color indication will allow you to visually determine which timings are optimal (green), sub-optimal (yellow) or critically (red) wrong. In the next update it is planned that this assistant in addition to the color indication will tell you what value should be set. Works for DDR4 in the range of 3600-3800 and DDR5 in the range of 5600-6200 MT/s.
  • DDR5. All presets got another important information field - CPU VDDIO/MC. This is one of the most critical voltages for memory stabilization.
  • DDR5. Added normal and fast presets for Hynix A-die.
  • DDR5. Added normal and fast presets for Samsung B-die.
  • DDR4. Added fast presets for Samsung B-die.
  • DDR4. Added normal and fast presets for Hynix CJR and DJR.
  • DDR4. Due to the fact that the timing of RCDRD significantly depends on the luck of the sample, I made a note in the presets (in brackets) that maybe if it is not stable you should use a higher value.
  • A number of edits and innovations to existing presets.

KNOWN ISSUES:

  • Zen 3 APUs refuse to change CO during CPU diagnostics.
  • The active iGPU in Zen 4 can cause problems with RX-TUNER or GPU diagnostics.
  • The found COs for some processors can be 2-4 steps more optimistic than in reality. Additional testing algorithms are being developed.
  • Some DRAM presets require additional testing.
 
we have a new update 1.3G
CHANGELOG:

  • CHECK TIMINGS (DCFR tab) function that allows you to check the set timings or the timings you plan to change for JEDEC rules and optimal overclocking. The color indication will allow you to visually determine which timings are optimal (green), sub-optimal (yellow) or critically (red) wrong. In the next update it is planned that this assistant in addition to the color indication will tell you what value should be set. Works for DDR4 in the range of 3600-3800 and DDR5 in the range of 5600-6200 MT/s.
  • DDR5. All presets got another important information field - CPU VDDIO/MC. This is one of the most critical voltages for memory stabilization.
  • DDR5. Added normal and fast presets for Hynix A-die.
  • DDR5. Added normal and fast presets for Samsung B-die.
  • DDR4. Added fast presets for Samsung B-die.
  • DDR4. Added normal and fast presets for Hynix CJR and DJR.
  • DDR4. Due to the fact that the timing of RCDRD significantly depends on the luck of the sample, I made a note in the presets (in brackets) that maybe if it is not stable you should use a higher value.
  • A number of edits and innovations to existing presets.

KNOWN ISSUES:

  • Zen 3 APUs refuse to change CO during CPU diagnostics.
  • The active iGPU in Zen 4 can cause problems with RX-TUNER or GPU diagnostics.
  • The found COs for some processors can be 2-4 steps more optimistic than in reality. Additional testing algorithms are being developed.
  • Some DRAM presets require additional testing.
All it needs now is adding DDR4. presets for Samsung E -die.
 
It seems like MSI doesn't have a CPPC option available in their BIOS. I have 3 of them (x470, x570 and b650), and all 3 have the same issue with "cppc tags are not available".
Any ideas on what to do with it? Other than moving to another vendor.

P.S. Win 10 on all systems, latest drivers, latest BIOS etc
 
After windows update today now I get cppc tags not available message and even uninstalling the update doesn't help... Why is it broken all of a sudden?

Windows 11 latest version
Asus X570 Crosshair Dark Hero
Ryzen 5800x
All drivers etc up to date
 
Hydra keep saying unable to set GPU parameters when i apply any change in to RX-tuner page. Anyone have the same problem as I do?
I am having a B350 chipset. Will this be the problem?
View attachment 2615312
View attachment 2615311
there is another 4 updates the last is 1.3G maybe fix your problem but your chip from mobo is very first and
some incompatibility only you make some test with last edition
 
Hey, i have a 5800x3d and using 1.3G but when i try to run diagnostics it tells me it can't create a profile?

I had used it previously on a 5900x and was able to create profiles no problem, but since switching to the 5800x3d i haven't been able to.
On latest bios and chipset drivers.
maybe dont support 5800x3d you send a email to usmus and ask him
 
Well i want to check if other users have the same issue or if i'm missing something before going directly to 1usmus. does usmus respond to emails? i assume he is busy and doesnt have time to resolve issues 1on1.
plus when i searched for this issue this thread is the only thing i found, so if other users have a similar issue they could find this thread to see what the issue is. it would stop him getting bombarded with emails asking the same question :)
 
Well i want to check if other users have the same issue or if i'm missing something before going directly to 1usmus. does usmus respond to emails? i assume he is busy and doesnt have time to resolve issues 1on1.
plus when i searched for this issue this thread is the only thing i found, so if other users have a similar issue they could find this thread to see what the issue is. it would stop him getting bombarded with emails asking the same question :)
the most logical thing is that since HYDRA PRO it is not free, it should answer you
 
we have update 1.4A PRO
CHANGELOG:
MISC
  • You choose where to minimize the application at OS startup: tray / taskbar / none (settings tab).
  • Overriding best core - stability and performance update.

CPU DIAGNOSTIC
  • It is possible to export (synchronize) AMD CO values from the AMD PBO2 tab to the dialog box with CPU diagnostics settings. The assistant asks.
  • The user will now have the ability to perform individual types of diagnostics so that time is not wasted on unnecessary diagnostic steps.
  • It is now possible to skip the raw AMD CO value search and go straight to the value verification. The assistant asks.
  • CPU diagnostics now checks for WHEA events.
  • Extra tests for CPU diagnosis have been added.
  • Increased speed and accuracy of CPU diagnostics. The first phase is a quick search for "raw" values, the second phase is a detailed verification.
  • Changed preset settings for CPU diagnostics.
  • Introduced a concept as Target VID - the maximum VID value that can be used by the diagnostician to search for HOC CO and create a 1T-4T profile. It affects the stability of HYBRID OC.
  • Fixed bug when system detecting wrong FFT value falsely stopped CPU diagnostics.
  • Alerts the user to background activity that negatively affects the accuracy of CPU diagnostics.
  • To avoid false detection of the error, the Prime95 log is deleted before each test run.

DCFR
  • New presets for DDR4 memory that is already in the app: 2*8 3866, 2*16 3866, 4*16 3600.
  • New presets for DDR5 memory that is already in the app: 2*16 6400.
  • Adjusting the rules for the CHECK TIMINGS function.
  • Fixed bug of incorrect RCDWR reading.
  • CHECK TIMINGS now logs the recommended values for the timings if the user wants to enter a completely unspecified timing value.
  • Unlocked management of some voltages for DDR5 memory.

GPU CONTROL
  • Enabled iGPU now does not block RX-TUNER operation.
  • Fixed a bug where adding or removing a new RX-TUNER profile did not deactivate the current profile switching process.
  • Added entry level monitoring for RTX and GTX graphics cards.
  • Added RTX/GTX-TUNER entry level. The user can manage CORE and VRAM offsets, temperature and power limits ,CORE voltage control.
  • Fixed bugs, which did not allow RX 7000 videocards to monitor and diagnose correctly.
  • Fixed a bug where RX-TUNER could not control multiple adapters at the same time. Note that the latest AMD drivers may block the use of multi-gpu.
  • Changed the default GPU diagnostic settings. In particular, it is recommended to use 4K resolution for reliable results.
  • GPU diagnostics now works better due to catching single artifacts. Accuracy has been improved.
  • Fixed critical bug when HYDRA could not show any data after video driver crash, also HYDRA knows how to notify if video driver is damaged.
  • PHOENIX for GPU diagnostics now works properly (was previously disabled due to a change in diagnostic algorithms).
  • The PHOENIX WAKE UP! function also works to diagnose graphics cards.
  • Fixed bug when starting GPU diagnostics did not save disabled profiles state in RX-TUNER.
  • Added setting the duration of the VRAM test. 0 - do not test.
 
201 - 220 of 322 Posts