Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12230

  • Joined

  • Last visited

  • Days Won

    539

 Content Type 

Everything posted by Fiery

  1. Fiery
    Thank you, we've added them to the following new beta build of AIDA64: https://www.aida64.com/downloads/latesta64xebeta
  2. Fiery
    Thank you! Please also post an nVIDIA SMBus Dump.
  3. Fiery
    The most delay, cca. 700 millisec is caused by the Aquaero sensor monitoring module. Aquaero and AquaComputer devices in general use slow USB protocols that take a lot of time to poll.
  4. Fiery
    LCD interface to use depends on the script you're using.
  5. Fiery
    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. If it still doesn't work, please post an updated RAID Dump and SMART Dump so we can check out the registers.
  6. Fiery
    It's me Let me know how can I help you either here on in private message.
  7. Fiery
    Thank you for your feedback! If you mean the GPU clock disappears/reappears, then it's normal for 6800 XT / 6900 XT video cards. It's due to the fact that the new AMD GPU generation introduced a very deep sleep where the driver reports zero MHz GPU clock to AIDA64 -- which is considered an invalid reading and triggers the relevant SensorPanel/LCD item to disappear. We'll need to come up with a workaround for that issue.
  8. Fiery
    Thank you for your kind words. What is listed on the Chipset page are the nominal values for the hardware, and not measured values. They cannot be shown on the SensorPanel. Our Capellix device has arrived, and we're already working on it. Give us a few more days to have something to try
  9. Fiery
    Thank you! Can you please check if perhaps the issue comes up after your computer returns from sleep?
  10. Fiery
    High Flow Next is fully supported by the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta
  11. Fiery
    Thanks for you feedback
  12. Fiery
    It depends on a number of factors, but mostly it depends on how the laptop cooling is implemented.
  13. Fiery
    1) AFAIK 5VSB and 12VSB are not measured by your motherboard. 2) The mentioned 3 fans are already measured for your motherboard. Please check if they're there on the Computer / Sensor page of AIDA64. 3) We're planning to roll out the new beta in a few days from now. 4) It's very difficult and time consuming to support every single high-end motherboard in AIDA64. We do our best, but such motherboards with a complicated sensor layout are always a big challenge.
  14. Fiery
    While I see your point and understand where you're coming from, we're still not interested in either averaging anything, or relying on SDK's when it's not absolutely necessary.
  15. Fiery
    Thank you for the dumps! The issue will be fixed in the next AIDA64 beta update. I will post a message into this topic once the new beta becomes available for download.
  16. Fiery
    No, it's not, since the SteelSeries LCD module supports hot-plug. Do you have other SteelSeries-made USB devices connected perhaps?
  17. Fiery
    Thank you I'm surprised that AMD found no such issues about Renoir when they were doing QC...
  18. Fiery
    I'm afraid we ran out of ideas on how to improve the EC interaction
  19. Fiery
    Measuring or monitoring anything during benchmarking is a bad idea since it would negatively affect the benchmark result. Therefore all AIDA64 background monitoring activities have to be paused while a benchmark is running.
  20. 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 makes a difference.
  21. Fiery
    You can use custom state images, but you cannot expand the number of states.
  22. Fiery
    Please note that unlike notebook PC batteries, Android devices do not feature sophisticated smart batteries. It sadly means that battery wear level or battery health estimations cannot be measured or computed.
  23. Fiery
    We've removed the links since they contain references to illegal (pirate) product keys of AIDA64. Since the transaction of you purchasing a hardware also involves distributing illegal product keys for our software, it's not our responsibility to assist you in this issue. Try to contact the seller and ask for technical support from them. If you'd like to continue using AIDA64 by purchasing a legal license key from us, please let me know in private message. This topic -- due to its course about illegal content involved -- has to be locked here.
  24. Fiery
    You can reset your OSD settings by closing AIDA64, navigating to AIDA64 installation folder, opening AIDA64.INI (settings file) in Notepad (or any other text editor of your choice), and removing all lines starting with OSDItem_ Please note that the explained process will delete all your customization about your OSD Panel. I'm not sure if I understand your issues about the sensors monitoring and whether it's separate from the OSD Panel reset issue. Is the missing +3.3V rail the only problem, or you have multiple issues that you're looking to solve? Edit: We will fix the missing +3.3V voltage reading issue in the next AIDA64 beta update.
  25. Fiery
    On the SensorPanel just use the mouse right-click context menu --> SensorPanel Manager --> Export to save your layout into a file. You will be able to select the folder and file name.
×
×
  • Create New...