Fiery

Please ask them to contact us. We're in contact with them already about different issues, but lately they seem quite swamped and we can rarely get a useful feedback from them Hopefully they get back on track soon. We would of course be more than happy to assist by providing them with the necessary technical information on the synchronization mutexes. Such mutexes are already implemented in a wide range of 3rd party monitoring, tuning and tweaking software like AMD OverDrive, CoreTemp, CPU-Z, EVGA E-LEET, GPU-Z, HWiNFO, HWMonitor, MSI AfterBurner, Rivatuner, SIV, SpeedFan, etc. etc. So by implementing the mutexes in Aquasuite they can not only ensure it would work more reliably with AIDA64, but also with all the other listed software that implements the same mutexes.

It sounds like a collision between Aquasuite and AIDA64. Please ask Aquacomputer to implement the necessary synchronization mutexes, to ensure it wouldn't collide with AIDA64 and other monitoring software.

That's quite normal. Battery charge rate measurement has to be implemented on each platform, by the manufacturer of the device. Some manufacturers are very thorough about this, and they implement it for every device they make, while others only implement it on a certain range of devices. It's a mystery why they leave certain devices out, while they care to implement battery charge rate on others...

The mentioned new AIDA64 beta update can be downloaded from: http://www.aida64.com/downloads/latesta64xebeta

The mentioned new AIDA64 beta update can be downloaded from: http://www.aida64.com/downloads/latesta64xebeta

I don't think that log file is associated with our app (AIDA64) in any ways. Regards, Fiery

It still works fine on our test systems running Win10 64-bit TH2. Are you on the Win10 stable channel (TH2), or on the Insider Preview channel (RS1) ?

I've just sent you an email about this issue. Thanks, Fiery

Thank you, we will rename Temperature #4 to DIMM temperature in the next AIDA64 beta update due in a few days from now

Thank you, the issue will be fixed in the next AIDA64 beta update due in a few days from now.

Please note that we've ordered az Aquastream Ultimate device that should arrive in 1 to 2 weeks from now. We'll push our luck to find out how monitoring works on the device. We should be able to solve at least the basic readings without help from Aquacomputer. I'll let you know how it goes

Thank you for the feedback

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. Please also let us know exactly which fan label should be renamed, and what the correct label is supposed to be. Thanks, Fiery

We haven't heard back from our contact at Aquacomputer yet

Thank you for the data. We've already added your motherboard in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

Thank you for the feedback. Do you mean the temperature reading that is now (with the latest AIDA64 beta) labelled as Temperature #4 ?

So far we haven't seen strong demand for such a special feature, so we have to focus on other issues.

Thank you. That reading is just a bogus value. We'll remove it in the next AIDA64 beta update.

Thank you for the feedback

The mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta Please let me know how it works

The mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta Please let me know how it works

The mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta Please let me know how it works

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. Thanks, Fiery

It depends on how CAM works. If it keeps the last fan duty cycle setting active after you close it, then it should be fine. However, in case it restores the fan speeds to a fixed 100% when you close it, then it's quite a bad implementation

Have you tried to restart Windows? Do you have any special devices connected, like a USB external hard disk drive or such?