Jump to content

Fiery

Administrators
  • Posts

    11546
  • Joined

  • Last visited

  • Days Won

    489

Everything posted by Fiery

  1. Thank you. Please 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 how it works.
  2. It would be a terribly "user-unfriendly" option, since then cca. a hundred fans would appear with zero RPM for all of them
  3. Once it shows up in the BIOS, it should appear in AIDA64 as well.
  4. DIMM slot numbering depends on the actual motherboard. Many motherboards have them mixed up. It's only a minor cosmetic issue that doesn't need a fix.
  5. AIDA64 doesn't support custom characters for external LCD displays.
  6. Thank you for posting this here. I don't think it's related to Corsair Link. But, he can disable Corsair AXi sensor support, Corsair HXi/RMi sensor support, Corsair Link sensor support in AIDA64 / main menu / File / Preferences / Stability, and try running the GPU stress test again.
  7. 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
  8. It isn't compatible, but it's mostly because AFAIK it's not possible to write a generic communication protocol for LCD displays that are connected to a PC USB port via Arduino. However, it should be possible to write an Arduino program (sketch) to emulate an existing LCD protocol to make the Arduino+LCD combo compatible with an existing AIDA64 LCD module.
  9. Your temperatures look normal.
  10. If you want to use the reports for network audit or change tracking purposes, using AIDA64 Business' own modules (Audit Manager and Change Manager), then you don't need to include the Motherboard / ACPI page in your reports in order for the mentioned features to work properly.
  11. Is it possible to somehow stream the bitmap data from a TCP/IP port (of the WiFi layer) into the display? Also, here are 2 projects that may be helpful for you: https://diyprojects.io/esp8266-web-client-sending-data-jeedom-tcp-ip-wireless-json-api/ https://www.dfrobot.com/blog-782.html
  12. Thank you. Strangely, the register that is supposed to hold the W_PUMP+ reading is zero on your system. Can you see the W_PUMP+ reading in the BIOS Setup?
  13. I think you can use VBScript for such purposes. I haven't tried it yet though...
  14. I have no idea where that message comes from No, we don't have a removal tool, since in 99% of the cases it's not necessary to do anything other than using the uninstall tool.
  15. We've ordered a sample of that display, and will implement support for it as soon as it arrives. I'll let you know in this topic when we have a new AIDA64 beta build that you can test on the RoboPeak display.
  16. It means your system no longer has the AIDA64 kernel driver present.
  17. Thank you, but that dump doesn't include EC registers. Please enable status bar in AIDA64 / main menu / View, and on the status bar (which will appear on the bottom of the AIDA64 main window) do a right-click --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.
  18. Samsung SPF devices are not LCD monitors, but digital picture frames. They simply have an additional feature (mini-monitor mode) that puts them ahead of their competitors. But they're still not intended to be used as a regular PC monitor.
  19. AIDA64 uses its own hardware database to report cache buffer size for SSDs. So the value is not detected at all, and may involve inaccuracies if the original database entry was incorrectly inserted. We'll fix it up in the next AIDA64 beta build. Your SSD is fine, don't worry about it. And don't alert Crucial either, since it's not their fault
  20. No things to worry there. Charge counter is reported with good, acceptable or poor accuracy by many devices. If it doesn't align with your expectations, then the value reported is most likely inaccurate or bogus. You can verify whether AIDA64 reports the proper value (as it is provided by the standard Android Battery API), you can compare the values against the ones reported by Ampere or HWMonitor.
  21. I don't think you can automate that
  22. You may want to try the following then, in order to remove the leftover traces of the AIDA64 kernel driver from your system: 1) Start a Command Prompt (CMD.EXE) in Administrator mode 2) Type in: sc delete AIDA64Driver 3) Run Registry Editor (REGEDIT.EXE), and navigate to the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AIDA64Driver 4) Right-click on the AIDA64Driver folder --> Delete 5) In Registry Editor navigate to: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\AIDA64Driver 6) Right-click on the AIDA64Driver folder --> Delete 7) Restart Windows
  23. AIDA64 is able to switch the frame to mini-monitor mode automatically.
  24. AIDA64 manages custom gauges as external files, so you should back them up too.
  25. 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. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
×
×
  • Create New...