Hi Martin, I'd like to tell you that I've been using HWiNFO64 for a while now, and it is just fantastic! First, I use it on my ASUS SaberTooth P67 board with i7-2600k CPU. IMO, all the Sensor readings are perfectly accurate, and thanks for including all the "Thermal Radar" sensor readings (all eleven of them) in the display. The System Summary display is working great now, IMO earlier versions of HWiNFO32 were not showing the correct clock speeds of the CPU cores, which never seemed to show the CPU cores in the C1E state, at 1.6GHz. That has been corrected, and it seems just perfect now. The core speeds really change quickly, don't they, and I imagine it was a challenge keeping up with them. I have the Turbo multipliers at 45 on my CPU, and the display shows that perfectly. I can't see anything not quite right whatsoever, very excellent work, just great and thank you for providing this great program! I also use HWiNFO64 on my SaberTooth X58 PC, with an i7-930 CPU, and it seems perfect on that system too.
I have a few questions and comments, if I may. I've noticed in the Sensor Status display, that there are two or three general CPU temperature values shown, one or two in the "Intel CPU" section (CPU Package, and also CPU IA Cores), the other in the "Nuvoton NCT6776F" section (labelled CPU). The CPU temperature value in the Intel CPU section do not match that shown in the Nuvoton NCT6776F section, the latter always reading at least 10 degrees C lower than the former.
Please note that I am not saying that this is a bug in HWiNFO64, I do not believe it is a problem at all. For whatever reason, the Nuvoton chip provides, IMO, an incorrect CPU temperature. I have actually seen it regularly report a CPU temperature that is less than my room/ambient temperature. While I use a high performance CPU cooler, I know it is impossible for the CPU temperature to be below the ambient temperature.
I am also mentioning this because recently an EFI/BIOS update from ASUS for the SaberTooth P67 caused the program provided by ASUS for temperature monitoring (the Monitor function of AI Suite II) to use the CPU temperature reading from the Nuvoton chip, where previously it used the temperature reading from (I assume) the Intel CPU. The "new" CPU temperature reading in Monitor matches exactly what HWiNFO64 shows for CPU in the Nuvoton section, where it previously matched what HWiNFO64 showed in the Intel CPU section. I consider this situation to be an error by ASUS, and not a trivial one because the CPU temperature value is used by their PWM fan control software to set the CPU cooler's fan speed. The result of this is an under-cooled CPU, and I have been warning users of this in the ASUS forum for this board.
I give credit to you Martin and HWiNFO64, for allowing me to verify and understand what is happening due to this unfortunate situation with the ASUS EFI update. The correct and incorrect CPU temperature readings in Monitor, when used with the previous and latest version of the EFI, match exactly what I see in HWiNFO64, and I was able to identify IMO, that the change was due to using the Nuvoton CPU temperature reading in the EFI update. Thank you so much for all this!
In the Nuvoton section of HWiNFO64, there are four temperature readings I don't understand. They are labeled "Auxiliary", and "SYSTIN1", 2, and 3. I can't match them with any of the other temperature readings in Sensor Status, any idea what they are supposed to be from? I don't consider this to be a bug or problem, just wondering about them.
Again, thanks so much for this program, I use it exclusively now, and is my first choice in hardware monitoring programs.
I have a few questions and comments, if I may. I've noticed in the Sensor Status display, that there are two or three general CPU temperature values shown, one or two in the "Intel CPU" section (CPU Package, and also CPU IA Cores), the other in the "Nuvoton NCT6776F" section (labelled CPU). The CPU temperature value in the Intel CPU section do not match that shown in the Nuvoton NCT6776F section, the latter always reading at least 10 degrees C lower than the former.
Please note that I am not saying that this is a bug in HWiNFO64, I do not believe it is a problem at all. For whatever reason, the Nuvoton chip provides, IMO, an incorrect CPU temperature. I have actually seen it regularly report a CPU temperature that is less than my room/ambient temperature. While I use a high performance CPU cooler, I know it is impossible for the CPU temperature to be below the ambient temperature.
I am also mentioning this because recently an EFI/BIOS update from ASUS for the SaberTooth P67 caused the program provided by ASUS for temperature monitoring (the Monitor function of AI Suite II) to use the CPU temperature reading from the Nuvoton chip, where previously it used the temperature reading from (I assume) the Intel CPU. The "new" CPU temperature reading in Monitor matches exactly what HWiNFO64 shows for CPU in the Nuvoton section, where it previously matched what HWiNFO64 showed in the Intel CPU section. I consider this situation to be an error by ASUS, and not a trivial one because the CPU temperature value is used by their PWM fan control software to set the CPU cooler's fan speed. The result of this is an under-cooled CPU, and I have been warning users of this in the ASUS forum for this board.
I give credit to you Martin and HWiNFO64, for allowing me to verify and understand what is happening due to this unfortunate situation with the ASUS EFI update. The correct and incorrect CPU temperature readings in Monitor, when used with the previous and latest version of the EFI, match exactly what I see in HWiNFO64, and I was able to identify IMO, that the change was due to using the Nuvoton CPU temperature reading in the EFI update. Thank you so much for all this!
In the Nuvoton section of HWiNFO64, there are four temperature readings I don't understand. They are labeled "Auxiliary", and "SYSTIN1", 2, and 3. I can't match them with any of the other temperature readings in Sensor Status, any idea what they are supposed to be from? I don't consider this to be a bug or problem, just wondering about them.
Again, thanks so much for this program, I use it exclusively now, and is my first choice in hardware monitoring programs.