Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12414

  • Joined

  • Last visited

  • Days Won

    550

 Content Type 

Everything posted by Fiery

  1. Fiery
    I'm afraid we're not experienced with overclocking, so we cannot help you with that. But hopefully someone else can chime in. You may also want to ask around in XtremeSystems or similar forums that are geared towards OC and system tuning.
  2. Fiery
    It depends on what the concurrent software is. If it's Asus AI Suite, then you need to uninstall it to make sure its background services are also removed. If it's another monitoring software, then closing it is enough.
  3. Fiery
    AIDA64 uses Windows default font size. You need to increase that system setting in case you find the text in AIDA64 too small. If you mean AIDA64 for Android, then in AIDA64 Settings there you can adjust text size to smaller or larger than the default value.
  4. Fiery
    We will fix the issue in the next AIDA64 beta update. I will post a message into this topic once the new beta build is available for download.
  5. Fiery
    If you have an Intel RST or RSTe RAID controller, try to update its drivers to the latest version. BTW, "nothing changed" may well be true for the hardware layer, but in the background Windows 10 could well have updated or messed up with the RAID drivers and that could cause issues when a software is trying to enumerate disk drives.
  6. Fiery
    They can be any size.
  7. Fiery
    I'm glad to hear that, thank you for sharing!
  8. Fiery
    We don't have such a collection yet.
  9. Fiery
    Thank you, that's reassuring We'll enable multi-bank EC support for Asus Prime Z270 Series in the next AIDA64 beta update.
  10. Fiery
    Awesome! I'm glad you've had a great user and customer experience with your panel (and AIDA64 )
  11. Fiery
    It is an issue for such apps that report GPU usage through a graphics API layer. We fortunately measure GPU utilization directly.
  12. Fiery

    Info about caches

    Fiery replied to MAA's topic in Brainstorming

    Thank you for your suggestion. We currently cannot promise anything about future feature additions.
  13. Fiery
    We'll have to do some research on that. It doesn't seem to be particularly easy to detect the number of speakers.
  14. Fiery
    GPU PerfCap is not a mutually exclusive list of values but a bitmask. So not just one could happen at any given time, but one or more in the same time. That's why it's quite difficult to handle it as an integer value or any other numeric value
  15. Fiery
    Thank you for the dumps. Currently we have no plans to decouple the slow sensor modules from the main sensor module due to it being already very complex. AFAIK it's not possible to talk to HXi/RMi Series PSUs through Corsair's software. We do not have plans to add more power readings for your PSU, especially about the power efficiency which is a calculated value and IMHO it's not something that is accurate or has much foundation.
  16. Fiery
    AFAIK there's no software based method to adjust the brightness of Samsung photo frames
  17. Fiery
    That's a notice that's displayed only on Windows 10 systems -- since AIDA64 Build 5006 -- on the AIDA64 Cache & Memory Benchmark panel after obtaining a memory bandwidth score to explain the relevance of each score. When you hover the mouse over those "i" icons, it will display: (for Memory Read) Read performance measurements offer insight into CPU architecture, but do not reflect typical application workloads. (for Memory Write) Write performance measurements offer insight into CPU architecture, but do not reflect typical application workloads. (for Memory Copy) Copy performance measurements offer the best insight into the effect of the CPU architecture and memory subsystem on typical memory-bound application workloads.
  18. Fiery
    We will fix the issue by disabling SMBus support for your notebook in the next AIDA64 beta update.
  19. Fiery
    I suppose it's more because of the slow gathering of sensor readings rather than because of a slow rendering of SensorPanel or RemoteSensor layout. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling 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
  20. Fiery
    I suspect the issue is either CrossFire or the improper implementation of AMD's own PMLog API in their recent video drivers. Try to disable Multi-GPU support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it helps. If it doesn't help, try to disable GPU sensor support on the same page of the Preferences as well, and restart AIDA64.
  21. Fiery
    That 200+ Celsius reading for DIMM temperature is an invalid reading and should be ignored. At such a high temperature your memory modules would get irreversibly damaged. The invalid reading could be because of a collision between AIDA64 and another monitoring software trying to access the sensor chip concurrently.
  22. Fiery
    Please check the temperatures with the following new beta build of AIDA64: https://www.aida64.com/downloads/latesta64xebeta
  23. Fiery
    Please check if the memory stress test gets more responsive with the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta
  24. Fiery
    Thank you! Please check the following beta about the IPMI issue: https://www.aida64.com/downloads/latesta64eebeta
  25. Fiery
    Thank you. Quite frankly, I wish we had the time and resources to develop a Stream Deck plugin for AIDA64 from scratch. But in the current situation I cannot make any promises about it. So it's either the current solution or taking over the whole device -- but none of those seems to be 100% suitable for your requirements.
×
×
  • Create New...