Jump to content

Fiery

Administrators
  • Posts

    12414
  • Joined

  • Last visited

  • Days Won

    550

Everything posted by Fiery

  1. I think this is already solved, but I provide the info on how to get around it before locking this topic. AIDA64 v6.10 implements an option in main menu / File / Preferences / Stability to let you disable Thermaltake Riing Plus and Pure Plus sensor support in case you experience issues about it.
  2. Please note that you can rename the fan labels on the Computer / Sensor page if you do a left-click on the labels. Thank you for the dump. It seems to be a bit complicated, especially since as I assume, that device cannot be purchased separately -- or can be?
  3. Don't worry, we will handle the mentioned issues (DIMM thermal readings and Ryujin 360 support) in their individual topics here on this forum.
  4. In case you use a different DPI zoom setting for your monitor than where the original SensorPanel layout was created, you need to re-adjust the gauge sizes and position of the LCD items as well.
  5. If you can see sensor type listed as "ITE IT8665E (MMIO F7000000h)" no matter how you have the option Asus WMI sensor support set, it means your motherboard doesn't support the Asus WMI ACPI interface. Please note that without that interface collisions between the motherboard BIOS and AIDA64 will occur, and it can cause minor (or sometimes even major) issues.
  6. Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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. BTW, do you have NZXT CAM running in the background? Thanks, Fiery
  7. Thank you for posting their response. Sadly in the past 10 or so years many hardware manufacturers just piled on existing technologies to unlock new sensor readings and new tricks (like putting RGB LEDs onto and into everything), without ever re-thinking the way sensor monitoring and interacting with hardware should work in the 21st century. With Ice Lake and Tiger Lake desktop platforms things will hopefully change though, so fingers crossed for Asus and others to come up with a more modern solution that causes less headaches not only to them but to all of us, including hardware owners, enthusiasts and software engineers as well.
  8. If it works sometimes, then I'd suspect AIDA64 collides with another monitoring tool like NZXT CAM. Do you experience the unstable Kraken readings even when you close NZXT CAM?
  9. Thank you! Is there a software -- made by either Asus or a 3rd party -- that can show you the readings for your Ryujin 360 that you're looking for?
  10. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). 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. Thanks, Fiery
  11. Unless we would use tricks that require rooting, I don't think it's possible
  12. Your motherboard doesn't provide a single CPU thermal reading, but instead it provides 2 readings: CPU Diode and CPU Socket.
  13. The issues about OS identification is always due to the fact that the AIDA64 version that you're using is outdated. Make sure to download the trial version of AIDA64 v6.10 (that's the latest one right now) and check it out thoroughly. Use up all the 30 days of the trial (evaluation) period and only purchase a license if you're satisfied with how it works and what information it provides.
  14. Try to remove the .txt part from the end of the filename.
  15. No problem, just create the file and put the 3 lines into it that I gave above.
  16. Try to go to AIDA64 installation folder, and find the settings file called AIDA64.INI. If you have the file there, try to edit it using Notepad, and replace the following lines: LowLevelRAIDEnum=1 LowLevelRAIDSMART=1 ... with the followings: LowLevelRAIDEnum=0 LowLevelRAIDSMART=0 If you don't have the file there yet, create it, and enter the following lines into the new text file: [Generic] LowLevelRAIDEnum=0 LowLevelRAIDSMART=0
  17. What motherboard and CPU do you have? Do you have any RAID arrays defined?
  18. Measuring CPU utilization (CPU load) is a tricky issue, since the CPU load (as measured) of modern CPUs are affected by the measurement of the CPU load itself So it's quite normal that you experience a different load if you look at different software. With AIDA64 the CPU load is affected by the tons of measurements that AIDA64 does in each cycle to collect all the sensor measurements and system measurements (like CPU clock, GPU clock, etc).
  19. It's normal for powerful mobile PCs.
  20. Please try to enable the option called DIMM thermal sensor support on the page AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it helps. I've moved your topic under Bug Reports
  21. Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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. I've moved the topic under Bug Reports Thanks, Fiery
  22. Yes, System #n is called Chassis #n in AIDA64, that should be the difference but it's normal. As for the Gigabyte RGB Fan Commander, please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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. Thanks, Fiery
  23. AIDA64 v6.10 implements an option in main menu / File / Preferences / Stability to let you disable Thermaltake Riing Plus and Pure Plus sensor support in case you experience issues about it.
×
×
  • Create New...