All Activity

As in the previous screenshot, they'll be labeled "Power Monitor #1 - #6". There are also entries for Total Power, Total Current and Power by Pin using the same nomenclature. I had to unplug and reseat the device before they were detected in Aida.

I apologize for double-posting. When posting elsewhere I am used to generally receiving a reply either within a day or two never. When I didn't get a reply within a few days, I thought I must have posted in the wrong category, that it belonged in Bug Reports. I won't do it again. I disabled GPU monitoring, closed AIDA64 by selecting End Task in the task manager Processes tab (where it appeared only as a background process), and restarted AIDA64. The Sensor Panel froze about half an hour later. When I selected End Task in the task manager Processes tab, the Sensor Panel closed and the AIDA64 icon disappeared from the system tray, but the Processes tab still shows AIDA64 running as a background process, and selecting End Task in the Details tab wouldn't work. Based on other attempts to close AIDA64, it seems possible that I didn't really restart it after disabling GPU monitoring. I'm about to reboot and try again and will report the results.

I wanted to create something that wasn’t techno-aggressive. An image from the internet + ChatGPT, and the new dashboard 1024x600 is ready.

Apologies, error on mine side. I had to reseat the device before the current values were detected. Although I'm able to see the sensors and add them to my panel, I do notice that when I open the Aida app from the taskbar, the sensors disappear. Refreshing sensors and restarting both Wireview and Aida doesn't fix it, nor does closing Wireview so that Aida is the only app running. A reboot seems to be the only way to restore them.

Please avoid opening multiple topics for a single issue. I've replied in your other topic. This topic is closed.

In order to narrow this down, first please disable GPU monitoring in AIDA64 / Preferences / Stability / GPU sensor support, and let us know if it makes a difference. Make sure to restart AIDA64 after altering that option.

Can you see the voltage and current readings similarly labelled on the Computer / Sensor page of AIDA64?

Where did you find these? I dont even see them and no setting for wireview.

Could you share it, friend?

I attempted to modify my panel tonight and it appears that just the power values for the device are being captured (see screenshot). What I, and I think others that are interested in seeing, are the current values per pin. It could be that the device isn't detected perhaps? Is there anything that has to be enabled to see these values? If the device is indeed detected, is there a way to enable a view of the current for each pin?

I have a licensed copy of AIDA64 Extreme. It has been updated 2-3 times since I installed it, most recently a few days ago. I purchased a 9x2 inch monitor (1920x480) specifically for the Sensor Panel. But as long as I have had it, whenever I run AIDA64, at some point it freezes. The Sensor Panel stops updating, and it is impossible to close AIDA64 (clicking X or selecting End Task in taskbar, task manager Processes or task manager Details) without rebooting. It has happened as quickly as a few minutes after launching and as late as 12-15 hours after launching, but it always freezes. As far as I can tell, nothing else is affected. I'm currently using the default Sensor Panel but have tried several customizations with the same result. My system: MSI MPG X870E Carbon Wi-Fi motherboard, Corsair PSU, Ryzen 9 9950X, ASUS RTX 5090, ASUS ROG RYUJIN 360 Cooler, 192 GB G.Skill DDR5 RAM, 4x4TB Samsung MVNE SSDs, 4x24TB Western Digital & Seagate HDDs What is the problem?

My preliminary version of the Asus Armoury Crate theme skin. 1024x600. Asus_AC.spzip ROGFonts-Regular_0.otf OCRAEXT.TTF

Hmm, after looking around in the thread I saw a couple of pictures with screen that has V2 in the default wallpaper under "TURZX" idk if it's referring to the same thing, but once I receive it i will be sure to give a feedback.

my first theme, I also changed it a bit to suit my taste 🙂 1920х480 Video_2026-03-17_163949.mp4

We're aware of 8.8-inch v1.1. Not sure what v2 is, but give it a shot, it could well work out of the box.

Oh Wow! 😍 This Butter Glide Dynamics is a huge game-changer. I love it. Awaiting for your next update.

After Flip Clock, I am excited to share something experimental: The "Butter" Glide Dynamics approach: Add buttery gauge physics (removes crossfade ghosting) to your custom gauges and they will feel sliding. Please see and share your thoughts if you feel any difference: ❤️ This lovely panel was shared by @BHSY 😍 Screen Recording 2026-03-17 172945.mp4 @Loyd I have now fixed the issue where new sensors/items were added to the bottom of the list and changing there position up was not getting saved.

I've already suggested something similar, but no response. btw, some time ago something like this appeared in OSD in RTSS through the Stub identifier, for example: average Stub =(sensor1+sensor2...+sensorN)/N . It's very convenient. For example, I can watch a split average loading of P-cores and E-cores, etc.

Unfortunately, I can't check beta for a while, I'll wait for the stable ones and report here.

Ah no problem, I decided to buy 8.8 instead since 9.2 seems lacking in some important areas, and from the seller it say it's V2, is that correctly supported?

Hello, I tested the issue on the following versions: Previous stable version: AIDA64 Extreme 8.20 Beta version: aida64extreme_build_8213_nz6msf5bdx Newly downloaded stable version: AIDA64 Extreme 8.25 The same symptom is present in all cases. I first had the issue on 8.20, then tested the 8213 beta and observed the same behavior. After that, I reinstalled a freshly downloaded 8.25 stable version, and the bug is still present there as well. So the problem is reproducible on both stable and beta versions. Thank you.

Hello, Additional detail: The issue is not limited to an incorrect displayed value. After I manually assign the SensorPanel item to GPU Hot Spot, the assignment does not persist. Each time I close and reopen AIDA64, the item reverts to CPU GT Cores instead of staying assigned to GPU Hot Spot. What makes this even more confusing is that, in the OSD panel, the value remains correct. So the problem seems to affect SensorPanel specifically, while the OSD still uses the expected GPU Hot Spot source correctly. This is why it appears to be a sensor assignment persistence issue inside SensorPanel, rather than a general sensor reading problem. I also verified the expected GPU Hot Spot value separately with HWiNFO, and it does not match the value shown after AIDA64 reassigns the SensorPanel item to CPU GT Cores. I am attaching a screenshot for reference. Thank you.

Thank you for your feedback!

@drearily 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 helps.

@vixr @booger.bear 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 helps.