No one suggests using hwinfo64 for tracking temperatures and voltages
No one suggests using hwinfo64 for tracking temperatures and voltages
Following the incident, if you have a gigabyte motherboard, use System Information Viewer only. For an ASUS board, stick to ASUS software to track temperatures and voltages. After assembling my new setup, I added hwinfo64 to monitor temps and voltages. Suddenly, it crashed with an alert for Vcore 2.3V, then after half an hour a spike to 2.0V occurred during YouTube videos. I reported this to my dad, who installed System Information Viewer for me since I'm using a Gigabyte Z170X gaming 5. I've been running it continuously for eight hours without any issues—Vcore stayed normal, ranging from 0.024 to a peak of 1.27 and 1.29. Even during a stress test with AIDA at full voltage, stability remained at 1.27. Proof? Both tools showed normal readings simultaneously.
It varies from board to board and operating system updates. For me, ASUS's system monitoring keeps showing my board at -170C with CPU voltage around 0.023v. The most trustworthy source is usually the BIOS. It’s wise to try several monitoring tools to compare results and rely on the temperatures reported by most.
You might choose a third-party tool because it offers better organization, efficiency, and features that can simplify your tasks compared to handling everything manually.
I haven't finished reading your message yet. I've been using hwinfo64 for at least eight hours, checking every half hour, but I haven't seen any VCore spikes. I also run SpeedFan for extended periods and it shows a negative 88°C temperature. I'm using AIDA64 since I built my PC, and neither VCore spikes nor negative temperatures have occurred. Could you clarify what you're observing?
I could ask you the same thing. The Vcore error points to a software issue since Skylake is relatively new. You're correct not to use it due to this reason. -88C might be a bad sensor or a software bug. Because it's the mobile temperature sensor, the problem is more likely in the sensor itself rather than a general software flaw. E: This doesn't mean the software is inherently bad for everyone, especially those with older or AMD systems. It's not that the software is causing problems on its own, and there isn't another capable software doing the same thing.