Jump to content

Fiery

Administrators
  • Posts

    12283
  • Joined

  • Last visited

  • Days Won

    541

Everything posted by Fiery

  1. We've figured out the protocol using proprietary tools.
  2. That particular motherboard has a very bad sensor implementation that is very difficult to handle. And with that it's quite easy to have the sensor access collide between AIDA64 and the BIOS We haven't found a perfect solution for the issue that would work with all BIOS versions of your motherboard. But, you may want to try enabling Asus WMI sensor support in AIDA64 / main menu / File / Preferences / Stability and restart AIDA64 to apply the changes in case you have your motherboard updated to the latest BIOS. If that layer (Asus WMI ACPI sensors) works correctly with your motherboard, then collisions along with pump stopping or fan stopping issues wouldn't occur.
  3. Thank you! Just to narrow it down a bit, please uncheck (disable) GPU sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Please let me know if the issue persists that way.
  4. Do you have Valorant Vanguard installed?
  5. Using beta build 5444, 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
  6. There's a sensor item called Time (HH:MM) that you may find useful
  7. Do you have an Asus motherboard? If yes, which one?
  8. "CPU" power is provided by the sensor chip of certain Asus motherboards. It could be a challenge to puzzle it together what that value actually means We just show it because it is definitely a meaningful value and related to the CPU, but its accuracy has to be researched and evaluated by the user.
  9. Thank you! Are you still running Firmware v1.04 on the device? I'm just asking because we've tested NZXT GRID+ V3 with Firmware v1.04 and it works fine for us.
  10. We'll fix it in the next AIDA64 beta update.
  11. The default setting is Celsius.
  12. We've tested the Samsung SPF module of AIDA64 using our SPF-75H test device, under Windows 10 64-bit Version 1909, with the libusb driver that we supply, and it works flawlessly.
  13. I'm sorry, but we currently have no plans to develop for Nest Hub.
  14. In many cases such issues happen because of memory module compatibility issues with the motherboard or the BIOS... In which case updating the motherboard to the latest BIOS may help. Another cause may be that you use an excessive memory clock setting or too agressive memory timings, incorrect memory voltage setting, etc, so basically the memory is incorrectly configured in the BIOS Setup (a.k.a. UEFI Setup).
  15. Our recommendation is at least a few hours with the FPU subtest enabled alone, and then a further few hours with all subtests of the AIDA64 System Stability Test enabled.
  16. Please let us know more about your system configuration. Motherboard model, CPU type, video card(s) model, any external drives (SSD or HDD) connected? Are you running 64-bit Windows 10 with the latest updates and patches applied?
  17. That reading was carried over from the (now old) Rampage VI Extreme where it was labelled as CPU PLLs OC in the UEFI Setup.
  18. That one doesn't need special support, since it acts like a monitor under WIndows, so you can extend the Windows Desktop to it. In which case you can use the AIDA64 SensorPanel to place your layout on the LCD.
  19. If you want to import the sensor readings from AIDA64 into Aquasuite, then please refer to Aquasuite's user's manual, because it's not our software and so we cannot provide you proper and accurate guidelines on how to use it.
  20. Thank you for your feedback!
  21. The above mentioned new AIDA64 beta update is now available for download at: https://www.aida64.com/downloads/latesta64xebeta
  22. The mentioned new AIDA64 beta update is now available for download at: https://www.aida64.com/downloads/latesta64xebeta
  23. 2) We do not have plans to show a scope or other visual representation of the audio that's playing. In fact, the SensorPanel and external LCD module of AIDA64 do not support video or animations, so showing such visual effect is not possible anyway, regardless of what it's showing.
  24. You're right, we need to work on FCLK.
  25. Indeed there's a bug about detecting RRD, RRD_L and RRD_S timings on AMD K17.x IMC. We will fix that in the next AIDA64 beta update. I'll post a message into this topic once the new beta build is available for download. BTW, it's so strange that noone else noticed this issue before. Thank you for pinging us about it!
×
×
  • Create New...