Fiery

Yes, GPU-Z can do it, but we have no idea how it does it. We thought it does it via ADL, but it's not the case. We'll try to research more, but I can't promise anything at this time

AIDA64 is still capable of monitoring such voltages, but please note that not all motherboards are capable of monitoring such voltage rails. Or maybe you mean the BIOS Settings section of the Motherboard / BIOS page? It should still be there, although please note that BIOS Settings cannot be detected on all motherboards, but only on Asus motherboards and on ones that supports Intel XTU. Regards, Fiery

I'm afraid AIDA64 can only write the real clock to the Registry.

Please drop a message at our reseller ABSEIRA about this matter: info AT abseira.com (replace AT with @) BTW, the minimum package is 5 licenses for Business Edition, for US$79.95. Regards, Fiery

AFAIK there's no way to check the status of a HDD The best solution would be if HDD manufacturers made it possible to read SMART attributes (incl. disk temperature attribute) while the drive platters are not spinning. Technically, it would be possible, but no HDD manufacturer makes that possible

You need to raise the Disk temperature polling frequency in AIDA64 / main menu / File / Preferences / Hardware Monitoring to avoid AIDA64 keeping the drives awake. Regards, Fiery

The effective frequency for the current (actual) memory clock is displayed on the Display / GPU page.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. Based on the dump we can check what's wrong with the DIMM TS sensor module of AIDA64 and fix it up Thanks, Fiery

I'm afraid I cannot promise anything, since ASRock's fan mux solution is quite peculiar and tough to handle from 3rd party applications like AIDA64

I guess the difference come from the fact that AIDA64 displays the real clocks for DDR memories, not the effective clock. DDR(1), DDR2 and DDR3 memories run at half the advertised frequency, so e.g. a DDR3-1600 module is actually running at 800 MHz real clock. DDR4 and DDR5 modules run at quarter the advertised frequency, so e.g. a DDR5-3200 module is actually running at 800 MHz real clock. Regards, Fiery

Our reseller ABSEIRA will contact you shortly about this. Regards, Fiery

I guess 3-pin would be better, although we don't have first-hand experiences on 7-Volt fans.

Thank you for the screen shots. Discharge Rate is only available when the UPS switches to DC power. We'll check if it's possible to measure the power draw via Smart Battery API calls.

I've posted a reply to your other topic. Please avoid starting multiple topics for the same issue. This topic closed.

On Radeon video adapters AIDA64 can measure video memory utilization only under Windows XP. Do you have Windows XP on both your machines? Thanks, Fiery

It's not possible to reset your trial period, but you can request our Sales Department (sales AT aida64.com) to create a 30-day license for you that you can use to fully evaluate AIDA64. In your email to the Sales Department please specify the product you're interested in (AIDA64 Business Edition or AIDA64 Extreme Edition), your name, and your email address. BTW, you may need to enable RAID SMART support in AIDA64 / main menu / File / Preferences / Stability (and restart AIDA64) to activate disk drive temperature monitoring on your system. Regards, Fiery

We'll work on it Do you mean the Discharge Rate that is already reported in AIDA64 / Computer / Power Management page? If you mean something else, then please show us on a SIW screen shot if possible

I'm sorry, but we don't plan to implement FPS monitoring anytime soon. As for the rest (like Winamp, Skype, Media Player) I believe they're out of the scope of our software. Winamp, Skype and other 3rd party software should implement built-in support for G15/G19 LCD, or Logitech itself should provide a plugin in the Logitech G-Series LCD driver package. In fact, as far as I know, Logitech already provides support for at least Winamp, indicating the place in the song playing. Regards, Fiery

Maybe it was due to some other BIOS settings caused either EIST, C1E or C-States to become enabled without you actually enabling it. As for the gadget issue. Please explain it in more details. Do you use the Sidebar Gadget feature of AIDA64, or the SensorPanel? Does the whole gadget/window disappear, or it just stops listing the values? Thanks, Fiery

I'm afraid it's still the same issue. We've contacted Asus and requested permissions to gain access to their Thermal Radar programming manuals, but they're reluctant to provide such documentation to other companies. So we still have no documentation on the Thermal Radar hardware, and we cannot figure it out on our own If someone can explain how to activate the special Thermal Radar temperature readings without installing Asus Thermal Radar software, we would be glad to implement that in AIDA64. Regards, Fiery

I'm sorry, but we do not make custom Sidebar Gadgets for our software. But maybe another forum user would be able to help you out. Regards, Fiery

Please check it with other tools (e.g. CPU-Z) as well. Also, make sure to disable C-States support (in the BIOS Setup) as well, since that may also cause clock variation.

I'm not sure what's wrong with the computer you benchmark, but many hardware reviewers from review portals think AIDA64 as a diagnostic software, and the benchmarks it offers are very useful and properly represent CPU and memory performance: http://www.aida64.com/testimonials Maybe if you could show us actual screen shots of benchmark results obtained with AIDA64 would help. Make sure to also explain what system it is, and whether it is overclocked or not. Please note that the reference benchmark results are always obtained on non-overclocked and non-tweaked systems, to represent "out of the box" performance of average PC systems. Regards, Fiery

No, it won't ask for a reboot. But from now on, with the Automatic Update feature things will improve, since before the actual update takes place, AIDA64 will unload the kernel drivers to avoid such issues.

It's working, since at least 4 fans are displayed on your screen shot But as I've stated above, it's not possible to detect all fans, due to the ASRock fan mux logic.