compare motherboard cpu voltage with hwinfo cpu voltage
compare motherboard cpu voltage with hwinfo cpu voltage
I've been attempting to achieve a consistent overclock on an fx 8320 @4.2ghz and am seeking clarity on which tool provides more precise voltage readings—the motherboard BIOS or HWiNFO. The CPU voltage is set to 1.46 in the BIOS, but HWiNFO displays Core VID: 1.363v with a core voltage of 1.332v. Stress testing with prime95 was also conducted. Temperatures are around 40°C, using a socket 60c.
Navek :
Idle, my core voltage increases to 1.428v - 1.440v and I'm still uncertain about how the LLC functions. I've turned it on a few times before only to notice my temperatures rise significantly beyond safe levels. My LLC settings are Auto, Enabled, and Disabled. That indicates a high Vdroop. In BIOS, Vcore is set to 1.46, but HFinfo displays 1.440v at idle. However, when I apply a load, Vcore drops to 1.332V. This might be due to an insufficient power supply or it could mean you need to activate LLC. When you turn on LLC, what does HFInfo show for Vcore during idle and under load (while running prime95)? Ideally, you'd like Vcore to remain close to the BIOS setting at idle and under load, which LLC assists with. But LLC can also lead to Vboost where you end up with more...
The CPU Voltage (Vcore) in BIOS is a configuration, but the actual value being displayed is what HWInfo shows. (For an accurate measurement you would need to test on the motherboard with a multimeter – though that isn’t essential).
If BIOS sets 1.46V and HWInfo reads 1.332V at idle, that indicates a 0.128V difference. This might seem significant, but it’s fixed by the motherboard and you can only change it to match the reported Vcore (as shown in HWInfo).
On the other hand, if HFInfo displays 1.332V Vcore during prime95 tests, it points to a high Vdroop that could be improved with some LLC adjustments.
What does HWInfo display for Vcore when idle?
You might also want to verify Vcore in CPU-Z to confirm what you’re seeing in HWInfo.
The CPU Voltage setting in BIOS is just a value, while what HWInfo displays reflects the actual measurement. For a precise reading, you’d need to test directly on the motherboard using a multimeter—this isn’t essential. If BIOS shows 1.46V and HWInfo reports 1.332V at idle, that indicates a 0.128V difference. This might seem significant, but it’s likely a hardware limitation; you can only change it to match the Vcore reported by HWInfo. On the other hand, if during prime95 testing you see 1.332V Vcore in HFInfo, it points to a high Vdroop that could be improved with some LLC adjustments. What does HWInfo display for Vcore during idle? You might want to verify with CPU-Z to confirm what you’re seeing. During idle, your core voltage typically ranges between 1.428v and 1.440v. The LLC settings available are Auto, Enabled, and Disabled (mobo m5a97 r2.0).
Navek :
Idle, my core voltage increases to between 1.428v and 1.440v. I’m also uncertain about the functionality of LLC; I’ve tried enabling it before only to notice my temperatures rise significantly beyond safe levels. The available LLC options are Auto, Enabled, and Disabled. This indicates a high Vdroop situation. In BIOS, Vcore is set at 1.46, but HFinfo displays 1.440v at idle. However, applying a load causes Vcore to drop to 1.332V. This could be due to an insufficient power supply or it might require implementing LLC.
When you activate LLC, what does the Vcore read in HFInfo during idle and under load (while running prime95)? Ideally, you want Vcore to remain close to the BIOS setting at idle and under load, which LLC assists with. Nevertheless, LLC can also trigger Vboost, giving more voltage than requested in BIOS—so monitor that as well.
If I were you, I’d revert the multiplier to 40 (for a 4.0GHz frequency), set Vcore in BIOS to 1.350V, enable LLC, and observe the Vcore reading in HWInfo at idle and during prime95 execution. Ideally, it should stay near 1.350 (perhaps around 1.340V). That would be ideal.
If you manage to keep Vcore stable at just 0.01V above the BIOS setting, I’d run prime95 and assess stability. If everything holds, increase the multiplier to 41 (for a 4.1GHz), check your Vcore at idle, then start prime95 and observe stability. If successful, raise the multiplier further to 42. Continue monitoring Vcore during idle and testing while keeping an eye on temperatures.