Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12171

  • Joined

  • Last visited

  • Days Won

    535

 Content Type 

Everything posted by Fiery

  1. Fiery
    Thank you! Did you have any other AIDA64 window open the time the error message popped up, or only the main window and the Preferences window?
  2. Fiery
    Are you configuring the SensorPanel with the configuration window placed on the same monitor as the SensorPanel, or you have multiple monitors and you dedicate one of them for the SensorPanel? Can you please also create a broader screenshot where we can see from what window (of AIDA64) does that popup comes up from?
  3. Fiery
    The project is still on hold I'm afraid. @Jupiterone02 Do you guys still own and use the Azoth keyboard? If so, would you be interested in having AIDA64 to handle the Azoth keyboard using direct communication with the OLED screen? Such an approach may require you to close concurrent software that may also be talking to the OLED screen, primarily the one made by Asus themselves.
  4. Fiery
    AX206 LCD is also supported but it's a different LCD module of AIDA64. You can configure your AX206 device in AIDA64 / Preferences / Hardware Monitoring / LCD / AX206.
  5. Fiery
    We've implemented support for Corsair iCUE Nexus LCD display in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. You can activate and configure the Nexus LCD module in AIDA64 / Preferences / Hardware Monitoring / LCD / Corsair.
  6. Fiery
    @Vitality We've implemented support for Corsair iCUE Nexus LCD display in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. You can activate and configure the Nexus LCD module in AIDA64 / Preferences / Hardware Monitoring / LCD / Corsair. Let me know how it works.
  7. Fiery
    We've implemented support for Corsair iCUE Nexus LCD display in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. You can activate and configure the Nexus LCD module in AIDA64 / Preferences / Hardware Monitoring / LCD / Corsair. Let me know how it works.
  8. Fiery
    @p1r473 @s3r1u5 @Ghiroza We've implemented support for Corsair iCUE Nexus LCD display in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. You can activate and configure the Nexus LCD module in AIDA64 / Preferences / Hardware Monitoring / LCD / Corsair. Let me know how it works.
  9. Fiery
    Please find the fixed AIDA64 beta build at: https://www.aida64.com/downloads/latesta64xebeta
  10. Fiery
    Thank you! Please check the latest AIDA64 beta update 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.
  11. Fiery
    Done that, thank you. We'll see if they can help us out with the necessary technical information there.
  12. Fiery
    Thank you! Please try the following: 1) Disable OSD. If you have it enabled already, you can do that without starting AIDA64 and so triggering the BSoD. Just navigate to the installation folder of AIDA64 and edit the file you can find there named AIDA64.INI using e.g. Notepad. Find the following line in the file: HWMonEnableOSD=1 And update it to: HWMonEnableOSD=0 Save the file. 2) Start AIDA64. Press Ctrl+D --> HWMon Modules --> uncheck (untick) ACPI there. 3) Now try to enable OSD and close AIDA64. See if it triggers the BSoD.
  13. Fiery
    Thank you! You're right, there're no "interesting" or "suspicious" USB devices connected to your system.
  14. Fiery
    We've done a lot of changes and improvements between v5.99 and v6.00. It looks like a minor update, but it wasn't.
  15. Fiery
    Have you enabled incoming connections on your main rig using Remote / Accept Incoming Remote Connections ?
  16. Fiery
    The problem is the sensor module of AIDA64 that you can effectively disable by fiddling around with the AIDA64 kernel driver, e.g. by renaming its file But, since the sensor module consists of a code over 130 thousand (!) lines, it's very difficult to find the exact place that causes the issue, especially since the bug doesn't come up with the issue occurs, but rather it only rears its ugly head when you close AIDA64. That makes it a _lot_ more difficult to find. We'd need to reproduce the issue on our own test systems. But, first we'd need to know which hardware or software component in your system causes the troubles. And that's where we're stuck since none of the apparent candidates seems to be the one. Not your motherboard, not the video card. It could be an external device like an USB-connected peripheral, but we'd need to find out which one first. BTW, do you have the latest BIOS installed for your motherboard?
  17. Fiery
    I like the idea, but it's not something we'd put at high priority, especially through the summer where we have limited resources due to folks being on vacation left and right We've categorized this as a future improvement idea that we may work on later on.
  18. Fiery
    Once you have a valid license for AIDA64, it will automatically update itself. Until then, just close AIDA64, go to our Downloads page: https://www.aida64.com/downloads Select the update you need, pick the ZIP package variant. For example, the latest stable release of v7.70 is available at: https://www.aida64.com/downloads/ODA1NDJhZjA= Download the ZIP package and extract it into the existing installation folder of AIDA64. Let it overwrite any existing files. Your configuration and settings are retained through the process.
  19. Fiery
    Please use AIDA64 v7.99 from now on, for all test runs and other purposes as well. https://forums.aida64.com/topic/18367-the-next-generation-aida64-is-around-the-corner/
  20. Fiery
    By using that method you effectively disabled the kernel driver of AIDA64. As for your NVMe drive, #2 in that context means the secondary thermal diode of the single NVMe SSD you've got.
  21. Fiery
    I'm afraid it's not possible to indicate that state of a HDD/SSD using AIDA64.
  22. Fiery
    The OSD (and the SensorPanel as well) is not supposed to work with full-screen games or other full-screen applications. You can use the OSD or the SensorPanel on a secondary monitor while you're playing a game full-screen on your primary monitor.
  23. Fiery
    There's an Auto-scale option for SensorPanel/LCD graphs that can be used to mitigate the issue you've described.
  24. Fiery
    Thank you. It must not be related to your motherboard since AIDA64 v7.35 works fine with another owner of the same motherboard you've got (MSI Z270 Tomahawk).
  25. Fiery
    So you mean you've actually tried it with v6.00.5100 and it failed to work?
×
×
  • Create New...