Fiery

I'm afraid we ran out of ideas on how to improve the EC interaction

Measuring or monitoring anything during benchmarking is a bad idea since it would negatively affect the benchmark result. Therefore all AIDA64 background monitoring activities have to be paused while a benchmark 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. Let me know if it makes a difference.

You can use custom state images, but you cannot expand the number of states.

Please note that unlike notebook PC batteries, Android devices do not feature sophisticated smart batteries. It sadly means that battery wear level or battery health estimations cannot be measured or computed.

We've removed the links since they contain references to illegal (pirate) product keys of AIDA64. Since the transaction of you purchasing a hardware also involves distributing illegal product keys for our software, it's not our responsibility to assist you in this issue. Try to contact the seller and ask for technical support from them. If you'd like to continue using AIDA64 by purchasing a legal license key from us, please let me know in private message. This topic -- due to its course about illegal content involved -- has to be locked here.

You can reset your OSD settings by closing AIDA64, navigating to AIDA64 installation folder, opening AIDA64.INI (settings file) in Notepad (or any other text editor of your choice), and removing all lines starting with OSDItem_ Please note that the explained process will delete all your customization about your OSD Panel. I'm not sure if I understand your issues about the sensors monitoring and whether it's separate from the OSD Panel reset issue. Is the missing +3.3V rail the only problem, or you have multiple issues that you're looking to solve? Edit: We will fix the missing +3.3V voltage reading issue in the next AIDA64 beta update.

On the SensorPanel just use the mouse right-click context menu --> SensorPanel Manager --> Export to save your layout into a file. You will be able to select the folder and file name.

Laptops are quite different from desktop computer in the sense that they have much less room to prevent the CPU from overheating when there's a very demanding task running on the system. Throttling is considered normal on many laptops therefore, and as long as the computer provides the expected system performance, you have nothing to worry about. Especially since what AIDA64 does in its stress test is truly the worst case scenario in terms of power draw and the resulting heat production.

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

I think you can achieve that by enabling Logging in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging as well as the option on that page called Log started and stopped processes. The latter option should indicate when you start and close a game as long as you do that by launching its main executable file and then closing the process at the end of gaming.

Do you use RTSS as it is installed a part of MSI Afterburner? If yes, then what version of Afterburner are you using? What game (or games) do you experience the issue in?

AFAIK it's not possible to use separate screensaver settings for multiple monitors.

Since it's a regular monitor that appears under Windows as a secondary monitor that you can extend Windows Desktop onto, you can simply use the AIDA64 SensorPanel module with it. This however requires that you connect the monitor directly to your PC and not to your Pi 4.

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

I understand, but it seems it's not possible to avoid EC collisions on your system

In that case it's best to completely disable EC support in AIDA64 / main menu / File / Preferences / Stability. I don't think you'd lose any sensor readings by that.

So far we haven't been able to reproduce the issue on our test systems here

We need to look into the installed RAID drivers as well as check how the existing RAID enumeration methods work on your system. Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART 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 --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Finally, right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> Disk Controllers Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

So far we haven't found a way to implement that functionality in AIDA64. We need to look for alternative solutions.

I see. I'm afraid we haven't dealt with such a device before. Maybe someone else can chime in who's already done it.

Logitech would need to come up with a SDK that provides such measurements for 3rd party applications like AIDA64.

Thank you for your feedback!

We've recently revamped the EC register access part of AIDA64, so 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.

Probably your best bet is to download a SensorPanel layout from: