Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11334

  • Joined

  • Last visited

  • Days Won

    476

 Content Type 

Everything posted by Fiery

  1. Fiery
    It's most likely because AIDA64 is polling your GPU(s) and that activity prevents your video driver from putting your video card(s) to sleep.
  2. Fiery
    Thank you for your feedback!
  3. Fiery
    Thank you for your feedback
  4. Fiery
    Please upgrade to the latest beta version of AIDA64 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 makes a difference.
  5. 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.
  6. Fiery
    Thank you! Please 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 how it works.
  7. Fiery
    Now https://www.aida64.com/downloads/latesta64xebeta
  8. Fiery
    Best option is #2 since it wouldn't collide with Asus' own solutions. We've fixed the missing sensors in the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta I'm not sure what's happening about SensorPanel. Please check this beta and let me know if that issue persists.
  9. Fiery
    The above mentioned new beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta
  10. Fiery
    For your motherboard you can either: 1) Use AIDA64 v5.99.4900 and disable Asus WMI sensor support or 2) Use AIDA64 v5.99.4944 and enable Asus WMI sensor support Option #1 will however collide with Asus AI Suite or the BIOS interface of the sensor solution on your motherboard. So it's best to go for option #2.
  11. Fiery
    It's quite possible that Storage Executive uses a fixed thermal offset of +5 Celsius on the measured Enclosure Temperature values. If it's possible, please try to put a bit of a pressure on the drive to make it heat up over 30 Celsius, and check if the difference between what AIDA64 reports and what Storage Executive reports stays the same 5 Celsius. If yes, then we will implement the temperature offset for MX500 in the next AIDA64 beta build.
  12. Fiery
    Thank you for the data! We will fix the issue in the next AIDA64 beta update. I will post a message into this topic once the new beta becomes available for download.
  13. Fiery
    That RGB fusion issue is fixed already, and the fix is inherited by the newer and newer beta updates, as well as the stable updates in the future.
  14. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor 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
  15. Fiery
    Thank you. I'm afraid the AIDA64 kernel driver is still not working on your system. We've done several test runs, and the updated kernel driver in the latest AIDA64 beta build of 4944 works fine. So the issue must be that either the old kernel driver got stuck on your system, and the new beta fails to load it for some reason. Other than reinstalling AIDA64 and restarting Windows, I'm not sure what else can be done In other cases that procedure fixes similar issues all the time.
  16. Fiery
    I'm sorry to hear that SPF-72H fails to provide a stable mini-monitor mode function. We'll add a warning to the AIDA64 LCD Guide about this.
  17. Fiery
    It's very odd Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor 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
  18. Fiery
    Please note that it's not possible to diagnose such issues remotely. You may want to take your phone to a local specialist and have it checked out.
  19. Fiery
    Thank you for your reply. Something must have been mixed up after the upgrade. Please try to close AIDA64, download the latest beta ZIP package, extract the whole contents into the existing installation folder of AIDA64, and let it overwrite any existing files. Restart Windows one more time, and check if it works. If not, then please check if your motherboard is properly identified (on the Computer / Summary page of AIDA64 for example).
  20. Fiery
    I've sent you a private message about this issue.
  21. Fiery
    Thank you for your feedback!
  22. Fiery
    Awesome!
  23. Fiery
    Just like in other cases, I will post a message into this topic once the new AIDA64 beta build becomes available for download.
  24. Fiery
    Thank you for your help. We'll rename the temperature labels accordingly, and also implement caching to make sure the Chassis fan reading can be measured more stable. IMHO it's not the fault of your motherboard or AIDA64, but more like due to the fan itself providing unstable fan speed signals to the motherboard. We'll apply those changes to the next AIDA64 beta update. As for DIMM temperatures, simply enable DIMM thermal sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64.
  25. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
×
×
  • Create New...