Does your Samsung 850 Pro SSD report "temperature" in S.M.A.R.T. data?


  1. Posts : 2,752
    Windows 7 Pro x64 (1), Win7 Pro X64 (2)
       #1

    Does your Samsung 850 Pro SSD report "temperature" in S.M.A.R.T. data?


    I could swear that the Samsung 850 Pro SSD I have in my Lenovo P70 laptop reported its temperature at one time in the recent past, to HWINFO64 as well as to AIDA64 as well as to Samsung Magician. However it no longer does that, as the temperature is not showing up in HWINFO64's display of S.M.A.R.T. data nor is AIDA64 offering it for display from the I/O sensor chip.

    I have another one in a desktop machine, and that one too also does NOT report temperature. Both of these drives are running the latest BIOS EXM04B6Q.

    I could swear I used to see temperatures for the 850 Pro in these two machines using AIDA64, perhaps when they were both still using BIOS EXM03B6Q. Maybe it's only been since both drives were upgraded to EXM04B6Q that the reporting of temperature in S.M.A.R.T. has disappeared.

    I checked yet a third desktop machine with an 850 Pro that still has an even older BIOS version EXM02B6Q and it IS reporting temperature to AIDA64, which displays it. Again, the temperature isn't showing up in S.M.A.R.T. data displayed by any program, but the sensor chip in this desktop machine obviously is reading it and providing it to AIDA64. And Crystal Disk Info can see that temperature as well, although it too does not show temperature in the S.M.A.R.T. data.

    If you own an 850 Pro, can you please report (a) what is the BIOS version, (b) is it reporting temperature, and (c) what software are you using where the temperature does or does not appear in?


    NOTE: I can see the temperature using Crystal Disk Info 7.5.1, but it doesn't appear in the detail S.M.A.R.T. info. It only shows up in the large and prominent "temperature" items up near the top of the screen. Very strange. I wonder where that value being displayed is coming from for Crystal that no other program seems to know about?
      My Computer


  2. Posts : 7,351
    Windows 7 HP 64
       #2

    I have a 850 Pro with EXM04B6Q.
    I use Open hardware monitor and it shows the temperature.
    It also shows on HWINFO64 under Drive Airflow Temperature. You have to move the cursor (bottom) to the right.
      My Computers


  3. Posts : 2,752
    Windows 7 Pro x64 (1), Win7 Pro X64 (2)
    Thread Starter
       #3

    Megahertz07 said:
    I have a 850 Pro with EXM04B6Q.
    I use Open hardware monitor and it shows the temperature.
    It also shows on HWINFO64 under Drive Airflow Temperature. You have to move the cursor (bottom) to the right.
    Thanks for the info.

    I will contact FinalWire (AIDA64), because they're not reporting the drive temperature since it's apparently not provided by the sensor chip but instead must be extracted from S.M.A.R.T. data. Or, perhaps I need to check some option box that's not currently checked for my ASUS motherboard.

    As far as "airflow temperature" in HWINFO64, I don't know what the other numbers are which don't change no matter whether temperature is displayed in F or C:

    [BE] Airflow Temperature: 69/Always OK, Worst: 58 (31.0 °C)

    I'm still pretty sure I recall that AIDA64 used to display the temperature of the 850 Pro, especially on my laptop where I distinctly remember having three lines of drive temperatures shown, for my 2 x 960 Pro M.2 NVMe and 1 x 850 Pro SATA. Now I only have temps for the 2 x 960 Pro.

    Anyway, I guess I'm straightened out now. Apparently there's nothing wrong with the drive. Thanks again.
      My Computer


  4. Posts : 7,351
    Windows 7 HP 64
       #4
      My Computers


  5. Posts : 2,752
    Windows 7 Pro x64 (1), Win7 Pro X64 (2)
    Thread Starter
       #5

    Ok. I believe I have discovered the fundamental cause of the problem with AIDA64 not reporting temperature of the 850 Pro which has been upgraded to firmware EXM04B6Q. This resulted in a new Hardware ID value that appears more 'generic" than it previously was with EXM04B6Q firmware.

    The new Hardware ID, regardless of the size of the drive, is: SCSI\DiskSamsung_SSD_____________EXM0

    I'm sure that with the previous EXM03B6Q this Hardware ID value was more specific in providing the "850 Pro" model name as well as its capacity (i.e. 512GB vs. 1TB).

    And whereas the Win10 Device Manager seems to be able to distinguish the particular device name and size to show a proper correct drive name, for some reason the Win7 Device Manager does not. I discovered this because I have both Win7 and Win10 on my Lenovo P70 laptop that has an 850 Pro in it. And strangely, the temperature WAS showing in AIDA64 in Win10, but not in Win7.

    And yet both HWINFO64 and CrystalDiskInfo running in either Win7 or Win10 have no problem correctly identifying the proper "Samsung SSD 850 Pro" drive name suffixed with its capacity as well as extracting all SMART data and displaying drive temperature, even though Device Manager in Win7 doesn't make any such distinction. In contrast, Win10 Device Manager also seems to correctly understand the new Hardware ID (and other uniquely identifiying information, obviously), which is most likely why AIDA64 also handles the 850 Pro properly in the Win10 environment.

    (1) Win7 Device Manager - Samsung SSD SCSI Disk Device
    (2) Win10 Device Manager- Samsung SSD 850 Pro 512GB
    (3) HWINFO64 Win7 and Win10 - Samsung SSD 850 Pro 512GB
    (4) CrystalDiskInfo Win7 and Win10 - Samsung SSD 850 Pro 512GB

    Furthermore, whereas both HWINFO64 and CrystalDiskInfo present the complete SMART information (including drive temperature) in both Win7 and Win10, AIDA64 fails to even list the 850 Pro in Win7 for SMART information even though it shows the SMART data perfectly in Win10.

    Clearly it is because of the problematic new "generic" Hardware ID stored in the 850 Pro with firmware EXM04B6Q and the resulting change of drive name in Win7's Device Manager to a "generic" value which is responsible for the AIDA64 Win7 problem issue. Somehow, Win10 Device Manager apparently queries additional information that Win7's Device Manager does not, because in Win10 the drive name appears correctly unique in Device Manager, and AIDA64 works correctly in Win10.

    So there's no question the solution must come from some update to AIDA64, as the other programs don't seem to have any problem with the new Hardware ID and the new Device Manager name as shown in Win7.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:06.
Find Us