Fiery

1) AFAIK your motherboard cannot measure VRM1 or VRM2 temperature. 2) PCI-E #1 and PCI-E #2 should be located around the PCI-E slots of your motherboard, but only Asus knows where exactly they placed the diodes corresponding to those readings. Temperature #1 is the temperature reading Asus calls "VCORE". Temperature #2 is the temperature reading Asus calls "VCORE (Back)". 3) We've noticed the same anomaly about our MP500 SSD. We've checked, and it seems to be due to a firmware issue that Corsair has to fix. Make sure to ask Corsair Support about this. Regards, Fiery

You can have AIDA64 Extreme installed on up to 3 computers at any given time. If you replace your PC, you can uninstall it from the old one and install it on your new one, without adding a license to your limit of 3. Regards, Fiery

Thank you. How many fans do you have connected, and which fan headers do you use? What I can see in the dumps is that your motherboard has 3 fans connected, labelled as Chassis #2, Chassis #3, Chassis #4. Maybe the number of monitored fans is correct, but their labels are incorrect?

Thank you, and no worries about the mentioned post Thanks for the dumps! What I can see there is that the Corsair RMi and Aquaero monitoring methods take quite a bit of time to complete. It's not 2 to 6 seconds, but more like 1 second per update. So that alone wouldn't explain the 2 to 6 seconds update rate you've mentioned in your opening post. However, it would still be interesting and helpful to try and disable the individual hardware monitoring modules, to see which one solves the slowness. You can disable the Aquaero and RMi modules if you right-click on the bottom status bar of AIDA64 main window --> HWMon Modules, and click on Aquaero or Corsair AXi / HXi / RMi. You don't need to restart AIDA64 to enable/disable those modules. Let me know how the behavior of AIDA64 changes when you enable/disable those individual modules. As for the matter of CL, as long as you have the latest version of Corsair Link software installed, you should have no issues running it and AIDA64 simultaneously.

If you have Asus AI Suite installed, then make sure to not rename the sensor values in there. Regards, Fiery

It's hard to tell, since we're not the developers of Task Manager or Afterburner We haven't changed anything about measuring CPU utilization, so it should still work 100% reliably under Windows 10. We're not aware of any change in the way Windows 10 manages CPU load that would render our method of measuring CPU utilization.

Thank you, we'll check if we can get ahold of the 2.xx version of the SDK, and update AIDA64. As soon as we have an update to this issue, I'll post a message into this topic.

To me that sounds like a classic CPU overheating issue Reseating the CPU heatsink should help. Regards, Fiery

That's exactly why such issues could happen AIDA64 simply can monitor more hardware components than most other software out there. But sometimes, digging deep and interrogating several sensor devices could cause inadvertent headaches. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling Dump. 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. Before creating that dump, it would be best if you could disable OSD Panel and restart AIDA64. Thanks, Fiery

Such issues may happen when you're running Corsair Link software in the background, along with AIDA64. First, try to update Corsair Link software to the latest version, and also update AIDA64 to the latest beta build: https://www.aida64.com/downloads/latesta64xebeta If it doesn't help, then you can try setting Asetek fan speed (in AIDA64 / main menu / File / Preferences / Hardware Monitoring) to the same fan duty cycle (%) value that you have configured in Corsair Link software.

Those banners only appear if you don't have a valid AIDA64 license. Regards, Fiery

What I was trying to say above is that you only need to watch CPU Package power, since the other 2 is included in that value

In order to enable such a feature, it would be necessary to re-render the SensorPanel 30 or more times a second, which would put quite a load on the system. And certain users already complain about the "high" (2 or 3%) CPU load that the monitoring and SensorPanel rendering layer of AIDA64 puts on the system. So I'm afraid we're not planning to implement the requested feature. Regards, Fiery

I'm afraid we have no plans to implement such a feature. Regards, Fiery

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. 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. Also 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 Thanks, Fiery

CPU Package should include GT Cores and IA Cores power. Regards, Fiery

The source of the reading is added because when you've got an external sensor device (e.g. Aquaero), it becomes tough to identify which temperature or fan reading comes from which device. "Motherboard" in this case means the reading comes from a sensor chip integrated on the motherboard. As for renaming, it's not planned for the Sensor page, since you can already do that with the OSD Panel, SensorPanel, LCD (etc). It's not convenient to use the Sensor page for long term monitoring purposes. It's there to let you have a quick overview of the values AIDA64 can measure. But in most cases you don't need all measurements, and/or want to rearrange or reformat the readings -- and that's where you would want to switch to using the mentioned AIDA64 modules (e.g. SensorPanel) instead. Regards, Fiery

Thank you We'll keep working on it in the next few beta updates.

Please check the latest AIDA64 beta of Build 4068: https://www.aida64.com/downloads/latesta64xebeta Let me know if it helps.

Thank you. Please let us know when your new build is ready. Let's hope it will solve this issue. If not, we'll keep hunting for the bug

In the latest AIDA64 beta, we've implemented a new option in the Preferences of System Stability Test. It let's you prevent your computer from going to sleep while the stress test is running. Make sure to 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. Regards, Fiery

Please check the latest AIDA64 beta of Build 4068: https://www.aida64.com/downloads/latesta64xebeta It should work better with X99 chipset based systems now, and hopefully will not force you to use the Refresh button

Thank you for the bug report. We'll build a similar configuration and try to reproduce the issue in order to fix it up.

Thank you for the info. Let's hope in the 2nd hardware revision ASRock can fix the issues about accessing the sensor chip under Windows. There's a good chance A-Tuning Utility doesn't support H270M Pro4 because of that hardware issue...

Make sure to 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.