Search results

Thanks for the info, makes sense.

Just to add a bit more nitpicking: despite core clocks showing 4600+MHz, Core ratios doesn't show 45.5x but ~44.5x, L3 Clocks aren't the same 4600+ as core clocks and the Frequency limit - global doesn't allighn with effective core clocks (stays around the 4536 MHz mark).

Ok, seems to be working as it should in single core loads too. Not sure if I needed to run the testing app for longer, but now it shows 4600+ in Snapshot polling too. EDIT: the reason for single core loads not showing up correctly in my previous post with the beta is that I forgot I had an app...

FCLK, UCLK - fixed All core load clocks - fixed Single core loads - not fixed. The report doesn't show it going above 4536 MHz where it should be 4638 MHz.

Yes, but only Core 0 effective clocks seems to deviate from the group. However, it could be it's just clock stretching as I haven't finalized OCing yet. Screenshot from a couple of passes of single core loads, captured with 500 ms update interval. Debug file is created with Snapshot polling...

Thanks for the quick reply. Yes, disabling Snapshot CPU polling fixes the core clocks readout. Looking forward to newer builds, will report if the UCLK/FCLK is fixed.

Additional screenshot during all core load. Something is definitely wrong.

Running 5800X3D CPU and latest stable 7.42-5030 build on Win 10. The CPU has 44.5x multiplier for all core loads and 45.5x for single core boost. When OCing the BCLK to 101.9375 MHz, HWInfo will presumably report FCLK, UCLK and boost clocks incorrectly while it's showing BCLK running at 101.9...

Thank you for the quick response. Hopefully newer driver versions will fix the issue.

Here's a new dbg file, hopefully you can figure out the source of the problem. The issue might be occurring more frequently when I use the reset values, but I'm not certain.

I'm running the latest drivers 22.5.2 The same was happening with 22.5.1 and one version before that, unfortunately can't recall which version started exhibiting the issues. I'll try running the dbg mode again when the issue reoccurs, if it helps any.

Hello, at some point the above mentioned sensor will get stuck at a certain temperature value and restarting HWiNFO v7.24-4770 will not fix it, it will return to normal readout only after reboot. I have attached a report and dbg file: when I noticed the value is stuck, exited HWiNFO, started it...