You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the expected output? What do you see instead?
I expect to see coldness initially and hot after gaming. I see the reverse of
that for temperature #2 of the Nuvoton NCT6776F on my Asrock z68 Extreme...
What version of the product are you using? On what operating system?
0.7.1.0 on MS Windows 7.
Please provide any additional information below.
As an additional test I blew cold air into the PC from an external fan and
watched the temp. 2 indication rise while others were falling. I've provided
two reports. The first shows the readings just after switching on and you can
see that temp. 2 has already been hotter than CPU or GPU.
Please attach a Report created with "File / Save Report...".
Grr - "Issue attachment storage quota exceeded."
Thanks for the program. It's great otherwise.
John.
Original issue reported on code.google.com by [email protected] on 22 Jun 2015 at 10:50
The text was updated successfully, but these errors were encountered:
Comparing two Open Hardware Monitor Reports
(Version: 0.7.1.0 Common Language Runtime: 4.0.30319.1026
Microsoft Windows NT 6.1.7601 Service Pack 1 64 bit.
ASRock Z68 Extreme3 Gen3 (/mainboard) Nuvoton NCT6776F (/lpc/nct6776f) = MB
Intel Core i5-3570K (/intelcpu/0) = CPU
NVIDIA GeForce GTX 980 (/nvidiagpu/0) = GPU1
SanDisk SDSSDHII480G (/hdd/1) = SSD1
Current Temp. indicated just after switching on the PC from cold = Cold
Current Temp. indicated just after playing a graphics intensive game = Game
<<>> MB#1 MB#2 MB#3 CPU#1 CPU#2 CPU#3 CPU#4 GPU1 SSD1
Cold 26.5 45.5 31.0 24.00 30.00 26.00 22.00 32.0 26.0
Game 35.5 35.5 43.0 30.00 34.00 30.00 29.00 58.0 29.0
As you can see, all sensors show increased temperatures except MB#2
which shows a decrease.
Original issue reported on code.google.com by
[email protected]
on 22 Jun 2015 at 10:50The text was updated successfully, but these errors were encountered: