Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12573

  • Joined

  • Last visited

  • Days Won

    563

 Content Type 

Everything posted by Fiery

  1. Fiery
    AIDA64 doesn't support average clock measurement. You can see average values in AIDA64 System Stability Test / Statistics.
  2. Fiery
    Make sure to use the latest AIDA64 beta build available at: https://www.aida64.com/downloads/latesta64xebeta Start with adjusting your SensorPanel on your main monitor. Set the SensorPanel resolution to 1400x840 in AIDA64 / Preferences / Hardware Monitoring / SensorPanel, and then pin it to your secondary screen on the same page of the AIDA64 Preferences. Once the SensorPanel properly occupies and fills your secondary monitor, you can keep on designing the layout the way you want.
  3. Fiery
    Those commands do not turn the screen on or off, but rather turn the brightness up and down.
  4. Fiery
    There's no sampling time. Each entry represents one chunk of data read or written to the drive.
  5. Fiery
    Yes, we've found your record in our customer database. Your license is still valid for AIDA64 v8.25. We've resent your license emails.
  6. Fiery
    We're looking into it, thank you!
  7. Fiery
    What motherboard and CPU do you have?
  8. Fiery
    Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know if it helps.
  9. Fiery
    Are the other GPU related measurements shown properly, so it's only the GPU power reading that is acting out?
  10. Fiery
    Thank you! We will fix the issue in the next AIDA64 beta update.
  11. Fiery
    In AIDA64 please press Ctrl+D --> Video Debug --> ATI GPU Registers. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  12. Fiery
    Yeah, we've heard about that issue, but sadly so far we haven't found a method to make such devices to transition into mini-monitor mode properly 😞
  13. Fiery
    Clashing shouldn't be an issue. Did you do anything to your WireView device between the two attempts? Maybe updating its firmware?
  14. Fiery
    After the device is transitioned into mini monitor mode, please create a USB Dump and send it to us. In AIDA64 please press Ctrl+D --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  15. Fiery
    You need to take the file called libusb0-amd64.dll from the 2021 folder of the ZIP you've downloaded, rename the file to libusb0.dll and copy that file to the AIDA64 installation folder. That should let you have the Samsung LCDs back in the Preferences of AIDA64.
  16. Fiery
    Make sure to have the following 2 options both enabled (checked) in AIDA64 Preferences: - Stability / Low-level SMART operations - Hardware Monitoring / Enable disk temperature measurement
  17. Fiery
    Thank you, we've fixed it up.
  18. Fiery
    No, those are simply bogus (invalid) readings that you can simply ignore.
  19. Fiery
    Not yet 😞
  20. Fiery
    I'm not sure if you have Thermal Grizzly's own software running. That software may collide with AIDA64, so try to close it and check it again.
  21. Fiery
    Have you tried it with the latest AIDA64 beta update? https://www.aida64.com/downloads/latesta64xebeta
  22. Fiery
    They should be there as Temperature #1 and Temperature #2 in your case.
  23. Fiery
    It means you will need to wait for Asus to fix the issue on their end too. They're a bit slower than us though.
  24. Fiery
    Please avoid opening multiple topics for a single issue. I've replied in your other topic. This topic is closed.
  25. Fiery
    In order to narrow this down, first please disable GPU monitoring in AIDA64 / Preferences / Stability / GPU sensor support, and let us know if it makes a difference. Make sure to restart AIDA64 after altering that option.
×
×
  • Create New...