Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12285

  • Joined

  • Last visited

  • Days Won

    541

 Content Type 

Everything posted by Fiery

  1. Fiery
    I'm confused. Are you talking about benchmarking or stress testing?
  2. Fiery
    To me it seems more like a collision on the sensor chip access, and not a hardware failure. Well, except for the case when AIDA64 reports a failure with that big red screen of course Make sure to check the voltages with Gigabyte's own monitoring software, with all other monitoring software not running in the background.
  3. Fiery
    No, since our benchmarks are designed to squeeze out the last bit of performance from actual processors. We use such extreme optimizations that take actual hardware architecture into account. If you distort the underlying architecture by e.g. removing a lot of CPU cores from a multi-core CPU in a virtualized environment, our optimizations may or may not work as great as on a non-virtual environment. That all doesn't mean that you cannot obtain valid benchmark results in a virtual machine. But the extreme optimizations will not work 100% in such an environment.
  4. Fiery
    It's most likely because Asus has implemented a temperature offset on the CPU temperature measurement. It may be because the previous values were inaccurate, and so the new values are more representative of the actual thermal status of the processor.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. Fiery
    What do you mean by "always bugs" ? Is it overheating? Does it keep locking up (freezing) ?
  10. 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
  11. 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
  12. 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
  13. 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...
  14. 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.
  15. 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
  16. 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
  17. Fiery
    It works fine now. Most likely it was a temporary issue about our download servers.
  18. 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
  19. Fiery
    The above mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta
  20. Fiery
    The above mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta
  21. 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
  22. 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.
  23. Fiery
    Please avoid posting the same issue into multiple topics. I'll soon reply to you in your main topic
  24. Fiery
    I've sent you a private message about this.
  25. 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?
×
×
  • Create New...