Multiplier stuck because of AXTU ver:0.1.434

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   In 2013 I've submitted a topic @TweakTown reporting an issue with AXTU. The problem was that everytime AXTU is run the cpu multiplier was stuck @16x. During the discussion, an Asrock support member was aware of the situation, as AXTU was limiting the cpu performance and, also, preventing OC.

Here is part of the message I've written there:

 The fact is that, everytime I run any software such as CPU-Z, AIDA64, HWInfo64, and go into sleep mode, when wakening the turbo technology fails to work properly. For instance, if I run AIDA64, close it and make the system sleep, as soon as the system wakes up the multiplier will be limited to 36x. In the case of CPU-Z, most of times the cpu clock will be stuck at 16x. If I run HWInfo64, when the system is back on the turbo multiplier will be stuck as well, but @ 37x. The only way to solve the problem is restarting the system. At this time I haven't tried to overclock yet. The UEFI bios has almost all default values (I've enabled the C states instead of letting them as auto). Even so, I've been facing that odd behavior. After doing some tests, I've noticed that everything seems related to AXTU. I've come to that conclusion because, even if I don't run any of the mentioned softwares, but simply click on the AXTU overclocking tab while cpu is @16 x 100 and go back to monitoring (no values changed), as soon as I go into sleep mode and wake the system up, the multiplier will be stuck @16x. And that happens with no exception.(...)
As you can see, mysteriously the turbo clock is set down to 1600 Mhz. I've uninstalled AXTU and tested the same softwares and the sleep mode and, when woken up, the turbo technology worked flawless. Having that said, I'd like to know if it isn't really possible to have the AXTU and run system tools like AIDA64 and others without having multiplier problems. Is that a common bug, already known? As well, isn't there any way of disabling software overclock in the UEFI?

http://forums.tweaktown.com/asrock/52359-z77-extreme4-axtu-sleep-mode-issue.html?highlight=alexandrebr

As Asrock has released AXTU ver. 0.1.434, I've decided to give it a try and, for my surprise, the issue remains. On that occasion the support member provided an extra version that could fix the problem when not overclocking the system, allowing the user to monitor CPU Fan and adjusting bios settings.
Having that said, considering my MB has a few years (Z77 Extreme4), I'd like to know if the problem is known by Asrock and if users with newer MB's suffer from the same issue.