Jump to content

Fiery

Administrators
  • Posts

    12161
  • Joined

  • Last visited

  • Days Won

    535

Everything posted by Fiery

  1. Thank you for your feedback!
  2. Those only apply to certain (mostly Asus) motherboards. Just ignore them, and we'll make sure to remove them from the list in the next AIDA64 beta update.
  3. Thank you for your feedback!
  4. Does the board have the necessary input power supplied?
  5. Snapdragon SoC's tend to provide a whole bunch of thermal readings, and they're not always something you want to use. You can simply ignore the readings that you deem invalid.
  6. I mean if you go to Device Manager, find the device for your Z63, right-click --> Properties --> Driver tab --> Update Driver --> Browse my computer for driver software --> you can update the driver there for a HID-compliant driver. However, due to normal circumstances that wouldn't be necessary at all. We'll check our Z63 again on a clean system, because it's rather strange what's happening on your system.
  7. Please check if the system restarts with the System Stability Test, if you only have the FPU subtest enabled there.
  8. Please avoid posting a single issue into multiple topics. I've replied in your other topic. This topic closed.
  9. If you cannot create a file in AIDA64 installation folder, then copy the whole folder to e.g. your Windows Desktop and create the file into that new folder.
  10. The above mentioned new beta build of AIDA64 Extreme is now 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 how it works.
  11. We've fixed the issue 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 how it works.
  12. We've fixed the GPU flickering issue as well as implemented support for EVGA iCX3 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 how it works.
  13. Thank you! 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 how it works.
  14. Thank you! Both of you, 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 how it works.
  15. Thank you for your feedback!
  16. AIDA64 v6.25 should work fine. We've tested it with an iPhone and it works properly (for us). Do you have your device connected properly and shown in the list of devices on the Arx Control tab of the Logitech Gaming Software Settings?
  17. Thank you! Temperature #1 and Temperature #2 should be the readings that your motherboard labels as T_Sensor1 and T_Sensor2.
  18. We have no technical information on how to use those USB ports for communications. Do you have some useful materials from Element14 about that?
  19. I'm afraid AIDA64 is not suitable for that task. You may want to check out the following tools, one of them may be suitable: https://www.raymond.cc/blog/schedule-windows-vista-shutdown-with-vista-shutdown-timer/
  20. It's quite difficult to diagnose such issues, but let's give this a go: 1) Please go to AIDA64 installation folder and create a new file (e.g. text file) called ENABLE_HWMONINIT_LOG.TXT. You don't need to put anything into the file itself. 2) Start AIDA64, and go to the Computer / Sensor page 3) Wait for 30 seconds, and then close AIDA64 (or close it using the Task Manager if you have to) 4) Check out your Windows Desktop where a new file called LowLevelLog.txt should have been created. Send us the file either by copy-pasting into this topic, or by attaching the file to a post. 5) After you've done with that test, make sure to remove the file ENABLE_HWMONINIT_LOG.TXT from the AIDA64 folder to disable its special debug logging facility. Thank you in advance!
  21. What we've found out recently is that indeed when AIDA64 SensorPanel is running on a secondary display and the primary display resolution changes, the SensorPanel position will change since it's tied to a relative position counting from the top-left corner of the primary display. One workaround for such issues we've found is to move the secondary display (in your case it's the tertiary display I guess) to the left of the primary display in the multi-monitor configuration panel of the WIndows 10 Settings. So when the small display is on the left and the large (primary) display is on the right, the position of the SensorPanel will be retained even when the primary display resolution changes.
  22. What we've found out recently is that indeed when AIDA64 SensorPanel is running on a secondary display and the primary display resolution changes, the SensorPanel position will change since it's tied to a relative position counting from the top-left corner of the primary display. One workaround for such issues we've found is to move the secondary display to the left of the primary display in the multi-monitor configuration panel of the WIndows 10 Settings. So when the small (secondary) display is on the left and the large (primary) display is on the right, the position of the SensorPanel will be retained even when the primary display resolution changes.
  23. It's not possible right now. I'm curious: what part of your layout would you like to rotate? And how many degrees of angle?
  24. We don't provide such services, but maybe someone else reading this would be willing to help you out.
  25. Try to run the AIDA64 System Stability Test again, but only have the FPU subtest enabled. That will put the most thermal stress on your CPU. Watch the bottom graph for any throttling activity. My assumption is that the frequency drops occur because your CPU is overheating and it throttles back to protect itself from permanent damage due to excessive thermal state.
×
×
  • Create New...