Samsung SSD 9100 PRO has two different Temperature Sensors, but only the lowest temperature is actually reported 2x

[FatBoyNL]

Looking at the SMART table for the Samsung SSD 9100 PRO, there are 2 different Temp Sensors on this SSD - which are showing 2 different values in SMART.
AIDA64, Samsung Magician and HWinfo64 all confirm this in their included SMART tools.
I guess they are to be used separately, one for the controller and one for the memory - of which the controller probably has the highest temp.

NOTE: There is also 1 separate Temperature value in SMART, that shows the readout of only 1 of the 2 Temp Sensors.

But in the Computer > Sensor page in AIDA64, both temperatures reported for the 9100 PRO are always shown to be exactly the same - no matter what the usage is.
So it seems only 1 of the 2 different  temperature sensors is used to show 'both' temperatures for the 9100 PRO in AIDA64.

I think this currently incorrect in AIDA64 for the 9100 PRO, as my other Samsung SSD 990 PRO does show two different temperatures in AIDA64 on the Computer > Sensor page, with the temperatures shown from both Temperature Sensors.
I attached some screenshots for clarification.

Could you please look into this?

EDIT:
By the way, it seems that Samsung has 'switched' Temperature Sensors 1 and 2 for the 9100 PRO, as opposed to those on the 990 PRO. Maybe that is the root cause of this issue? I mean, AIDA64 could be showing "Temperature" and "Temperature Sensor 2" for both the 990 PRO and the 9100 PRO - which would cause the 9100 PRO to show one and the same value (by mistake).

[Fiery]

2 hours ago, FatBoyNL said:

EDIT:
By the way, it seems that Samsung has 'switched' Temperature Sensors 1 and 2 for the 9100 PRO, as opposed to those on the 990 PRO. Maybe that is the root cause of this issue? I mean, AIDA64 could be showing "Temperature" and "Temperature Sensor 2" for both the 990 PRO and the 9100 PRO - which would cause the 9100 PRO to show one and the same value (by mistake).

Yes, I think you've nailed it there: Samsung -- probably by mistake -- switched the Temp Sensor 1 and 2 sensors in the NVMe log.

[FatBoyNL]

31 minutes ago, Fiery said:

Yes, I think you've nailed it there: Samsung -- probably by mistake -- switched the Temp Sensor 1 and 2 sensors in the NVMe log.

I hope this can easily be fixed in the next AIDA64 (beta)? Or should I write a letter to Samsung about this? 😉

The downside of my little research is that my 9100 PRO just isn't as cool as I thought before though.. Bummer 🥵 

[Fiery]

4 minutes ago, FatBoyNL said:

I hope this can easily be fixed in the next AIDA64 (beta)? Or should I write a letter to Samsung about this? 😉

The downside of my little research is that my 9100 PRO just isn't as cool as I thought before though.. Bummer 🥵 

The problem is: if we switch it now, and Samsung switches it around in the next firmware update, we will have more switching around to do, separate the logic using firmware revision, etc...  Let's wait for the next firmware update and then we'll see what the right move is.

[FatBoyNL]

1 hour ago, Fiery said:

The problem is: if we switch it now, and Samsung switches it around in the next firmware update, we will have more switching around to do, separate the logic using firmware revision, etc...  Let's wait for the next firmware update and then we'll see what the right move is.

Can't this be solved by using only both Temp Sensor values (and just leave the 'Temperature' value) and use them as T(high) and T(low) for determining the actual output values as shown by AIDA64? But for all Samsung NVMe drives only maybe? 

I don't know whether all other NVMe drives from all other manufacturers are using the same SMART data for temperature readings like this. Or is that about exactly what you're saying? That would make completely sense and I guess then we'll have to wait for new firmware like you said.

EDIT: I think see your point now. Most programs like CrystalDiskInfo would use just 'Temperature' for their one-and-only Temp reading, so that should be the primary reading whatsoever. And then there's 'another' reading, but which one of the two... That's a problem. Still think this can be solved by simple math though 😜

Meanwhile, do you know any higher-tier support contacts over at Samsungs btw? I would like to offer my (nagging) skills to contact them about this, but I have the feeling their AI Support Chatbot just wouldn't understand me in that First Encounter 😇

[FatBoyNL]

EDIT: I guess we'll have to wait for Samsung to fix this.

[Fiery]

21 hours ago, FatBoyNL said:

Can't this be solved by using only both Temp Sensor values (and just leave the 'Temperature' value) and use them as T(high) and T(low) for determining the actual output values as shown by AIDA64? But for all Samsung NVMe drives only maybe? 

I don't know whether all other NVMe drives from all other manufacturers are using the same SMART data for temperature readings like this. Or is that about exactly what you're saying? That would make completely sense and I guess then we'll have to wait for new firmware like you said.

EDIT: I think see your point now. Most programs like CrystalDiskInfo would use just 'Temperature' for their one-and-only Temp reading, so that should be the primary reading whatsoever. And then there's 'another' reading, but which one of the two... That's a problem. Still think this can be solved by simple math though 😜

Meanwhile, do you know any higher-tier support contacts over at Samsungs btw? I would like to offer my (nagging) skills to contact them about this, but I have the feeling their AI Support Chatbot just wouldn't understand me in that First Encounter 😇

No, I'm afraid we don't know anyone at Samsung

We'll implement a temporary workaround to mitigate the firmware issue.  In order to do that, please let us know the firmware revision of your 9100 Pro drive.  Is it 0B2QNXH7 ?

[FatBoyNL]

7 minutes ago, Fiery said:

No, I'm afraid we don't know anyone at Samsung

We'll implement a temporary workaround to mitigate the firmware issue.  In order to do that, please let us know the firmware revision of your 9100 Pro drive.

Thanks, the current firmware revision of my 9100 PRO is 0B2QNXH7.

[Fiery]

On 4/11/2025 at 11:33 AM, FatBoyNL said:

Thanks, the current firmware revision of my 9100 PRO is 0B2QNXH7.

Thank you!  Please check the latest AIDA64 beta update available at:

https://www.aida64.com/downloads/latesta64xebeta

Let me know how it works

[FatBoyNL]

1 hour ago, Fiery said:

Thank you!  Please check the latest AIDA64 beta update available at:

https://www.aida64.com/downloads/latesta64xebeta

Let me know how it works

Thanks, this looks perfect 👍

[Fiery]

12 minutes ago, FatBoyNL said:

Thanks, this looks perfect 👍

Thank you for your feedback!