This is not correct. Both drives are also affected by the bug. See the "Raw Values" column of ID 9. The hours are encoded in the lower 4 bytes:
000DA76E hex = 894830 decimal
000DA77C hex = 894844 decimal
The values displayed in the extra "Betriebsstunden" or "Power On Hours" field look sane because these are corrected by CrystalDiskInfo itself.
Fortunately this tool is open source, so to be convinced please have a look at the following lines in AtaSmart.cpp from CrystalDiskInfo6_2_2Src.zip:
// Workaround for Intel SSD
if (asi.Model.Find(_T("Intel")) == 0 && asi.MeasuredPowerOnHours > 0x0DA753)
{
asi.PowerOnRawValue -= 0x0DA753;
asi.DetectedPowerOnHours -= 0x0DA753;
asi.MeasuredPowerOnHours -= 0x0DA753;
}
@Intel: Could you please confirm that the offset 0x0DA753 (894803) used by CrystalDiskInfo is the correct one to compensate this bug?
