Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11545

  • Joined

  • Last visited

  • Days Won

    489

 Content Type 

Everything posted by Fiery

  1. Fiery
    Apparently the issues are caused by the embedded thumbnail data of PNG images. Try to edit the PNG images and remove the thumbnail data.
  2. Fiery
    Thank you, that's very helpful info. We're working on fixing the PNG decoder module of AIDA64 to ignore the thumbnail data.
  3. Fiery
    Thank you for your feedback!
  4. Fiery
    Something's not working as expected about the EC registers readout. Do you think you have any other software running in the background that could interfere with AIDA64 about sensor polling?
  5. Fiery
    Are you using SensorPanel?
  6. Fiery
    The issue is caused by the embedded thumbnail data of PNG files. If you remove that from the PNG file, it works fine with AIDA64. We're working on a bug fix about decoding PNG images in AIDA64.
  7. Fiery

    Image png error

    Fiery replied to FoX's topic in Bug reports

    So far it seems the issue is caused by embedded thumbnail data in PNG files. If you can, please edit the PNG and remove the thumbnail data. Meanwhile, we're working on a bug fix, but it will most likely take longer than a workaround of editing the PNG on your end.
  8. Fiery
    Thank you for your feedback!
  9. Fiery
    Thank you! Please open a separate topic for your SSD issue by letting us know the SSD model. We will try to find out what's happening there...
  10. Fiery
    Thank you for your feedback
  11. Fiery
    I'm afraid it's very difficult to diagnose such issues. Maybe if we could narrow it down a little bit... Please try the following experiment: 1) Disable Low-level SMART operations and the two RAID options in AIDA64 / main menu / File / Preferences / Stability. Restart AIDA64 and check if it throws a BSOD at exit. 2) Disable GPU sensor support in AIDA64 / main menu / File / Preferences / Stability. Restart AIDA64 and check if it throws a BSOD at exit. Let me know how it turns out.
  12. Fiery
    Thank you for your feedback! The indicated readings come from your smart PSU (I suppose it's a Corsair PSU), so they're not related to the motherboard sensor readings.
  13. Fiery
    Thank you. We'll try to find out what's going on. There must be an issue with AMD's own video drivers that causes these headaches.
  14. Fiery
    Thank you, that looks correct so far. Is there a software like Corsair's own iCUE that can report all 3 fans individually for your AIO device?
  15. Fiery
    Please be more specific about what exact sensor readings do you miss from AIDA64.
  16. Fiery
    Awesome
  17. Fiery
    In order to have SMART information and thermal readout for Samsung 980 Pro, make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
  18. Fiery
    That's the utilization of memory. So in your case (based on your screenshot) 4758 MB out of total 6144 MB (= 6 GB) is utilized at the time you made the screenshot. Auto-starting is only initiated by the built-in facility of AIDA64 at Windows startup (AIDA64 / main menu / File / Preferences / General / Load AIDA64 at Windows startup). Any other case is managed by another software. Logitech Gaming Software and Logitech Ghub are known to have a facility to start AIDA64 on their demand, but I'm not sure about MSI Afterburner...
  19. Fiery
    Thank you for your feedback! AIDA64 should measure the same CPU temperature as Asus' own monitoring software. If you have doubts about the CPU temperature reading, just focus on the other ones (CPU Diode, CPU Package). All three of those thermal readings are measured using different methods, so they most likely will never end up showing the same reading.
  20. Fiery
    Please contact the author of Odospace and request a bug fix in their DLL.
  21. Fiery
    Then it must be an issue about AMD Adrenalin video drivers We've already discussed this with AMD, but they seem to have no more ideas on what to do about this matter. A part of AIDA64 sensor code triggers the BSOD in AMD video drivers. We've eliminated direct register access as requested by AMD, but it doesn't seem to be 100% suitable as a fix
  22. Fiery
    We can compile a beta build for you. Please send me your email address and AIDA64 Business product key in private message.
  23. Fiery
    The latter image looks interesting. Can you please expand the Path column to let us see the filename part of the path? It would be useful to see the 5th column expanded on the first image too. The one with values starting with HKCU.
  24. Fiery
    The sensor profiling dump indicates that the whole update process takes less than a second. If you have a low SensorPanel update rate (could be down to 100 millisec) configured in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Update Frequency, then the update rate shouldn't be 2-3 seconds. Currently it's not possible to decouple any part of the sensor update process from the others. We'll need to work on that.
  25. Fiery
    1) Computer / Sensor page can be found in the left page menu of AIDA64. First you need to expand Computer to find the Sensor page. 2) Beta builds are only available as portable ZIP packages. You can download the ZIP file and extract it to the existing installation folder of AIDA64. Let it overwrite any existing files. It will retain your settings as well as your license. 3) It's very odd to be honest. 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. 4) Fan Extension Card is already supported for your motherboard.
×
×
  • Create New...