could not get power table

[iamhasantan]

AMD Ryzen 3 3100/MAG X570 Tomahawk (MS-7C84)/BIOS 1.63/SMU 46.70.0/ComboAM4PIV2 1.2.0.2

[irusanov]

I would need some more information.

• Does it refresh at some point after clicking "OK"?
  If the power table cannot be read, then fclk, mclk and uclk will be empty, along with vddp and vddg voltages.
  If they show up at some point, then something else is blocking the app from accessing the power table when launched.
• Does it happen every time?
• Do other tools, such as hwinfo, show the usual information?
• Are there some other tools running at the same time?
• A debug report would also be helpful

Thanks!

PS: The error simply means the power table is empty or the command to get it failed for some reason within the specified timeout (10sec).

[k1rOuX]

Hi, I have the same issue,

• after click ok it doesn't refresh, only 3 voltage are missing MCLK, FCLK and UCLK are correctly displayed.
• It happen everytime.
• other tools are working (HWinfo64)
• nothing else running, I like minimalist boot settings.

My config: Ryzen r5 3600 - MSI x470 Gaming Pro Max (bios up-to-date with agesa 1.2.0.2) - ram 2x8gb GSkill Trident Z Neo

Debug_Report_26983950,2393232.txt

PS: I just noticied that the autor is also on a msi board with agesa 1.2.0.2. It may be something relating to this version?

[irusanov]

It seems to be AGESA 1.2.0.2 related (and maybe MSI).
The issue is current version of the app checks if first value is 0 (zero) and it seems that's always true with this new AGESA.
You can see that in the debug report, under "SMU: Power Table" section, Offset 000".
I've done this for performance reasons and until now it always had the PPT value at this offset.
I don't know what's wrong and why it changed with that AGESA version. Basically it means PPT is 0 (disabled)

I'm going to release a new version with a bugfix, but will now have to check if the whole table contains only zeroes, not just the first offset.

You can ignore the Error message for now, although I know it is annoying.

[k1rOuX]

No prob man, thing happen. Keep up the good job😊

[iamhasantan]

My machines been up for a few days and I mysteriously don't get the error now either, suspeciously I havnt changed any settings in the UEFI BIOS Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: k1rOuX ***@***.***> Sent: Tuesday, April 27, 2021 7:06:55 AM To: irusanov/ZenTimings ***@***.***> Cc: b1tbucket ***@***.***>; Author ***@***.***> Subject: Re: [irusanov/ZenTimings] could not get power table (#19) @irusanov<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Firusanov&data=04%7C01%7C%7C53965598d52043d3c14a08d908f73d56%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637550680246069522%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=B29wdmCIFAOW0j%2FEhvLLpIy4Tuo1Px3WjU9ExjytWdo%3D&reserved=0> hey man, little feedback again. It seem that this issue is related to a UEFI settings, cause I just tryed to set back a setting in UEFI, in amd CBS > SoC/FCLK part, I dont remember the name rn but the description was "enable to force LCLK to run full speed, but it impact power saving" I only have enable or auto. Enable was what I had until now. I tryed to put back on auto, didn't saw any change about FCLK / UCLK / MCLK , but now Zen Timing working fine and even HWinfo64 show me more info, especially watts and amperes, also FCLK MCLK UCLK.. I'll try to take some picture — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Firusanov%2FZenTimings%2Fissues%2F19%23issuecomment-827147172&data=04%7C01%7C%7C53965598d52043d3c14a08d908f73d56%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637550680246069522%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CtaMoEdJ%2BIAZgdm%2F7exVQMajVfCIxJCBob6joX4NHlg%3D&reserved=0>, or unsubscribe<https://apac01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMWR5F4OZUZJXJKFQV5IP33TKXIW7ANCNFSM426S5XCQ&data=04%7C01%7C%7C53965598d52043d3c14a08d908f73d56%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637550680246079477%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=gUd00gBx%2FoBtdwmihmTw%2BaBcPe2lJ2M8LamsKW5qJIw%3D&reserved=0>.

[k1rOuX]

@irusanov hey man, little feedback again.I found a workaround. this issue is related to a new UEFI settings (or I never noticied it before lol), in "advanced\ AMD overclocking" (not the normal OC part, but in the part where you usually set PBO) called "LCLK Control". I had it disabled until now. I tryed to put back on enabled, I dont see any change about FCLK / UCLK / MCLK , but now ZenTiming working fine and even HWinfo64 show me more infos, especially watts and amperes, also FCLK MCLK now...
I have no idea what is this LCLK frequencies (it's not FCLK, UCLK or MCLK) but from what I saw it seem to be related to PCIe stuff oO

So before change it was like this:

And now :

Hope it will help =)

[irusanov]

@b1tbucket, @k1rOuX Thanks for feedback!
I have a new beta/debug build which should not show that error.
ZenTimings_v1.2.4.234-debug.zip

[k1rOuX]

okay let's try =)

[k1rOuX]

@irusanov yep no error message anymore, here is the debug output if you need
Debug_Report_26991250,7275392.txt

[k1rOuX]

What ? ^^

[irusanov]

That's valid for all 3600. They have 2 physical cores disabled (one from each CCX)

[iamhasantan]

I can't explain it as i've not modified any settings on my end however the error is gone on the stable build (same build i used when I opened this issue) and works fine also on the debug build even after hard power off.

I'll keep an eye out for it but perhaps we can close this issue off now. My setting for LCLK DPM is set to auto btw. I suspect that the motherboard after a few reboots retrained its settings accordingly.

[irusanov]

I will close it when this version gets released. Thanks for cooperation, really helped me solve the issue.

[k1rOuX]

@irusanov yeah I already heard something like this, it's basically low binned 3700/3800, with core disabled. But it's the first time I see 8 core displayed in a tool ^^ I miss the good old time where we could unlock hidden cores on old AMD phenom cpu ^^

@b1tbucket yep it's due to this settings. Fun fact in my bios, when I change it then press F10 to save and exit, it say I didn't change anything xD. Btw it seem to allow my fix CPU overclock to downclock a bit (from 4.5 to 4.2 at idle in task manager, no change in HWinfo64, I use the 1usmus power plan).