All Activity

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.

It's good, thanks so much for your great work

Thank you! We've implemented a few tricks to mitigate this issue. Please check it out and let us know whether it helps or not: https://www.aida64.com/downloads/latesta64xebeta

@Skinny12 @Kleimo @Tanis53 @braintez @ParisV We've implemented support for Thermal Grizzly WireView Pro II in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta

We've implemented a workaround to mitigate this issue. Please check it out: https://www.aida64.com/downloads/latesta64xebeta

Thank you for your feedback!

Hello, I am experiencing a recurring issue with AIDA64 SensorPanel concerning temperature source assignment, and I would like to know whether this is a known bug, a sensor mapping problem, or a SensorPanel item persistence issue. System / hardware configuration My system is currently configured as follows: Motherboard: ASUS ROG Strix Z790-A Gaming WiFi D4 CPU: Intel Core i7-14700K RAM: 32 GB DDR4-3600 GPU: Sapphire Radeon RX 9070 XT Pulse Cooling: TRYX Panorama 360 SE AIO Main display: Samsung Odyssey G55C QHD 165 Hz Secondary display: Z-Edge 1080p 240 Hz Additional monitoring display: HDMI display used for monitoring / SensorPanel I use AIDA64 SensorPanel on a custom monitoring screen to display hardware values in real time. Problem description My goal is to display the GPU Hot Spot temperature from my AMD graphics card. However, when I assign a SensorPanel item to the GPU Hot Spot temperature, the assignment does not remain valid. After some time, or after reopening / reloading AIDA64, the same item seems to switch back automatically to a CPU-related sensor, specifically CPU GT Cores, instead of staying linked to the GPU Hot Spot sensor. So in practice: I select the correct GPU Hot Spot sensor the displayed value may appear correct temporarily but later the item is no longer linked to the correct GPU sensor instead, it points to CPU GT Cores (or another CPU / iGPU-related temperature entry) What makes this confusing This does not look like a simple wrong temperature reading. The issue is that the SensorPanel item itself does not seem to keep the correct sensor association. It looks as if the sensor source is being remapped or replaced internally. What I already noticed the issue concerns SensorPanel assignment persistence it specifically affects the value I want to use for GPU Hot Spot the incorrect fallback sensor is related to CPU GT Cores this makes the displayed value unreliable for panel monitoring What I would like to know Is this a known issue in AIDA64 SensorPanel? Can SensorPanel items become linked to the wrong sensor after restart, refresh, or hardware polling reordering? Is there a recommended way to bind a SensorPanel item more reliably to the intended GPU sensor? Could this be caused by ambiguous sensor naming, changing sensor indexes, or an AIDA64 bug? Additional detail I am not asking here about a general temperature discrepancy with another monitoring software. My main issue is really the loss of the correct sensor binding inside SensorPanel, where GPU Hot Spot ends up being replaced by CPU GT Cores. If needed, I can also provide: screenshots of the SensorPanel item settings screenshots of the incorrect displayed value full hardware details AIDA64 report / preferences export Any help would be appreciated, because this prevents me from trusting the displayed GPU Hot Spot value in my panel. Thank you.

link please?

thank you very much

What do you think based on your design?

KILLNAGATHUL PANEL.spzip BEBASNEUE-REGULAR.rar

That’s wonderful. May I ask you to share it?

My project in 1280 x 800

Oh, you know what, I think I had the same high CPU usage issue you ran into when I updated to a newer version of Wigi manager. I haven't checked to see if they fixed it, but looking back at an email I had sent to GSkill, the issue happned after I updated the manager to something newer than the 1.1.9190.33009. I just ended uninstalling and reinstalling the older 1.1.9190.33009 and everything went back to normal. One of those "don't update what ain't broke" things. If you go to https://www.gskill.com/download/1702985017/1702985071/WigiDash you can find that version, which was released a year ago.

Those are odd numbers. On my 5700x3D WigiDashManager is using 0.8-1.5% (under 1% half the time) CPU and memory use is bouncing between 90-107 MB. I'm on Win10, WigiDashManager 1.1.9190.33009, and Aida 64 8.25.8200

1920 x 1280

Neon.zip

Thanks for the update and for expanding support for more LCD and VFD devices in AIDA64. It’s great to see continued development in this area since there are indeed many different displays with different controllers and interfaces. The list of upcoming devices looks promising and it’s good that you’re gathering feedback from users about what hardware should be supported next. That will definitely help prioritize the most commonly used displays. If I come across any unsupported LCD or VFD hardware I’ll share the manufacturer model interface type and a link to the product page. And if it uses USB I’ll provide a USB dump from AIDA64 as you requested.

Very good, could you share it?

Enter the Electric Future with “Sci-Fi IonWire | I-9” A fusion of energy, signal, and precision - crafted for those who see beauty in every byte. Size: 1920x480 Need a custom fit? Your panel, your way - tailored dimensions on request: 3840x1100 | 1280x800 | 1024x768 | 1920x720 | 1920x1080 & more! Precision > Perfected: Temperature: CPU · GPU: 100 States Utilization: CPU · GPU · RAM · VRAM: 100 States Note: Requires AIDA64 v7.70.7500 or Beta v7.99.7829 or above. Please click here to send me a PM to claim your exclusive Sensor Panel. Forge Tomorrow - Precision engineering for minds that dare. Explore more on my webpage: Surjeet Skins Turning Every Byte Into Beauty.

@Fiery Unlike Aida64, the value does not disappear and drops to 0.0V much less frequently. Thanks