Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VCore incorrect with Winbond W82637THF #3

Closed
GoogleCodeExporter opened this issue Jun 5, 2015 · 6 comments
Closed

VCore incorrect with Winbond W82637THF #3

GoogleCodeExporter opened this issue Jun 5, 2015 · 6 comments

Comments

@GoogleCodeExporter
Copy link

Sometimes the VCore displayed is incorrect. In a previous screenshot (Issue
#1) it was OK, now it's reading over 2V which is physically impossible.

Original issue reported on code.google.com by furex.fu...@gmail.com on 21 Feb 2010 at 4:30

Attachments:

@GoogleCodeExporter
Copy link
Author

Do you run any other hardware monitoring applications at the same time? 

Is the value constantly wrong, or only for short moments (1s-2s) and then 
return to
normal?

Original comment by moel.mich on 21 Feb 2010 at 4:41

@GoogleCodeExporter
Copy link
Author

ATM it's costantly wrong. No other app is accessing the SuperIO chip AFAICT, I 
also
suspect that running two different applications alongside can lead to system 
freezes.

Now the CPU is idling at 0.95V but OHM says 0.82-0.85. After shutting down OHM, 
I
opened Speedfan and the correct value. Then I closed SpeedFan and ran OHM and 
it's
still reporting 0.82-0.85 :-?

Original comment by marco.sa...@gmail.com on 21 Feb 2010 at 7:26

@GoogleCodeExporter
Copy link
Author

There are two voltage measurement modes for the W82637THF, right now only one is
implemented. Some other tool or the OS must have switched the mode, so that's 
why the
value was first correct and now its wrong. I will not switch the measurement 
mode,
but implement just both formulas and detection of the current mode.

Original comment by moel.mich on 21 Feb 2010 at 9:26

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

The revision 74 should fix the problem. Please verify with relase version 
0.1.23-beta.

Original comment by moel.mich on 21 Feb 2010 at 9:52

@GoogleCodeExporter
Copy link
Author

It seems to be working now, thanks Michael for the quick fix!

Original comment by marco.sa...@gmail.com on 21 Feb 2010 at 10:09

@GoogleCodeExporter
Copy link
Author

Original comment by moel.mich on 21 Feb 2010 at 11:12

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant