Fiery

Thank you! Your device uses the Asetek LC protocol, the older Version 6 of it. Everything seems to be working well in terms of finding the device itself, so the problem that prevents AIDA64 from talking to the device could be that EVGA's own software has the device open and blocking concurrent access to the same device. Try to close EVGA's software and check if AIDA64 can pick up the Asetek LC device.

We will add a few special keys in the next AIDA64 beta update. Row key manager would be overkill for the purpose of the RGB LED module which is supposed to be an easy-to-use module.

We will add the requested option called Corsair Hydro Platinum sensor support to the AIDA64 / main menu / File / Preferences / Stability page in the next AIDA64 beta update. I'll post a message into this topic once the new beta build is available for download.

I suppose RTSS (which may be a component of MSI Afterburner) would open AIDA64 or HWiNFO.

That's a known limitation of AMD RAID drivers. They provide ATA passthrough and SMART information only for the first drive of the RAID array.

Can you please post a screenshot of Asus GPU Tweak II, showing how you can control and monitor the fans? I'm asking for that because even though both Asus Strix-RTX2080 and Asus Strix-GTX1080 seem to have the same sensor chip, somehow they seem to have a different registers layout So we're not sure how to handle them both properly.

Thank you for your help and feedback!

Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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 --> Corsair Link Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

Thank you for your feedback

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.

Please avoid posting a single issue into multiple topics. I've replied you in your other topic.

Make sure to upgrade to the latest beta version of AIDA64 Engineer available at: https://www.aida64.com/downloads/latesta64eebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

Thank you. I'm afraid we couldn't reproduce the issue with our own GRID+ V3 device. So we've decided to change the GRID+ V2 option in AIDA64 / main menu / File / Preferences / Stability to apply to GRID+ V3 as well. So you can use that option to disable GRID+ V2 and V3 support altogether if it keeps working incorrectly on your system.

Thank you for the info. 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

I'm glad you've managed to resolve it. In HWMonitor where can you see the WHEA error info? I've checked and I cannot find anything related to it there. Can you perhaps post a screenshot to show us what you're looking for?

Not yet, since we don't know what's happening. We'll need to get an ASRock Fatal1ty class motherboard to diagnose this issue.

Sadly we cannot find anything useful in there But since you've mentioned SIV, try to contact its author (Ray) as well. Ray is very eager and skilled in digging down deeper when it comes to supporting exotic and unique hardware.

We don't have a direct solution for that problem, so you gotta find a way to bridge the gap between SCOM and the existing External Applications or Logging facility of AIDA64.

What motherboard and CPU do you have?

Of course, it will!

We've fixed the device icons in the following new AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta

Sadly, via WMI the same incorrect information is returned, e.g. last AV signature update in 2016, etc. Anyway, here's a new AIDA64 beta where we've fixed what we could: https://www.aida64.com/downloads/latesta64xebeta

We've fixed the sensor readings for your motherboard in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.

We've implemented the requested feature in the latest AIDA64 beta: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works

I'm afraid we don't maintain such a list of devices.