SSD temperature reading

[Deleted member 180]

I've got 3 storage devices on my pc. One SSD and two WD HDD drives. The SMART reading for my SSD always shows 128 degrees so I guess it doesn't have a temperature sensor. So, I have hidden this sensor reading. The problem is that when I restart my computer the SSD sensor reading appears and one of the WD HDD sensor reading disappears. It is completely random which drive sensor appears.

Before restart

[attachment=286]

After restart

[attachment=287]

 

[Martin]

Yes, it seems the SSD doesn't have a temperature sensor.
Please send me a screenshot of the Sensor Configure screen before and after restart, it might also be helpful to attach a registry dump of the following key (using regedit): HKEY_CURRENT_USER\Software\HWiNFO64
Also one question: this this problem occur also after you close and start HWiNFO64 again, or is a reboot required to reproduce it?

You might also try to "Reset Preferences" prior to HWiNFO start to see if this fixes the problem.

 

[Deleted member 180]

Yes, it seems the SSD doesn't have a temperature sensor.
Please send me a screenshot of the Sensor Configure screen before and after restart, it might also be helpful to attach a registry dump of the following key (using regedit): HKEY_CURRENT_USER\Software\HWiNFO64
Also one question: this this problem occur also after you close and start HWiNFO64 again, or is a reboot required to reproduce it?

You might also try to "Reset Preferences" prior to HWiNFO start to see if this fixes the problem.

This only happens when I reboot my machine. I tried "Reset Preferences" with no success. I've attached screenshots and registry dumps. I noticed that the order of the storage devices changes order between reboots and I think this may be causing this problem.

 

[Martin]

Definitively, that must be the reason.
Does the order of devices after reboot change in system and HWiNFO64 under Drives ?
Can you please attach the respective Debug Files with sensor data too?

 

[Deleted member 180]

Definitively, that must be the reason.
Does the order of devices after reboot change in system and HWiNFO64 under Drives ?
Can you please attach the respective Debug Files with sensor data too?

Yes, the order in system matches the order in the sensor window. I've attached the debug files.

 

[Martin]

Indeed, the debug files confirm, that the order of drives in system changes after reboot and that's the reason why your sensor settings in HWiNFO are applied to a different drive after reboot.
Since HWiNFO keeps the settings per device index, there's no easy fix for this. I'd rather search for the reason why this happens. Do you have an idea why?

 

[Deleted member 180]

Indeed, the debug files confirm, that the order of drives in system changes after reboot and that's the reason why your sensor settings in HWiNFO are applied to a different drive after reboot.
Since HWiNFO keeps the settings per device index, there's no easy fix for this. I'd rather search for the reason why this happens. Do you have an idea why?

I don't have an idea why this happens. Maybe it is because I have the WD drives configured in raid 0 using windows dynamic volumes. I tried disabling SMART monitoring in the bios for the SSD drive but it still appears on the sensor window. I have all drives configured in AHCI mode and don't know if this is causing the problem too. Can't you bind the drives to the SATA port number? If you order them by the sata port number this won't happen unless I switch the sata ports where they're connected.

 

[Martin]

That won't be easy, but I'll have a look at it.
Anyway, I think it's not ok when the order of drives changes between boots and that it should be fixed on operating system level.

 

[Deleted member 180]

That won't be easy, but I'll have a look at it.
Anyway, I think it's not ok when the order of drives changes between boots and that it should be fixed on operating system level.

I've got no issues with the operating system. Everything works fine and drives allways have the same letter assigned. I don't know what may be causing this. The operating system's drive is on sata port 3 and maybe if I change it to sata port 1 will resolve this.