Invalid voltage readings reported in both overlay and captures
Opened this issue · 5 comments
Both the overlay and capture functions are recording all CPU related voltages as 1.55v on my system. Confirmed with hwinfo and the correct voltages show up there.
Both core and SoC voltages are effected. GPU voltages are unaffected.
System specs are in the attached image.
This issue appears to be caused by Windows Memory Integrity.
I ended up turning the feature off and then CapFrameX is able to capture a lot more data.
What CapFrameX version is this?
I tried both 1.7.1 and the 1.7.2 pre-release and both had the same issue.
Interestingly each version behaves a bit different. In 1.7.1, voltages show up as all 1.55v. In the 1.7.2 pre-release, they all show up as 0.00v.
In both CPU MHz is shown as 0MHz.
Actually, the v1.7.2 beta got a Ryzen voltage bug fix. If Memory Integrity causing this, there is nothing what we can do from our side. The effort would be extremely high (redesign of some of the core components from scratch).