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 afraid AIDA64 doesn't support such sensor source.
  2. Fiery
    You need to perform the upgrade this way: close AIDA64, download the new beta ZIP package, and extract the ZIP contents into the existing installation folder of AIDA64. Let it overwrite any existing files. It will retain your Preferences settings and your license as well.
  3. Fiery
    They look normal to me.
  4. Fiery
    We've done several test runs and tried to fix it from our end, but it seems LGS and Arx sometimes simply act up and stop working through the Logitech Arx SDK that AIDA64 relies on What we've found out is that the only way to fix it is to start AIDA64, and when it fails to work with Arx, restart LGS. That seems to be an annoying but working fix.
  5. Fiery
    Thank you! Maybe what HWiNFO64 measures is the CPU VID instead of the Vcore? In AIDA64 you can see both readings right next to each other.
  6. Fiery
    Thank you for your feedback! About the ext.fan, please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller 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
  7. Fiery
    Thank you, it's always great to bump into and work together with other developers
  8. Fiery
    In the next AIDA64 beta we will add the drive serial numbers to the Physical Drives page in order to help you out about this issue. I will post a message into this topic once the new beta build becomes available for download.
  9. Fiery
    Please give us a few weeks to complete that task though, since even acquiring the device will take at least a week due to low supplies/stock at local dealers on such specific products.
  10. Fiery
    Driver details and hardware ID look correct. Maybe it's because the manufacturer of your device updated the USBD480 firmware to one that's incompatible with the old firmware that we designed our USBD480 support around. Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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. If it's possible, please also post a screenshot of the AIDA64 / main menu / File / Prerefences / Hardware Monitoring / LCD / LCDInfo page. Thanks, Fiery
  11. Fiery
    The FPU subtest puts the most demanding task on the processor which could make it hit TDP, TDC or other power limits or simply overheat, and that will effectively disable automatic overclocking, or prevent any kind of overclocking without potentially damaging the CPU. In other words, in your particular case what happens is that 4.6GHz is only possible with 90-95% of the tasks (workloads), but the most demanding few of such tasks will only enable a lower CPU clock frequency to be used.
  12. Fiery
    I agree When you got your new PSU and you find a software (which could be the manufacturer's own software too) that can monitor it via USB -- but without AIDA64 supporting it -- please let us know, and we'll try to push our luck to implement support for it.
  13. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug -->SMART 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 --> Sensor Debug -->RAID Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  14. Fiery
    What CPU do you have?
  15. Fiery
    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
  16. Fiery
    We'll order a SMT Series PSU in order to help us work on implementing the Modbus protocol in AIDA64. I'll let you know about our progress in this topic.
  17. Fiery
    I think the missing readings come from a Corsair liquid cooler integrated into your computer. Please let us know what model number is your Corsair One PC. Also, please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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.
  18. Fiery
    Thank you! Are you sure you're running the latest beta build I've linked above?
  19. Fiery
    https://www.aida64.com/compare-aida64-features You can download the latest beta build of AIDA64 Engineer from: https://www.aida64.com/downloads/latesta64eebeta
  20. Fiery
    Octo should be fully supported already. I've sent you a private message about High Flow NEXT.
  21. Fiery
    Thank you! I'm afraid the device is out of stock, so it'll be more difficult to implement support for it. I've sent you a private message about this.
  22. Fiery
    That's very strange. Can you please post a screenshot of the Computer / Sensor page of AIDA64?
  23. Fiery
    Specifically what Corsair gear can Modbros monitor while the iCUE software is also running? I'm just asking because there are Corsair devices that can be monitored by AIDA64 while iCUE is running, and then there are other Corsair hardware that cannot provide such flexibility.
  24. Fiery
    I suppose most of those readings are available in AIDA64 too, but maybe with a different label/caption. What motherboard and CPU do you have? Can you please post a screenshot that shows the sensor readings in AIDA64 Computer / Sensor page, and also shows the HWiNFO64 readings (like what you've shown on that screenshot that you've posted) side-by-side?
  25. Fiery
    You need to manually adjust the layout to make sure it looks great with your higher resolution screen/panel.
×
×
  • Create New...