GPU Hot Spot value in SensorPanel does not stay assigned and switches back to CPU GT Cores sensor

[Sam2971]

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

1. Is this a known issue in AIDA64 SensorPanel?

2. Can SensorPanel items become linked to the wrong sensor after restart, refresh, or hardware polling reordering?

3. Is there a recommended way to bind a SensorPanel item more reliably to the intended GPU sensor?

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

[Sam2971]

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.

[Sam2971]

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.