Fiery

Well... It was a very stupid mistake. I was lazy to properly assemble a PC, and left the SSD on top of a HDD. I thought after installing the OS and drivers, I'll remove the HDD and install the SSD in its drive bay. The two device heating themselves up ended up in a disaster, even though it was only for a few hours...

Thank you for your feedback

Thank you, we'll add VCCST (VCC Sustain) voltage to the next AIDA64 beta

Once I've had a SSD heating up over 100 Celsius, and that killed it. Not immmediately, but shortly it just died. I'd definitely get Corsair's take on the subject. If they fail to respond in a few days, then I'd get a refund and look elsewhere.

Can you see the missing set of voltages in the UEFI Setup or in ASRock's own monitoring software? As for the PCH temperature, we will add it in the next AIDA64 beta update due next week. We will also check how to detect the chassis intrusion state.

Amazon sells illegal (pirate) AIDA64 license keys. We've already notified them about this, and they said they're investigating the fraud. If you bought a license at Amazon, make sure to ask for a refund ASAP.

On the SensorPanel and also LCD devices, you can enter "Mbps" into the unit field to make it the measurement unit. Let me know if you meant a different place in AIDA64. In which case please let us know on what page or in which module do you see the MB/s measurement unit. Regards, Fiery

I suppose Corsair's own SSD software doesn't support NVMe drives yet. Hopefully in a few weeks they can get that done, along with a new firmware for the MP500 family. As for the operating temperature, I suppose they mean ambient temperature there. If not, and it's actually the operating temperature range of the MP500, then the drive may be working out of spec under heavy stress/load... According to our test runs, the MP500 heats up to 70+ Celsius when there's a heavy flow of outgoing data (ie. copying a lot of large files to the drive).

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

The mentioned new AIDA64 beta update is now available for download at: https://www.aida64.com/downloads/latesta64xebeta

Thank you. We've added a new synchronization mutex to make sure AIDA64 works properly with other monitoring software running simultaneously. We've notified the authors of HWiNFO, HWMonitor and SIV about this issue. It's now up to them to implement the same mutex. Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta

We've added a right-click menu option for the Sensor page to let you disable the extended labels. Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta

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 how it works

No need to do that. The issue will be fixed in the next AIDA64 beta update due to be rolled out in an hour or so I apologize for the late response.

No, the temperature is really that high. MP500 runs very hot even at idle. I'm not sure why, but I'm sure Corsair knows about it.

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.