Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11334

  • Joined

  • Last visited

  • Days Won

    476

 Content Type 

Everything posted by Fiery

  1. Fiery
    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.
  2. 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
  3. Fiery
    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.
  4. Fiery
    Your temperatures look normal.
  5. Fiery
    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.
  6. Fiery
    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
  7. Fiery
    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?
  8. Fiery
    I think you can use VBScript for such purposes. I haven't tried it yet though...
  9. Fiery
    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.
  10. Fiery
    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.
  11. Fiery
    It means your system no longer has the AIDA64 kernel driver present.
  12. Fiery
    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.
  13. Fiery
    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.
  14. Fiery
    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
  15. Fiery
    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.
  16. Fiery
    I don't think you can automate that
  17. Fiery
    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
  18. Fiery
    AIDA64 is able to switch the frame to mini-monitor mode automatically.
  19. Fiery
    AIDA64 manages custom gauges as external files, so you should back them up too.
  20. 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. 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
  21. Fiery
    AIDA64 currently only supports reading strings and DWORD values from the Registry, and put them on external displays (or SensorPanel, OSD Panel, etc). You need to find a way to write the Registry values into the following path: HKEY_CURRENT_USER\Software\FinalWire\AIDA64\ImportValues And name them as: Str1 Str2 ... Str10 for string values, or: DW1 DW2 ... DW10 for DWORD values. As you keep updating those values in the Registry, the values get updated on your external display.
  22. Fiery
    Thank you for your feedback. Please submit a report from the About page, and we will fix the reported issue in the next AIDA64 app update of v1.55.
  23. Fiery
    Probably you have started AIDA64 once in the past, and its kernel driver got cached by the Windows kernel. If you want to make sure you have all files related to AIDA64 removed from your system, then scan your system for the following files: AIDA64.* KERNELD.X32 KERNELD.X64 And if you find any of those files on your system, make sure to remove them all.
  24. Fiery
    Thank you for your feedback. When the liquid temperature reading becomes unstable, do the other readings (fan RPM, pump RPM) also become unstable? Or it's only the liquid temperature that has that issue?
  25. Fiery
    Those are generic temperature readings that we cannot properly label due to lack of information for the motherboard in question. Do you have temperature readings in your BIOS Setup? If yes, then you may be able to figure out the proper labels for the thermal readings. In which case we can adjust the readings to make the temperature readouts more meaningful.
×
×
  • Create New...