propergol 10 Posted October 14, 2015 Share Posted October 14, 2015 I just swapped my system SSD from a Sandisk Extreme II to a Crucial BX100 and I did noticed that temp is read correctly in Scanner's SAMRT detail window (31°C) but is wrongly displayed in Scanner's main windows (0°C). BitFlock : RQKIA4F2 Quote Link to post Share on other sites
Christopher (Drashna) 632 Posted October 19, 2015 Share Posted October 19, 2015 What version of StableBit Scanner are you using specifically? Quote Link to post Share on other sites
propergol 10 Posted October 19, 2015 Author Share Posted October 19, 2015 The screenshot was made with version v 2.5.2.3103 BETA under Windows Server 2012 R2. I have just dicided to simplify my setup and give a test to Windows 10 as my server machine rather than running Server R2. Under Windows 10 with the same Scanner version I face the same issue : 0°C reported Quote Link to post Share on other sites
Christopher (Drashna) 632 Posted October 19, 2015 Share Posted October 19, 2015 .... that's really odd. Flagged for Alex: https://stablebit.com/Admin/IssueAnalysis/20829 Quote Link to post Share on other sites
propergol 10 Posted October 19, 2015 Author Share Posted October 19, 2015 hmmm... I am thinking ... I could try to plug the SSD on the M1115 rather than on Intel mobo port. But since this is my system's SSD I m not sure it would boot. Will try and report. Quote Link to post Share on other sites
propergol 10 Posted October 20, 2015 Author Share Posted October 20, 2015 Ok I did test with BX100 on M1115 and it still shows 0°C. Quote Link to post Share on other sites
Christopher (Drashna) 632 Posted October 20, 2015 Share Posted October 20, 2015 I'm not surprised that it didnt' work. Specifically, the issue here is that there are two ways the drive reports it's temperature. SCT (which is what the problem is) and SMART. SCT is newer and "is supposed to work better" than SMART. But clearly that isn't' the case. Basically, we need to disregard SCT temp if it's 0C, and use SMART in this case. Alex is aware of the issue (I talked to him directly about it), and we hope to get to the issue soon. Quote Link to post Share on other sites
Christopher (Drashna) 632 Posted November 12, 2015 Share Posted November 12, 2015 Sorry, this should be fixed in the latest beta builds, IIRC. Quote Link to post Share on other sites
propergol 10 Posted November 13, 2015 Author Share Posted November 13, 2015 Sorry but it isn't Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.