Jump to content

Fiery

Administrators
  • Posts

    11545
  • Joined

  • Last visited

  • Days Won

    489

Everything posted by Fiery

  1. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor 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
  2. It's not possible right now. What keyboard do you have?
  3. All of them are correct values.
  4. Please check if the Computer / Sensor page in the left menu? Also, does the Motherboard / SPD page work?
  5. Are you sure the GPU is not available anymore? Or it's just not available for stressing or benchmarking in AIDA64 anymore?
  6. Please note that on many devices the standard Android Battery API is inadequately implemented, and fails to provide proper charge counter information for the battery. If you want, you can hide the incorrect charge counter information from the Battery page by unchecking the charge counter option in the AIDA64 Settings.
  7. It is due to an OpenCL driver issue. Try to update your video drivers that will also update the OpenCL drivers for your GPU.
  8. On many devices the standard Android Battery API is inadequately implemented, and fails to provide proper charge counter information for the battery. If you want, you can hide the incorrect charge counter information from the Battery page by unchecking the charge counter option in the AIDA64 Settings.
  9. It's hard to tell since "technical errors" can be a lot of different issues. Give it a try and you will see what you can do with it. It's free of charge to use it on Android, iOS and Sailfish mobile platforms.
  10. 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 the problem persists.
  11. Thank you for your support and feedback!
  12. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor 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. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor 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 --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  14. We will fix the abnormal chars in the Simplified Chinese language module issue as well as the incorrect strings displayed on the NetUpdate message box issue in the next AIDA64 beta update. The name of languages cannot be fixed in the Preferences because that's just due to a limitation of AIDA64 being a non-Unicode application.
  15. It seems your laptop has no PCH diode thermal measurement enabled by the BIOS.
  16. DIMM temperature measurement has to be enabled in AIDA64 / main menu / File / Preferences / Stability / DIMM thermal sensor support. Please restart AIDA64 after altering that option. We'll check what's up with CPU VDD and CPU VDDNB voltages.
  17. It's not possible with AIDA64.
  18. The above mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta
  19. The above mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta
  20. I'm not sure if this issue is related to AIDA64 or whether your computer acts up even without AIDA64 running?
  21. HWiNFO may use the direct method that collides with the motherboard BIOS. Asus' own software also digs deeper, but we have no information on what it does exactly and how can it be more accurate than the Asus WMI ACPI interface.
  22. AFAIK you cannot check the exact cause using a software method. You need to change components one by one and check the issue again to see when it gets resolved.
  23. I suppose it could be a specific setting in Windows that disables non-primary monitors when playing a full-screen game.
×
×
  • Create New...