search

labradore / open-hardware-monitor

Automatically exported from code.google.com/p/open-hardware-monitor
0 stars 0 forks source link

Wrongly Reporting Temperature Spikes #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
After testing with an older beta, today I installed the newest beta version
0.1.26.1 and am still experiencing the same incorrect spikes in either my
MB or CPU temperatures.  Open Hardware Monitor reports spikes of 83 when
both Everest and CPUID Hardware Monitor both reported my temps never
exceeded 34. The image I sent you is from the older beta but the new one is
reporting the same thing.  It has to be a bug because the spike is ALWAYS
83.  Not once has it reported the spike as 81 or 82 or 84 or 85... but
ALWAYS 83 no matter if just surfing the Internet or maxing my system with
Orthos.  The spike is always 83.

Original issue reported on code.google.com by chuckl...@gmail.com on 9 Mar 2010 at 3:21

Attachments:

GoogleCodeExporter commented 9 years ago 
Have you closed all other monitoring applications like Everst, CPUID HWMonitor 
or
SpeedFan when this problem occurs?

Does this happen for both temperatures of the IT8718F, or only for the first?

Can you post an OpenHardwareMonitor.Report.txt file (create with File / Save 
Report)?

Original comment by moel.mich on 9 Mar 2010 at 8:08

GoogleCodeExporter commented 9 years ago 
The other programs were not running when I first started having these spikes, 
so yes
they were closed.  After I had these spikes several times is when I decided to 
start
the other programs also and see if they could confirm the spikes, but they did 
not. 
It only shows up with Open Hardware Monitor.

As the above image shows the spike was on sensor #1, but lastly they have been 
on
sensor #2... so yes they are showing up with both and always 83.

Original comment by chuckl...@gmail.com on 9 Mar 2010 at 3:12

GoogleCodeExporter commented 9 years ago 
Here is another image from today

Original comment by chuckl...@gmail.com on 9 Mar 2010 at 9:02

Attachments:

GoogleCodeExporter commented 9 years ago 
Thank you for the report. I am not really sure what causes the problem, because 
I
can't reproduce it here. The IT8718F doesn't show this problem.

My guess is, that there is some other software (like CPU-Z, some driver, ...)
somewhere in your PC that thinks it needs to read the CPU VCore voltage from 
time to
time. This could cause the following collision: The OHM configures the IT8718F 
for
reading the temperature, then another software prepares the IT8718F for reading 
the
VCore, and then the OHM reads the value, thinking it gets the temperature, 
while it
actually gets the voltage. But this is only a guess.

Anyway, I have implemented a few additional checks, which could solve the 
problem (or
reduce the chance of it happening). Can you test the new version 0.1.27 Beta, 
and
report if there is any improvement?

Original comment by moel.mich on 9 Mar 2010 at 10:45

GoogleCodeExporter commented 9 years ago 
I haven't been running the new version long, but at first impression it seems 
you
have the spikes fixed...  Attached is an image I sent to a friend... that is 
why I
have the notes on the image.

Original comment by chuckl...@gmail.com on 10 Mar 2010 at 12:14

Attachments:

GoogleCodeExporter commented 9 years ago 
Just an update... I have been running the new beta version 1.27 for a couple 
hours
now and still not a single temperature spike has been reported.  I think you 
have it
fixed.

Thank You!

Original comment by chuckl...@gmail.com on 10 Mar 2010 at 2:06

GoogleCodeExporter commented 9 years ago 
Thank you for your feedback. I will change the status to fixed now. In case the
problems reappear, just add another comment and it can be reopened.

Original comment by moel.mich on 10 Mar 2010 at 4:23