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. 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?

Thank you, we'll fix the issue in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new beta is available for download.

Thank you, we'll fix the issue in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new beta is available for download.

AFAIK there's no way to automatically turn the frame on into a certain mode of use. This is a firmware limitation of the SPF device

Even if there are exceptions from the rule, it's still a rule. We simply don't want to show such information to users that obviously doesn't add up, that looks wrong or incorrect from the get-go. From day one we wanted to design AIDA64 to make it as user-friendly as possible. Not to overwhelm users with endless amount of information, not to show ridiculous or hard-to-understand readings. That's why we keep working hard to implement motherboard-specific sensor adjustments for example. In that process we remove those readings that look suspicious, that are obviously due to a non-connected sensor rail, etc. You could bring up a case on that too, like why don't we show a 128 Celsius reading for the 3rd motherboard temperature sensor input. Afterall, it is a sensor reading... Back to the actual issue. Let's say we implement the readings that don't add up. Why would you trust a reading that doesn't add up? Why would you want to monitor such a reading? It's like keeping a close eye on an obviously wrong +12V voltage rail reading that shows a fluctuating value between +7.2V and +8.5V. Why would you want to monitor that? As for the screenshot... Do you think it's possible that the +5V rail draws 0 Ampers? If you think it can be correct, then the whole calculation of adding up +3.3V, +5V, +12V and -12V power can be implemented in AIDA64 even if one of the rails indicate 0 Ampers. We don't do that right now simply because it doesn't seem to be correct, even if Corsair's own software shows it. If there's a firmware issue of measuring +5V rail current, and Corsair's own software is not prepared to properly handle it, then even CL Software can show nonsense But we here at FinalWire don't like showing nonsense.

Fan speed monitoring and fan control are 2 very different issues. AIDA64 uses Dell SMI calls to measure fan speed and temperatures on your device. Dell SMI has no special EC states or such, but it's a universal method that works similarly across devices. It may be possible to talk to the EC directly, but AIDA64 doesn't work that way on your device, so I cannot give you the EC states (or EC registers).

All I can tell you is that sadly it's quite normal with fan controllers and smart PSUs that the manufacturer supplied software collides with any 3rd party software that tries to talk to the device. So if you close CAM, it should work with AIDA64. If you keep both software running, AIDA64 readings can only be accurate in case CAM implements the necessary synchronization mutexes. 3rd party monitoring software like AIDA64, CoreTemp, CPU-Z, GPU-Z, HWiNFO, HWMonitor, SIV (etc) are all synchronized with each other to assure they wouldn't collide when talking to various hardware. Unfortunately most hardware manufacturers develop their own monitoring software in a way that they don't really care about 3rd party monitoring software. So they don't care about synchronizing their software with any other monitoring software out there. In case NZXT is the unique exception who would be willing to implement the necessary mutexes, we would of course be more than happy to work with them. Please note that the necessary job to do is merely adding no more than 10 lines of code to the existing CAM sources. So it's not a huge job, it's not even a sizable amount of coding necessary.

Sounds interesting. And also, it doesn't really make much sense Unless by removing some visual elements the JPEG image size falls under a certain limit where the device stops failing

It is possible of course. SPF-72H is one of the oldest SPF series devices, so it may not work as reliably as newer models like SPF-87H and 800P

Alright We'll do the necessary adjustments in the next AIDA64 beta update.

I'm afraid it's not possible to do that with AIDA64. Regards, Fiery

SPD is enumerated in a completely different way in AIDA64. But yes, it may be possible to use that numbering scheme to make the labels look slightly better. It would still not be perfect in all configurations, but it may work better in most configurations.

It's not a stupid question at all. But it's outside the scope of our expertise, so I don't have the answer.