Fiery

It's not quite easy since SPD memory module detection and IMC detection are two very different matters. Finding synergy or association between the results can be unreliable and not always trustworthy. So we better not go down that path.

We currently have no plans about a network benchmark.

Many fake Android devices can be revealed by sending a report from the System menu in email (to e.g. your own email address). That's because the detected information can be faked on the screen but now when the information is written directly to a report.

Please note that it's not possible to diagnose such issues remotely. You may want to take your phone to a local specialist and have it checked out.

Right-click on the label you'd like to remove --> Delete.

Thank you, we'll implement iCX3 support for your video card in the next AIDA64 beta update. I'll post a message into this topic once the new beta becomes available for download.

I'm not sure if I understand your display configuration. Please explain what displays you've got, how do you connect them, on which display do you use AIDA64, what module are you using to display those stats (SensorPanel? RemoteSensor? Odospace?), and which display stops working as expected.

I'm pretty sure B460M Pro4 supports XMP. If it's advertised like that but fails to work with XMP, then it's a BIOS bug that ASRock has to fix.

What we need to do is decouple those items that are quick and easy to re-enumerate to those that have problems about that.

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.

Thank you! 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 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 els

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.