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
    Yes, you need to use both options in the same time.
  2. Fiery

    Kraken x52

    Fiery replied to DiSa's topic in Bug reports

    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. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> USB PSU Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  3. Fiery
    I'm afraid it's not possible to detect such property for Android devices. We may add that fieldt to the hardware database of AIDA64 for Android later this year though.
  4. Fiery
    What motherboard do you have and which version of AIDA64 do you have installed?
  5. Fiery
    Try to run the AIDA64 System Stability Test twice. First, enable only the FPU subtest so you can put the maximum stress on your system when it comes to power draw and thermals ("heating it up"). Watch the Statistics tab for any abnormalities, and check if the system can stand the pressure for several hours. Meanwhile you can also enable Logging (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging) in case you want to analyze the data later on. When you're done with that, run it again, now with all subtests enabled. If and when you have a crash, check back the logs and see which voltages look abnormally low or high.
  6. Fiery
    Do you have another monitoring software running that may collide with AIDA64 performing the EC sensor access in the same time?
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. Fiery
    They can be any size.
  13. Fiery
    I'm glad to hear that, thank you for sharing!
  14. Fiery
    We don't have such a collection yet.
  15. Fiery
    Thank you, that's reassuring We'll enable multi-bank EC support for Asus Prime Z270 Series in the next AIDA64 beta update.
  16. Fiery
    Awesome! I'm glad you've had a great user and customer experience with your panel (and AIDA64 )
  17. Fiery
    It is an issue for such apps that report GPU usage through a graphics API layer. We fortunately measure GPU utilization directly.
  18. 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.
  19. Fiery
    We'll have to do some research on that. It doesn't seem to be particularly easy to detect the number of speakers.
  20. 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
  21. 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.
  22. Fiery
    AFAIK there's no software based method to adjust the brightness of Samsung photo frames
  23. 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.
  24. Fiery
    We will fix the issue by disabling SMBus support for your notebook in the next AIDA64 beta update.
  25. 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
×
×
  • Create New...