Thank you for the file and your observation, that explains a lot! But I'm not sure yet what exactly needs to be enabled, I will check this with GIGABYTE.
Just one more question - once it's enabled, does HWiNFO show same values as the GIGABYTE tool ?
HWiNFO cannot talk directly to the drive/controller, that might result in data corruption when the system accesses it too.
The only way is to go thru the driver, which however doesn't support it on Windows 7.
Thanks, but that's not the Debug File.
Nevertheless, I noticed that you're running Microsoft Windows 7 and that's the reason. Unfortunately this system doesn't have dedicated support (drivers with NVMe pass-thru) for directly querying NVMe drives.
Windows 10 has it, so there's no issue. For...
These are intentional changes. The amount of memory timings has been filtered to include only timings according to the specification.
I can see only one issue that I will check, which is the tRCD @ 933 MHz. For that I will need the HWiNFO Report File. Could you please attach it?
And here the ASUS "own" (EC) chipset temperature matches the value read straight from the chipset. So HWiNFO reports this correctly.
I assume the other boards read the X570 temperature from a diode not close enough to the heat source.
It's difficult to predict how the order of drives (and respective sensors) will change when adding those drives. It depends on the controller and port attached to.
So yes, best would be to avoid running HWiNFO during that. Alternatively you might backup HWiNFO settings before the process and...
It seems that those erratic values occur only seldom. Unfortunately, these were not captured in the report file attach.
Can you please try to capture them either in the HTM report or sensor log file?
Since I need to see the exact values obtained, it would also be good if you could enlarge the...