Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12008

  • Joined

  • Last visited

  • Days Won

    525

 Content Type 

Everything posted by Fiery

  1. 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.
  2. 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.
  3. Fiery
    It means your system no longer has the AIDA64 kernel driver present.
  4. 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.
  5. 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.
  6. 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
  7. 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.
  8. Fiery
    I don't think you can automate that
  9. 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
  10. Fiery
    AIDA64 is able to switch the frame to mini-monitor mode automatically.
  11. Fiery
    AIDA64 manages custom gauges as external files, so you should back them up too.
  12. 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
  13. 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.
  14. 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.
  15. 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.
  16. 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?
  17. 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.
  18. Fiery
    That one looks incredible Great job!
  19. Fiery
    Thank you! Voltages still do not look correct though. If you would be so kind to help us fix them, then 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
  20. Fiery
    Start the AIDA64 stress test (AIDA64 / main menu / Tools / System Stability Test), make sure to have only the FPU subtest enabled, press Start, and leave it running for a few hours. In case your computer keeps working properly with such demanding task, the PSU as well as other components work fine.
  21. Fiery
    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.
  22. Fiery
    Thank you. Please check the latest AIDA64 beta: 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.
  23. Fiery
    Thank you. I think the issue is that you don't have the necessary SiUSBXp.dll library installed on your system, or AIDA64 is unable to locate it. Can you please try to find that file on your system, and let us know the full path name for the file?
  24. Fiery
    Edge is fully supported. We've just checked under Win10 1809 using AIDA64 latest version, and it performs the auto-polling just fine in IE, Edge, Firefox, Safari and Chrome as well.
  25. Fiery
    I don't know much about the LED. You may want to ask around in MSI motherboard related forums about that. I would make sure to have the latest BIOS and latest Windows 10 updates installed, and use the system with factory settings. With those settings everything should work fine. Don't worry about the temperatures as long as the system is running fine and never slows down due to overheating.
×
×
  • Create New...