Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11545

  • Joined

  • Last visited

  • Days Won

    489

 Content Type 

Everything posted by Fiery

  1. Fiery
    Perfect.
  2. Fiery
    Try to remove the .txt part from the end of the filename.
  3. Fiery
    No problem, just create the file and put the 3 lines into it that I gave above.
  4. Fiery
    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
  5. Fiery
    What motherboard and CPU do you have? Do you have any RAID arrays defined?
  6. Fiery
    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).
  7. Fiery
    It's normal for powerful mobile PCs.
  8. Fiery
    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
  9. Fiery
    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
  10. Fiery
    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
  11. Fiery
    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.
  12. Fiery
    Fans and pumps from such controllers could disappear when they stop, ie. when their RPM becomes zero. Is there a chance both the fan and pump can stop on your Krakens? Also, please note that AIDA64 supports only one Kraken device, so in your case only the first one it can detect will be supported. I'm not sure if the primary controller is for the CPU or GPU in your system. Please also note that NZXT's own monitoring software (CAM) may also collide with AIDA64 during low-level hardware communication, so it's best to close CAM to verify if the missing fan/pump is due to a collision or due to an AIDA64 bug.
  13. Fiery
    Do you mean you would like AIDA64 to allocate one out of the 15 LCD keys available and use it as an external LCD screen to display sensor info and such? I'm not sure if there's anything more than that possible, like to use multiple keys together or separately by a single software.
  14. Fiery
    Do you have TT's own monitoring software running in the background, along with AIDA64?
  15. Fiery
    Thank you for your help and feedback!
  16. Fiery
    Thank you for your feedback and help.
  17. Fiery
    Thank you! 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. Let me know if it helps.
  18. Fiery
    Yes, thank you. 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. Let me know if it helps.
  19. Fiery
    Feel free to share this topic with anyone. I'm glad you like using AIDA64. I wish we could do more to fix this issue and issues about monitoring Asus AM4 motherboards internally. But with the whole thing riding on how Asus implements the WMI ACPI interface, we need to work with Asus and expect them to deliver the fix soon.
  20. Fiery
    Battery Capacity is shown on the Battery page in our AIDA64 for Android app. In the Windows PC version of AIDA64 you can find the information on the Computer / Power Management page.
  21. Fiery
    Thank you for the photos. I suppose the issue is because of the problem with Asus AM4 motherboards where concurrent access by a 3rd party monitoring tool (like AIDA64) and the motherboard BIOS can cause collisions which could make the fans to act up. In case your motherboard supports Asus WMI ACPI interface, you can try switching to that to avoid the collisions: go to AIDA64 / main menu / File / Preferences / Stability / tick the option called: Asus WMI sensor support and restart AIDA64 to apply the changes. If you cannot see the 2nd line on the Computer / Sensor page to change to "Asus WMI", then your motherboard doesn't support the new Asus monitoring interface and so we cannot fix the problem from our end. BTW, you've got a nice AX206 there
  22. Fiery
    If you have no RAID arrays defined, you can try disabling the two RAID related options in AIDA64 / main menu / File / Preferences / Stability. It accelerates AIDA64 startup and you can also avoid BSoD in certain circumstances.
  23. Fiery
    On Asus AM4 systems it's safer with the Asus WMI sensor support enabled. Without it concurrent access by AIDA64 and the motherboard BIOS can cause collisions that may just end up in fan duty cycles messing up. Please note that even though the new Asus WMI ACPI interface was invented and designed to avoid those collisions that plagued the Asus AM4 platform since the very beginning, the interface is poorly implemented in multiple Asus motherboards. It is also not implemented all across the board. So while it's a great thing in theory, in practice it causes a lot of headaches. All you can do is put more pressure on Asus to fix this issue in a future BIOS update.
  24. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor 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
  25. Fiery
    I don't think Asus' own monitoring tool uses their own ACPI WMI interface simply because it's still not mature. Your case is just one example where it has a glitch. A future BIOS update is the only way to fix this up.
×
×
  • Create New...