Yes, that's me. I just had no time to update the OP here, because I had to travel.
Yes. The download link is directly from my github account. I just modified ZenStates site a little to release ZenTimings.Hopefully 1.10 above is from the same dev!
Protonrom is my domain from the time when I was making a custom Android ROM for some smartphones and I'm using subdomains since I'm still paying the hosting.
I could change the value that is read to the strap and not the real frequency. Then it will always show a steady frequency. In fact it was a new thing to me as well, because it doesn't happen on my motherboard, regardless of settings.I don't know if this is a software bug or I'm just not familiar enough with how the infinity fabric works but mine is fluctuating from 745 mhz to 1900 mhz at idle. Is this a BIOS setting and if so, how do I lock the FCLK in place at 1900 mhz?
Edit: NVM, Google is wonderful thing. I had to disable DF C-States buried in AMD CBS in the BIOS. Will disabling this give me better FCLK stability?
It is a bug in the app which is a result from the "configuredClockSpeed" reported incorrectly on your system (Freq field is halved).Clocks are halved for me and both tRFC and tREFI latencies are doubled.
That frequency is then used to "correct" FCLK, MCLK and UCLK in an attempt to take blck in consideration.
FCLK, MCLK and UCLK are always reported on a 100MHz BCLK base, while configuredClockSpeed shows real frequency on some systems, so I'm basing my correction factor on that one.
In your case, those 3 frequencies get halved due to this. I will have to improve the correction mechanism to fix this bug.
TREFI (ns) and TREF (ns) are also a direct victim of the same halving, since they are calculated based on MCLK.
Thanks for the report!