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
    Logitech Gaming Software and Ghub are known to be behind such anomalies
  2. Fiery
    Do you experience the issue with Odospace disabled, and SensorPanel or OSD Panel enabled?
  3. Fiery
    As I've requested above, please post an Embedded Controller Dump.
  4. Fiery
    Yes, there is. You basically need as many licenses (nodes/seats) for AIDA64 Business as many licenses you'd wish to use at any given client's. So if you have 3 clients: a small client with a network of 50 computers, a mid-size client with 500 computers and a large client with 5000 computers, you need an AIDA64 Business license with 5000 nodes or the size of your largest client's network basically. If you're looking for a more affordable solution, please contact our distributor ABSEIRA at: https://www.aida64.co.uk/contact They will be able to propose alternative ways of making the envisioned project possible.
  5. Fiery
    It's not possible for the SensorPanel, but you can have that data either logged into a HTML or CSV log file (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging), or track it using the Statistics tab of the AIDA64 System Stability Test (AIDA64 / main menu / Tools / System Stability Test).
  6. Fiery
    Thank you for your help! The fix will be added to the next AIDA64 beta update. As it turns out, a similar bug plagued the Elgato and EVGA LCD modules as well, so we've fixed all three at once
  7. Fiery
    Thank you! In order to accelerate fixing this bug, I've sent you an email about this.
  8. Fiery
    We'll try to replicate the same environment where you experience this issue. Do you have RTSS installed as part of Afterburner, or did you use a RTSS standalone installer? Do you experience the issue with other 3D games as well? Or the issue only comes up with Minecraft?
  9. Fiery
    Try to toggle the option AIDA64 / main menu / File / Preferences / Stability / Asus WMI sensor support.
  10. Fiery
    It's in AIDA64 / main menu / File / Preferences / General / Load AIDA64 at Windows startup.
  11. Fiery
    Thank you, we'll fix the issue in the next AIDA64 beta update due next week. I will post a message into this topic once the new beta becomes available for download.
  12. Fiery
    Thank you, we'll fix the issue in the next AIDA64 beta update due next week. I will post a message into this topic once the new beta becomes available for download.
  13. Fiery
    Thank you for your feedback
  14. Fiery
    I'm afraid that's not that useful since it refers to a module (PSHED.DLL) that is not used by AIDA64 at all. I have no idea how that module can be related to this issue or AIDA64.
  15. Fiery
    It's not supported by AIDA64 yet. In order to let us have a better understanding on the USB layer of it, 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. Thanks, Fiery
  16. Fiery
    The issue is about loading certain PNG images when the PNG decoder module of AIDA64 goes crazy and starts leaking memory We've added a new PNG decoder module, but it seems it fails to work in some cases too. Our best guess is that there's a certain property of the PNG images you use and that by converting the images or exporting them using a different image editor could help -- but so far we haven't found a single reason that could be blamed for the PNG module to go south. Check the following post for a potential workaround, although it requires you to convert your images using Gimp:
  17. Fiery
    Are you sure the GPU is not activated when you start a 3D game? What AIDA64 notified about was simply a Registry setting that needs to be altered to put a constant stress on the GPU using OpenCL. It will not alter any hardware settings or remove any hardware.
  18. Fiery
    Try to install the standalone RTSS. We've heard one instance when that helped.
  19. Fiery
    I'm not sure about that. Predicting that something will go wrong in the future is quite a difficult business
  20. Fiery
    I've replied you in your other topic. This topic closed.
  21. Fiery
    Make sure to enable (check) the option called DIMM thermal sensor support in AIDA64 / main menu / File / Preferences / Stability. Restart AIDA64 to apply the changes.
  22. Fiery
    It depends on what modules of AIDA64 do you have activated. A constant monitoring of a whole bunch of sensors, rendering SensorPanel or LCD layouts indeed will put additional tasks to the processor which will make it work at higher temperatures.
  23. Fiery
    You can download AIDA64 using Armoury Crate: https://rog.asus.com/us/innovation/armoury_crate/
  24. Fiery
    Thank you for your feedback and help!
  25. Fiery
    I'm afraid the Capellix is a hard nut to crack. We've tried a number of ways to try and communicate with the device, but so far we haven't found a way to interrogate it in a way to make it return the fans+pump RPM as well as the thermal reading. We'll keep researching it, but at this time I cannot promise any timeline about this issue
×
×
  • Create New...