Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12405

  • Joined

  • Last visited

  • Days Won

    550

 Content Type 

Everything posted by Fiery

  1. Fiery
    No, that's a separate issue that we expect nVIDIA to fix in a future ForceWare update.
  2. Fiery
    Thank you. Go to AIDA64 / main menu / File / Preferences / Stability, disable (uncheck) the option called Asus WMI sensor support, and restart AIDA64.
  3. Fiery
    We've presented our arguments, and also asked fellow developers (of CPU-Z, HWiNFO, HWMonitor, SIV, etc) to join in our efforts, but it didn't go through just yet. You as owners of Corsair hardware may need to put more pressure on Corsair to force them to find a proper resolution to this issue.
  4. Fiery
    Try to lower the DRAM frequency slightly. It may just help to stabilize your system.
  5. Fiery
    I don't think it's possible to pull the calculated efficiency data from Corsair Link Software or iCUE.
  6. Fiery
    Thank you. The issue has already been fixed in the latest AIDA64 Extreme update: https://www.aida64.com/downloads/latesta64xe
  7. Fiery

    Date format

    Fiery replied to ANUBIS's topic in Brainstorming

    AIDA64 uses the Windows default date format to display the date. I suppose you can alter the date format in Windows Regional Settings to achieve the date display you're looking for.
  8. Fiery
    No, because AIDA64 doesn't support dynamic measurement units.
  9. Fiery
    That would still provide virtualized values and not the real values for the underlying hardware, wouldn't it?
  10. Fiery
    We've tried to reproduce the issue on various Win7 64-bit machines of ours, but with no luck so far. If you still experience the issue, then please open Registry Editor (by running REGEDIT.EXE), navigate to the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management And export the Memory Management section by right-clicking on Memory Management in the tree --> Export. Please rename the resulting file to MEM.TXT and attach it to your forum post. If you have difficulties doing that, please contact me in private message.
  11. Fiery
    Thank you for your feedback
  12. Fiery
    That's most likely because of a collision between AIDA64 and Corsair iCUE. In iCUE Corsair decided to remove the synchronization mutexes that ensured that previous Corsair Link Software worked great together with 3rd party monitoring applications like AIDA64, HWiNFO, HWMonitor, SIV, etc. We're in conversation with Corsair and try to convince them to put the mutexes back again. Until then the collision can only be avoided by using only iCUE or only AIDA64, but not the two together in the same time.
  13. Fiery
    Please contact our international distributor Abseira for details on that: https://www.aida64.co.uk/support-request
  14. Fiery
    Thank you. IMHO no matter what component of the SSD the thermal reading is coming from, if it's higher than the rest, that's the one that is the critical temperature reading and so it should be considered the drive temperature.
  15. Fiery
    From where did you gather the info on the meaning of Drive Temperature 1 and 2?
  16. Fiery
    Thank you for your feedback, I'm glad it works now. Corsair Commander Pro should work already, as long as you have Corsair Link sensor support enabled in AIDA64 Preferences / Stability.
  17. Fiery
    Close AIDA64, download the ZIP package, extract its contents into your existing AIDA64 installation folder, and let it overwrite any existing files. Don't worry, your existing settings and your license will both be retained. Just make sure not to delete any files during the process.
  18. 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 how it works.
  19. Fiery
    Perfect, 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.
  20. Fiery
    Now https://www.aida64.com/downloads/latesta64xebeta
  21. Fiery
    Yes, the mouse hovering only works when there are more than 1 update available. We're planning to enhance the new version notification message box in the upcoming weeks, and we'll of course make it possible for you to check what's new in the new build. I'll drop a message into this topic once the enhanced message box is implemented.
  22. Fiery
    Thank you! It seems AIDA64 is unable to locate a necessary library file called SiUSBXp.dll. Can you please try to locate that file on your system and let us know the full path where that file resides?
  23. 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. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Corsair Link Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  24. Fiery
    Have you checked this solution?
  25. Fiery
    Your system may get unstable under heavy load due to overheating or PSU failure. Try to use the AIDA64 System Stability Test with only the FPU subtest enabled. It will put a very demanding load on your system. Let it run for a few hours and watch the temperature readouts as well as the CPU throttling graph. When your CPU throttles, it means it's overheating. If your system turns off or locks up (freezes) while running the AIDA64 stress test, there's definitely a hardware malfunction or configuration error.
×
×
  • Create New...