- Added support for the Nuvoton NCT6791D super I/O chip.
- Added support for Intel Core i7 4xxx CPUs.
- Added support for Intel Core i7-59xx and Xeon E5-2600/1600 v3 CPUs.
- Added support for Intel Core M-5xxx CPUs.
- Added support for Intel Atom N2xxx, D2xxx, C2xxx, E3xxx and Z3xxx CPUs.
- Added support for up to 64 logical processors.
- Added a data logging implementation with configurable logging interval.
- Changed the Intel core temperature reading to evaluate the “reading valid” bit for package level sensors as well.
- Fixed an issue with restoring default control of GPU fans.
- Changed the settings save code to use a more robust two file based approach.
Release Version 0.7.1 Beta
Posted by Michael Möller on December 30, 2014
How painless will upgrading from previous versions be? I understand there is a difference in the way the preferences are saved.
Thanks!
It depends from which version you upgrade, but in general you can just replace all files but the OpenHardwareMonitor.config (contains your settings) and it should work.
Issues reported on MalwareBytes’s forum.
Thank you 🙂
Malwarebytes replied:
“This has been fixed already. Please update your database to version v2015.01.12.04.”
https://forums.malwarebytes.org/index.php?/topic/163422-open-hardware-monitor-071-beta-trojanmsil/
So the root of the problem is a bug with the software Malwarebytes (or their database).
Here is a scan with virus total
https://www.virustotal.com/en/file/55eb3733f183e304446a13f5eca8dc1f75c0e240ccef6b26f96fd5f9a7563e41/analysis/1421099210/
and the latest database showing the same file as clean once more.
Having minor glitches affecting nuvoTon NCT6791D chip on my ASUS Z97 SABERTOOTH. Yet, this tool is quite essential for me, especially tray temperatures. HWMonitor from CPUID reads more correct values at the moment. Could you have a look at those:
– Incorrect temperature readings (often just #, some even missing), and that is the most important aspect for me,
– as someone mentioned earlier, voltages are also often invalid (e.g. maximum VCore way under @4.2GHz), that is excluding extra hidden sensors.
I just hope you’re working on fixing NCT6791D support sometimes…
Are you running an ASUS tool in parallel? Please don’t do that, because some ASUS tools don’t respect the mutex conventions to avoid hardware access conflicts.
This is the most useful HW monitor. I much appreciate the gadget.
Thankyou so much.
Cheers Michael, for continuing your work on this!
I have a small request; to see the 12v reading under voltages. Thank you.
Project looks to be alive and well, good work with this, lot of nifty features.
Hello!
Thank you for all your job.
I have a question – is there a way to increase sensors polling interval? Most of the time 2000-3000 ms would be much better and “cheaper” in terms of preserving system resources.
Thank you.
thank you !!!
thanks for the new update 😉
Where I can find the console versions of this program?