Fiery

Thank you! Please upgrade to 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'll implement Gbps and GB/s unit conversion in the next AIDA64 beta update

I'm not sure what your customers would do with the attached TXT file. Would they save it to somewhere on their phone? If yes, then finding it afterwards could raise the same difficulties than when the report is saved to file directly from AIDA64 IMHO. Can't they simply email the report directly to you? Or forward it from e.g. Gmail when they receive the email that they sent to themselves? BTW, am I right in assuming that the OS of choice there is Android? I'm just asking because we have multiple mobile apps covering all mobile platforms available out there.

Thank you for your feedback!

That would be great as a test. Thank you in advance! Meanwhile, we've ordered an EK-Loop Connect device in order to help us do more research. I'm not sure however if it's gonna be V1 or V2 of the device. Do you know how to recognize device version, and what the differences are between the two versions?

Yes, on your motherboard all 3 temperature readings (Motherboard, CPU, Aux) should reflect a correct measurement.

What version of AIDA64 are you using? And what chipset and CPU do you have in your notebook?

It's a complex thing to monitor and report, but we'll do our best in the remaining part of the year to make it happen.

Thank you! We'll fix the reporting of VCCIO voltage on Asus ROG Maximus XII Series motherboards in the next AIDA64 beta update.

It's not AIDA64, but Winsock.

I understand that it can be difficult to handle NICs these days, but the whole reason behind that is that Windows 10 itself manages NICs that way. They can appear and disappear, their order can change dynamically, virtual NICs here and there, etc. etc. With such a dynamic scenario anything you configure as a fixed setting can change on-the-fly. I'm not sure how could AIDA64 follow that automatically...

It could be a collision between the polling activity done by AMD's video drivers and AIDA64. It's very difficult to handle that issue without proper help from the driver itself. Later AMD video cards (based on Vega and Navi) has a special video driver call that can be used to avoid such issues. With older video cards it's still a hit & miss, and it's difficult to find a proper way to avoid the problems. Other than giving up on GPU monitoring (AIDA64 / main menu / File / Preferences / Stability / GPU sensor support)

Thank you for your feedback!

We've figured out the protocol using proprietary tools.

That particular motherboard has a very bad sensor implementation that is very difficult to handle. And with that it's quite easy to have the sensor access collide between AIDA64 and the BIOS We haven't found a perfect solution for the issue that would work with all BIOS versions of your motherboard. But, you may want to try enabling Asus WMI sensor support in AIDA64 / main menu / File / Preferences / Stability and restart AIDA64 to apply the changes in case you have your motherboard updated to the latest BIOS. If that layer (Asus WMI ACPI sensors) works correctly with your motherboard, then collisions along with pump stopping or fan stopping issues wouldn't occur.