Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11334

  • Joined

  • Last visited

  • Days Won

    476

 Content Type 

Everything posted by Fiery

  1. Fiery
    I'm not sure what your customers would do with the attached TXT file. Would they save it to somewhere on their phone? If yes, then finding it afterwards could raise the same difficulties than when the report is saved to file directly from AIDA64 IMHO. Can't they simply email the report directly to you? Or forward it from e.g. Gmail when they receive the email that they sent to themselves? BTW, am I right in assuming that the OS of choice there is Android? I'm just asking because we have multiple mobile apps covering all mobile platforms available out there.
  2. Fiery
    Thank you for your feedback!
  3. Fiery
    That would be great as a test. Thank you in advance! Meanwhile, we've ordered an EK-Loop Connect device in order to help us do more research. I'm not sure however if it's gonna be V1 or V2 of the device. Do you know how to recognize device version, and what the differences are between the two versions?
  4. Fiery
    Yes, on your motherboard all 3 temperature readings (Motherboard, CPU, Aux) should reflect a correct measurement.
  5. Fiery
    What version of AIDA64 are you using? And what chipset and CPU do you have in your notebook?
  6. Fiery
    It's a complex thing to monitor and report, but we'll do our best in the remaining part of the year to make it happen.
  7. Fiery
    Thank you! We'll fix the reporting of VCCIO voltage on Asus ROG Maximus XII Series motherboards in the next AIDA64 beta update.
  8. Fiery
    It's not AIDA64, but Winsock.
  9. Fiery
    I understand that it can be difficult to handle NICs these days, but the whole reason behind that is that Windows 10 itself manages NICs that way. They can appear and disappear, their order can change dynamically, virtual NICs here and there, etc. etc. With such a dynamic scenario anything you configure as a fixed setting can change on-the-fly. I'm not sure how could AIDA64 follow that automatically...
  10. Fiery
    It could be a collision between the polling activity done by AMD's video drivers and AIDA64. It's very difficult to handle that issue without proper help from the driver itself. Later AMD video cards (based on Vega and Navi) has a special video driver call that can be used to avoid such issues. With older video cards it's still a hit & miss, and it's difficult to find a proper way to avoid the problems. Other than giving up on GPU monitoring (AIDA64 / main menu / File / Preferences / Stability / GPU sensor support)
  11. Fiery

    Image png error

    Fiery replied to FoX's topic in Bug reports

    Thank you for your feedback!
  12. Fiery
    We've figured out the protocol using proprietary tools.
  13. Fiery
    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.
  14. Fiery
    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.
  15. Fiery
    Do you have Valorant Vanguard installed?
  16. Fiery
    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
  17. Fiery
    There's a sensor item called Time (HH:MM) that you may find useful
  18. Fiery
    Do you have an Asus motherboard? If yes, which one?
  19. Fiery
    "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.
  20. Fiery
    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.
  21. Fiery
    We'll fix it in the next AIDA64 beta update.
  22. Fiery
    The default setting is Celsius.
  23. Fiery
    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.
  24. Fiery
    I'm sorry, but we currently have no plans to develop for Nest Hub.
  25. Fiery
    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).
×
×
  • Create New...