Fiery

We've added your motherboard to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta

We've fixed that issue in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

We've implemented further tweakings about AMD GPUs in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

We've implemented further tweakings about AMD GPUs in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

Since noone else with a Gigabyte motherboard similar to yours reported issues like what you've been experiencing, I have to assume that your motherboard has issues providing sensor readings in a constant and reliable fashion; or there's a software running on your system that interferes with AIDA64. BTW, incidently we have the same motherboard than yours and on our sample we also cannot reproduce your issue.

Thank you for the data. Please give us a few more days to fix this issue. We're currently waiting for our 980 Pro SSD sample to investigate this further.

In your particular case the bottleneck is your motherboard's capabilities about maximum supported memory frequency. If your motherboard cannot handle anything above 2666MHz or 2933MHz, it doesn't matter if your memory modules can -- theoretically -- do 3000 or more. And BTW, make sure to run the stress test for at least a few hours before deeming a certain system configuration or setting stable.

We've checked, and it should work as long as DIMM thermal sensor support is enabled in AIDA64 / main menu / File / Preferences / Stability. Are you sure it is enabled there?

That's a bit clumsy, I admit. But I think they should appear after an initial value is assigned to them in the Registry and you open the Preferences window again. Or maybe after you restart AIDA64 Polling and re-enumerating system values can be quite time consuming and is avoided to be done again at each time you click through Preferences windows. Before, when it was more dynamic, the re-enumeration process made the LCD configuration very sluggish and the user experience became terrible in many cases.

I suspect that this is related to a USB storage device that AIDA64 polls (or try to poll) for SMART disk drive temperature measurement. Try to go to AIDA64 / main menu / File / Preferences / Hardware Monitoring, and disable (uncheck) Enable disk temperature measurement. Restart AIDA64 and check if it makes the tones go away.

Not at all, we don't have a problem with Corsair products. What we do have is constant issues and headaches about Corsair's policy of blocking out 3rd party software developers from accessing their hardware concurrently with their own software (iCUE). Another issue is the firmware stability problems of AXi Series PSU's, as well as the market availability of certain 2nd generation lower priced AXi PSU's. Since we have to pay out of pocket for each of those Corsair products that we need to work on, we simply can't afford to purchase the highest-end and most expensive model. Sadly nothing else seems to be available on the market than AX1600i which is bleeding expensive. We'd be happy to continue investigating the issues related to 2nd generation AXi PSU's in case we could get our hands on one.

Yes, it's actually normal: on modern PC's using just one memory module per memory channel could help to stabilize an otherwise problemous configuration since it puts less stress on the memory controller.

I'm afraid it's not possible to access DAC chips in Android devices.

Your motherboard isn't capable of monitoring those readings.

Thank you for the data! I'm afraid we cannot find any sensor readings among those registers. This sadly is the case with most laptops, so it's not just yours but most of them out there. Only Clevo (the original manufacturer of your laptop) would know what registers can be used for fan monitoring, but usually those companies wouldn't reveal such technical details with anyone.

Asus RGB devices are currently supported through the Aura SDK. We do have direct support (that doesn't require Aura SDK) for Claymore keyboard and Gladius II mouse. If you have other Asus products than these two, please let us know and we'll check if we can implement direct support for them.

The best place to look for those is:

Try to lower memory frequency and/or set the memory modules to work at 2T Command Rate (tCR or tCMD).

What motherboard and video card(s) do you have? Are you using AIDA64 v6.32 (latest version) ?

No problem at all, AIDA64 quite a complex piece of kit. Some call it a Swiss Army Knife for your PC

You can see a more precise and dynamically updated BCLK reading on the Computer / Overclock page. You can adjust the number of decimal digits for clock frequency readings at AIDA64 / main menu / File / Preferences / Hardware Monitoring / Decimal digits for clock speeds.

We've tested it with Catalyst 12.4 WHQL + Windows 7 32-bit + HD4670, and it worked flawlessly for us. Have you tried to re-install your video driver and update the motherboard BIOS?

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, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

You can use the Registry for that purpose. Put your values into the following Registry path: HKEY_CURRENT_USER\Software\FinalWire\AIDA64\ImportValues Name them as Str1, Str2,... Str10 to have 10 string values imported to AIDA64. Name them as DW1, DW2,... DW10 to have 10 integer (DoubleWord) values imported to AIDA64. If you place a value to one or more of those Registry entries, the values will get listed among the other sensor items for LCD, OSD Panel, SensorPanel, etc.

What GPU do you have in your laptop? Do you have the necessary video driver installed?