You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When changing the p-state from 100.0000 to 104.5. It shows in zen timings that the KClk and Bclk has synced with the setting applied. However, during testing on both p-state settings. 100.0000 always yields the same results as 104.5. This is in cinebench r15.
the system can crash if the p-state is set higher to example - 104.75. But it’s not consistently crashing. Which signifies that the change is taking place. But I have no idea where. As adjusting the p-state clock. Should result in better performance.
The text was updated successfully, but these errors were encountered:
Z1-extreme rog ally - testing the program setting bclk to 106 causes instant crash. It runs stable at 104.5. Consistently causes lower performance in graphical benchmarks. Shows no improvement or reduction in memory tests (even if zen timings says that clocks have changed) and shows no improvement or slowdown in CPU only benchmarks both in single and multithreaded scenarios. Is it possible that it doesnt apply the BCLK properly?
On my lenovo laptop, going over a certain bclk slows it down. I can't tell if the bclk option does something on the Z1 as I don't have the device. Have you tried testing at 101.5 - 102?
I think the better option would be to set curve optimizer values if that is even allowd on that device, it would get better results than adjusting bclk, which is a bad idea on these locked chips.
Have you checked if cpuz detects the higher bclk?
When changing the p-state from 100.0000 to 104.5. It shows in zen timings that the KClk and Bclk has synced with the setting applied. However, during testing on both p-state settings. 100.0000 always yields the same results as 104.5. This is in cinebench r15.
the system can crash if the p-state is set higher to example - 104.75. But it’s not consistently crashing. Which signifies that the change is taking place. But I have no idea where. As adjusting the p-state clock. Should result in better performance.
The text was updated successfully, but these errors were encountered: