Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11964

  • Joined

  • Last visited

  • Days Won

    520

 Content Type 

Everything posted by Fiery

  1. Fiery

    Battery

    Fiery replied to 123c123's topic in Android Forum

    Thank you for your feedback. Please note that on many devices the standard Android Battery API is inadequately implemented, and fails to provide proper charge counter information for the battery. If you want, you can hide the incorrect charge counter information from the Battery page by unchecking the charge counter option in the AIDA64 Settings.
  2. Fiery
    Thank you for your feedback!
  3. Fiery
    Try to set tCR (Command Rate) to 2T, and also disable Turbo Boost. Check if it helps to stabilize your system. We've seen an AM5 motherboard that failed with Turbo Boost enabled and had to be RMA'd.
  4. Fiery
    Thank you for your feedback!
  5. Fiery
    The above mentioned new AIDA64 beta build is now available for download at: https://www.aida64.com/downloads/latesta64xebeta
  6. Fiery
    @VintageOffice We've added a new hot key entry to open the SensorPanel Manager. You can find it in AIDA64 / Preferences / Hardware Monitoring / Hot Keys. Please check the following new beta update of AIDA64: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  7. Fiery
    Thank you! Please check the following new beta update of AIDA64: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  8. Fiery
    Thank you! Please check the following new beta update of AIDA64: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  9. Fiery
    I'm glad your issue got resolved. The ROG Ryujin III Extreme display is 640x480 pixels.
  10. Fiery
    We've checked it with our own 265K based test system, and the core temperatures are a lot closer to the other CPU temperature measurements. If you can see the same anomaly in other monitoring software (like HWMonitor, HWiNFO), then it could well be a hardware issue.
  11. Fiery
    Unfortunately we do not have the necessary technical information to implement the missing sensor readings for your computer
  12. Fiery
    It is most likely caused by a slow USB protocol that is used by your AX206 display.
  13. Fiery
    Yes.
  14. Fiery
    1) About hotspot temperature, please check the following article: https://videocardz.com/pixel/nvidia-has-removed-hot-spot-sensor-data-from-geforce-rtx-50-gpus 2) About GPU stress testing and GPGPU benchmarks, the issue is actually because of the faulty OpenCL drivers that the current ForceWare drivers include for RTX 5000 Series. Hopefully nVIDIA will soon fix that up.
  15. Fiery
    Thank you! That issue is actually because of the faulty OpenCL drivers that the current ForceWare drivers include for RTX 5000 Series. Hopefully nVIDIA will soon fix that up.
  16. Fiery
    Thank you for letting us know about the resolution.
  17. Fiery
    Have you tried to do a complete power-off of your computer as I advised above?
  18. Fiery
    Based on that dump, the USB device for your Ryujin III Extreme display looks fine. That doesn't mean much though, since it doesn't mean the device is fully operational.
  19. Fiery
    Yes, you can use that trick, it works
  20. Fiery
    The SMBus on your motherboard seems to have gone haywire Please try to do a system power down (shut down Windows, remove power from your PSU), start Windows, and check if it works then.
  21. Fiery
    Thank you! Something's going south about detecting your memory modules. In AIDA64 please press Ctrl+D --> Sensor Debug --> SMBus Dump (Full). Attach the results as a TXT file to your post. Thanks, Fiery
  22. Fiery
    It's already in the works, and will be rolled out in the next AIDA64 beta update due in a few days from now.
  23. Fiery
    1) In AIDA64 please press Ctrl+D --> Disk Debug --> Disk Controllers Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. 2) In AIDA64 please press Ctrl+D --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. 3) In AIDA64 please press Ctrl+D --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  24. Fiery
    Please navigate to the AIDA64 installation folder, and create a new text file there called ENABLE_HWMONINIT_LOG.TXT Then start AIDA64, go to the Computer / Sensor page. Wait 20 seconds, and then check if you can find a new file named LowLevelLog.txt on your Windows Desktop. Please send us the file so we can see where the sensor scanning gets stuck on your computer.
  25. Fiery
    Does the Computer / Sensor page of AIDA64 work properly? In case it also fails to load, then please let us know more about your computer, e.g. motherboard model, CPU type, video card model.
×
×
  • Create New...