Jump to content

Fiery

Administrators
  • Posts

    11737
  • Joined

  • Last visited

  • Days Won

    503

Everything posted by Fiery

  1. The above mentioned new AIDA64 beta build is now available for download at: https://www.aida64.com/downloads/latesta64xebeta
  2. @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.
  3. Thank you! Please check the following new beta update of AIDA64: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  4. Thank you! Please check the following new beta update of AIDA64: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  5. I'm glad your issue got resolved. The ROG Ryujin III Extreme display is 640x480 pixels.
  6. 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.
  7. Unfortunately we do not have the necessary technical information to implement the missing sensor readings for your computer
  8. It is most likely caused by a slow USB protocol that is used by your AX206 display.
  9. 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.
  10. 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.
  11. 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.
  12. Yes, you can use that trick, it works
  13. 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.
  14. 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
  15. It's already in the works, and will be rolled out in the next AIDA64 beta update due in a few days from now.
  16. 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
  17. 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.
  18. 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.
  19. Have you tried to push the Reset Position button in AIDA64 / Preferences / Hardware Monitoring / SensorPanel?
  20. Yes, it is possible.
  21. Yes, you need to close the Turzx app to let AIDA64 gain access to the LCD.
×
×
  • Create New...