Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12412

  • Joined

  • Last visited

  • Days Won

    550

 Content Type 

Everything posted by Fiery

  1. Fiery
    Is it because the width of the OSD panel keeps changing? It should change with left alignment too, BTW.
  2. Fiery
    The FPU subtest alone is perfect to drive the power draw and thermal state of the system to the maximum. You should run it for several hours, and then switch to a mixed workload, like CPU+FPU+Cache+RAM+Disks order to verify how the system handles a more mixed scenario.
  3. Fiery
    Here's the fix for the rotation bug: https://www.aida64.com/downloads/latesta64xebeta
  4. Fiery
    The new AIDA64 beta build is available for download at: https://www.aida64.com/downloads/latesta64xebeta
  5. Fiery
    We've implemented a new option called Alignment on the AIDA64 / main menu / File / Preferences / Hardware Monitoring / OSD page. You'll know what to do https://www.aida64.com/downloads/latesta64xebeta
  6. Fiery
    Thank you for the dump. I'm afraid we have no information on noise detection sensors, but we'll try to ask someone at Gigabyte about it. As for the fan labels, we've checked, and they should be labelled properly already. Can you please post a screenshot of the Computer / Sensor page of AIDA64 showing all measured values (incl. temperatures, fan speeds, voltages)
  7. Fiery
    Does it crash if you disable Include debug information in the report in AIDA64 / main menu / File / Preferences / Report?
  8. Fiery
    No need to install it.
  9. Fiery
    Yes, I'm afraid AMD's PMLog API is not 100% stable
  10. Fiery
    I'm not entitled to publish any of the Corsair contact emails I've got. Especially since they're proven to be great folks -- except for this single issue. So I don't want to unleash a s* storm of angry emails flying into their individual mailboxes
  11. Fiery
    Does it work if you make a custom HTML report and exclude the Config / Event Logs page? Maybe that page is very long in your case?
  12. Fiery
    AIDA64 still supports the LCD screen of the Strike7 keyboard.
  13. Fiery
    You don't need an Aquaero device to issue the Aquaero Dump. We'll rename that dump to Aquacomputer Dump to avoid further confusion.
  14. Fiery
    Thank you, we'll add flow rate reading for D5 Next in the next AIDA64 beta update due in a few days from now.
  15. Fiery
    Yes, you need to disable ULPS to enable monitoring both your GPUs. Scan the Registry (using REGEDIT.EXE) for EnableUlps and set all occurences of that to 0 (zero). When you're done, restart Windows to apply the changes.
  16. Fiery
    Ask the great folks at Matrix Orbital about EVE3-39 It should fit your needs. If not, they should be able to provide you with a solution. Worse case anything can be 3D-printed these days
  17. Fiery
    I'm afraid we cannot find a solution
  18. Fiery
    I don't know how those devices can interact with each other. As long as you can have a device that provides the readings via a meaningful way to AIDA64, it will display the measurements. AIDA64 does support Corsair Commander Pro, just keep in mind that iCUE (Corsair's monitoring software) and 3rd party monitoring applications don't play well together due to Corsair's decision on not supporting the industry standard synchronization mutexes that would prevent collisions.
  19. Fiery
    No idea, sorry
  20. Fiery
    I don't think so, since motherboard fan headers are designed to measure the RPM of fans and not the temperature of a fan or something else. Unless of course the thermal diode is designed in a way to let you connect it to a fan header and it provides thermal readings as e.g. 2345 RPM = 23.45 Celsius or so.
  21. Fiery
    Quite frankly, I don't know any IoT users personally, so I cannot gauge the generic approach or requirements of IoT users. And because of that I cannot really allocate developer resources on a complicated project where we haven't yet seen a big demand for MQTT support. You can however come up with your own library, publish it on GitHub or your own website, we can implement support for it in AIDA64 (as well as linking to your website), and it could drive more exposure to your page/website as well as satisfy those IoT users who're hungry for a MQTT sensor solution.
  22. Fiery
    We try to avoid writing dynamic data periodically into files, since many computers these days are equipped with a SSD drive. Wearing it down by writing a file constantly (like once or twice a second) is a bad idea. You can however use any of the existing 3 methods that AIDA64 offers to export the sensor readings for post-processing by a library or another software. Just check AIDA64 / main menu / File / Preferences / Hardware Monitoring / External Applications. Out of the 3 options there we recommend going for Shared Memory, since it's the most efficient way.
  23. Fiery
    AIDA64 uses the standard Asus WMI ACPI interface that has a known issue in a few BIOS versions on AM4 motherboards. You need to wait for Asus to fix this bug in the BIOS of your motherboard.
  24. Fiery
    I'm afraid we have no information on the register index of the flow rate reading on D5 Next. In other words, we don't know how to measure that value right now. If you can help us a bit about that, we _may_ be able to figure it out though, so it's not a lost cause Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Aquaero 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, check what Aquasuite reports as flow rate for your D5 Next device. The value should fluctuate a bit, in which case please let us know a few examples of readings. We'll do our best to try and find the reading among the D5 Next registers that are shown in the Aquaero Dump. Thanks, Fiery
  25. Fiery
    AMD processors have no per-core thermal diodes, so it's normal.
×
×
  • Create New...