Jump to content

Fiery

Administrators
  • Posts

    11973
  • Joined

  • Last visited

  • Days Won

    521

Everything posted by Fiery

  1. We've fixed the flickering GPU clock issue on Radeon RX 6800/6900 video cards in 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. Let me know how it works for you.
  2. Please 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. Let me know if it helps.
  3. Thank you for your feedback
  4. Apparently the issues are caused by the embedded thumbnail data of PNG images. Try to edit the PNG images and remove the thumbnail data.
  5. Thank you, that's very helpful info. We're working on fixing the PNG decoder module of AIDA64 to ignore the thumbnail data.
  6. 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?
  7. Are you using SensorPanel?
  8. 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.
  9. Fiery

    Image png error

    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.
  10. Thank you for your feedback!
  11. 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...
  12. 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.
  13. 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.
  14. 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.
  15. 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?
  16. Please be more specific about what exact sensor readings do you miss from AIDA64.
  17. 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. 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. 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. Please contact the author of Odospace and request a bug fix in their DLL.
  21. 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. We can compile a beta build for you. Please send me your email address and AIDA64 Business product key in private message.
×
×
  • Create New...