Jump to content

Fiery

Administrators
  • Posts

    12633
  • Joined

  • Last visited

  • Days Won

    567

Everything posted by Fiery

  1. It has been resolved in the latest AIDA64 release.
  2. Our benchmark reflects the performance of GPUs using OpenCL. When there's a bottleneck due to OpenCL limitations then AIDA64 will reflect that too.
  3. In general, no, that's not the case.
  4. Thank you! It may mean the standard VBAT register in your sensor chip is not actually relevant for VBAT measurement.
  5. We've ordered a device and will start working on it as soon as it arrives in our labs.
  6. That screen should work as a regular monitor too, in which mode you can use the SensorPanel facility with it.
  7. Thank you. We've double-checked it, and according to the information available to us, AIDA64 uses the right sensor register to measure VBAT voltage. Did you see the VBAT voltage drop to under 1 Volt in the UEFI Setup?
  8. Yes, we're looking at a summer sale around late next month or early August.
  9. It will be supported by the next stable update of AIDA64 Business due next month.
  10. It means AIDA64 may use an incorrect sensor register to measure VBAT. Can you make test runs with both a depleted and a good battery?
  11. On that motherboard VBAT monitoring should work accurately.
  12. It should be able. What motherboard do you have?
  13. If you have no existing AIDA64 license, then you need a new license.
  14. You can do that with AIDA64 Business, AIDA64 Engineer and AIDA64 Network Audit using the /SILENT command-line option. You may also like the following guide about command-line automation offered by our business products: https://www.aida64.com/news/aida64-command-line-builder-tool
  15. Yes, of course.
  16. I've sent you a private message about this issue.
  17. It can be true since the GPU column lists the memory bandwidth that the iGPU can actually utilize through OpenCL. While the CPU column lists the full data path available for the CPU without the overhead of OpenCL and the overhead of the CPU-iGPU connection.
  18. Thank you for your feedback. Please note that ever since Android 7.0 (for whatever reason) Google decided to block apps from accessing several system files that were previously readable. That includes the files apps would need to show thermal sensor readings. Battery temperature reading is still available fortunately.
  19. Thank you! 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 helps.
  20. @fip00 @Sc00byD00 We've fixed the mentioned issues in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta Let us know if it helps.
  21. AIDA64 only supports the 9.16" version at this time. We'll work on implementing support for other Thermalright devices.
  22. You've got a private message 😉
  23. We've fixed the handling of CFA631 in 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.
  24. I've sent you a private message about this.
×
×
  • Create New...