Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12281

  • Joined

  • Last visited

  • Days Won

    541

 Content Type 

Everything posted by Fiery

  1. Fiery
    It can be due to a few issues. One of which is that the new Android platform (Nougat) blocks access to the necessary Linux kernel files that AIDA64 uses to detect the list of connected USB devices.
  2. Fiery
    Please show us the line in your logon script that launches AIDA64. If it includes sensitive information, please send the line in private message to me.
  3. Fiery
    We haven't received bug reports about AIDA64 vs. Aorus Graphics Engine other than the posts in this forum topic. The issue may be wide spread, but we haven't heard of a massive number of users complaining yet. We'll do our best to find a resolution soon.
  4. Fiery
    We will fix the issue in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new beta build is available for download.
  5. Fiery
    What do you mean by "always bugs" ? Is it overheating? Does it keep locking up (freezing) ?
  6. Fiery
    Do you have EC bank switching enabled in AIDA64 / main menu / File / Preferences / Stability? If yes, then please create the following 2 dumps and post them as TXT file attachments to your post at both 1.00V Vcache setting and 1.10V Vcache setting. We have 2 registers that may hold Vcache, and cannot decide which one is the right one I'm afraid 1) Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. 2) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Thanks, Fiery
  7. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers. 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
  8. Fiery
    I'm afraid we cannot find your license in our customer database. Please send me a private message with your full name and the email address that you've specified at your purchase. Thanks, Fiery
  9. Fiery
    As long as Mad Catz offers a similar SDK for RAT9 that it has for Strike7, we can implement that feature in AIDA64. But I haven't seen any such SDK offered by Mad Catz...
  10. Fiery
    It seems AIDA64 is unable to use its kernel driver. Make sure to install AIDA64 properly using its self-installer package from e.g.: https://www.aida64.com/downloads/latesta64xe Also make sure to have administrator privileges for the user that launches AIDA64.
  11. Fiery
    I'm afraid it's not possible to filter the reports for certain items. You need to come up with a script that identifies the sensitive lines and removes them. Regards, Fiery
  12. Fiery
    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
  13. Fiery
    It works fine now. Most likely it was a temporary issue about our download servers.
  14. 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. Let me know if it helps. Thanks, Fiery
  15. Fiery
    The above mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta
  16. Fiery
    The above mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta
  17. Fiery
    Thank you. Just to make sure we can identify the issue and pair it up with the right submitted report, please let me know what is the model (part number) of your Android device. On that particular day when you've submitted your report, we've received quite a few report submits
  18. Fiery
    Thank you for the clarification. We'll need to get a similar video card to let us reproduce the issue and perform special test runs to find which portion of the GPU detection code causes the collision with Aorus Graphics Engine.
  19. Fiery
    Please avoid posting the same issue into multiple topics. I'll soon reply to you in your main topic
  20. Fiery
    I've sent you a private message about this.
  21. Fiery
    I'm afraid I don't understand that. Can you please explain (in details) how the issue has been affected by the new beta build of AIDA64?
  22. Fiery
    I'm not that experienced in Linux, but I don't think any of those motherboards would have any issues running Linux.
  23. Fiery
    Thank you for your feedback. Please submit a report from the About page, and if possible, we will fix the reported issue in the next AIDA64 app update.
  24. Fiery
    AIDA64 memory stress test is supposed to allocate almost the entire free physical memory amount. You're not supposed to browse the web while the test is running, since the stress test will not leave enough free memory for other processes to work properly.
  25. Fiery
    AX1500i vs RM650i: Make sure to enable both Corsair AXi sensor support and Corsair HXi/RMi sensor support on both systems, in order for AIDA64 to properly handle both PSUs. They use very different protocols BTW, and the one used in the AXi PSU is prone to be less reliable than the more stable protocol of RMi. GPU TDP% should be available for both your GPUs. On your PC2 system (with GTX1050Ti) please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus 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...