Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11740

  • Joined

  • Last visited

  • Days Won

    503

 Content Type 

Everything posted by Fiery

  1. Fiery
    .sensorpanel files can be imported directly into your SensorPanel layout. Right-click on SensorPanel --> SensorPanel Manager --> Import.
  2. Fiery
    Yes, it is.
  3. Fiery
    Once you change anything about your SensorPanel, the work is saved to the AIDA64.INI file that you can find in AIDA64 installation folder. You can backup that file if you need to save your work to a safe place.
  4. Fiery
    No, thank you for the USB dump, we're working on the implementation. I'll send you updates in this topic.
  5. Fiery
    Actually Task Manager does it in a special way, not AIDA64. Task Manager scales the actual CPU utilization values with Turbo Boost headroom. If you disable Turbo Boost, you can see that the values will match between AIDA64 and Task Manager. Previously Task Manager didn't do that, but Microsoft -- with their infinite wisdom -- figured it would be great to bend the truth
  6. Fiery
    I've sent you an email about this.
  7. Fiery
    Thank you! We've implemented further fixes about ASRock Z790 Taichi monitoring in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
  8. Fiery
    Merci.
  9. Fiery
    The rest of the difference is due to the calculation method Task Manager uses that takes Turbo Boost into account too. It's not a bug in either AIDA64 or Windows, it's simply a different way of calculating CPU utilization. If you disable Turbo, you will see that the CPU load measurements will match between AIDA64 and Task Manager. Check my 2 related posts above (November 23, 2022)
  10. Fiery
    @Qwinn @nin6996 @DBentt @Amit Paz @Martin Piotrowski @JarleH @Mach @Sayoung @plzt @hosty @odt_jarvis @Tomas914 @A Blade Of Grass @ozkr_tech We've fixed the suck CPU temperature issue about Asus X670 motherboards in the latest AIDA64 beta build available at: https://www.aida64.com/downloads/latesta64xebeta
  11. Fiery
    @cbo305 @rdorian Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta You need to activate (tick) the last option on the AIDA64 / main menu / Preferences / Stability page called Windows 11 CPU utilization measurement workaround. Let me know if it helps to obtain more realistic CPU utilization measurements.
  12. Fiery
    Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it works as expected now
  13. Fiery
    You need RTSS or Fraps to measure FPS and send the measurements to AIDA64.
  14. Fiery
    Gauges are not supported by the RemoteSensor and Logitech Arx LCD modules. They have Arc Gauges instead.
  15. Fiery
    Thank you for your feedback!
  16. Fiery
    Thank you for your feedback! That could be due to the way Task Manager calculates CPU load: it takes into account the headroom that's provided by Turbo Boost. Try to compare CPU load values with Turbo disabled (either in BIOS Setup or AIDA64 CPU Tweakings).
  17. Fiery
    Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.
  18. Fiery
    @BeanZ @AJ1 Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta You need to activate (tick) the last option on the AIDA64 / main menu / Preferences / Stability page called Windows 11 CPU utilization measurement workaround. Let me know if it helps to obtain more realistic CPU utilization measurements.
  19. Fiery
    @a3v01d @Nenesse007 @AäronWydoodt @rgp @doncarlos @Stratdevel @JPALEOLOGOS @Jethro @Babaz @Uroš Huzjak @Haggbo @rdorian @Squall Leonhart @Benni231990 @Pepo @jklei18 @Eireman @fossi @Slipknot79 @EvolutionVR @zynaps @geoff.s @jimmysombrero @mondueo @Raymond David Smith Jr. @mfung1985 @Peabutt Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta You need to activate (tick) the last option on the AIDA64 / main menu / Preferences / Stability page called Windows 11 CPU utilization measurement workaround. Let me know if it helps to obtain more realistic CPU utilization measurements.
  20. Fiery
    About the CPU utilization measurement issue, please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta You need to activate (tick) the last option on the AIDA64 / main menu / Preferences / Stability page called Windows 11 CPU utilization measurement workaround. Let me know if it helps to obtain more realistic CPU utilization measurements.
  21. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery
  22. Fiery
    What store was it? You can send it to me in private message too. Please note that several criminals run websites where they sell non-genuine (pirate) licenses for well respected software for incredibly low prices. Sometimes 1/10th of list price. We never sell our licenses that cheap, and we don't have any resellers who would be able to push the price that low. So when the deal is too good to be true, you should know what you're getting.
  23. Fiery
    Let's clear the air here. This is not a bug in our software. It's a bug of the operating system. I hope you're banging on Microsoft's door at least with the same ferocity than on our door. The fact that Microsoft was unable to fix this bug of their operating system for months now means something. We're still unable to reproduce the issue on our own test systems. Trust me, we've tried quite a few hardware platforms with Win11, but none has issues about CPU usage reporting. I have no idea what particular bit of hardware or maybe firmware setting that triggers the issue to come up. Usually we're hesitant to implement a workaround for an OS bug without being able to reproduce the issue. If we cannot reproduce it, it's very difficult to validate and QC the workaround. The nature of this issue is also very fundamental and affects multiple features of AIDA64. Therefore, we have to be extra careful to alter the existing code _if_ we cannot reproduce the issue and then check how the new code works on both older systems (without the OS bug) and the new ones (with the OS bug present). But, our current projection is that we'll be able to roll out a new beta build with an optional workaround in a few days from now. It will have to be optional unless we can "catch" the OS bug in our labs and have a proper test environment built around it.
  24. Fiery
    Do you have a valid, genuine AIDA64 product key that you've purchased in our Online Store?
  25. Fiery
    The above mentioned new AIDA64 beta update is now available for download at: https://www.aida64.com/downloads/latesta64xebeta
×
×
  • Create New...