Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12431

  • Joined

  • Last visited

  • Days Won

    554

 Content Type 

Everything posted by Fiery

  1. 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?
  2. 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.
  3. 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.
  4. 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/
  5. 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.
  6. Fiery
    I'm afraid it's not possible to indicate that state of a HDD/SSD using AIDA64.
  7. 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.
  8. Fiery
    There's an Auto-scale option for SensorPanel/LCD graphs that can be used to mitigate the issue you've described.
  9. 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).
  10. Fiery
    So you mean you've actually tried it with v6.00.5100 and it failed to work?
  11. Fiery
    Thank you! The issue will be fixed in the next AIDA64 beta update due before the end of this week
  12. Fiery
    Thank you! That's a brand new variant of Asus RTX5090 that we haven't seen before. Please let me know the full model name of your video card, e.g. ROG-XXXX-RTX5090-YYYY-ZZZZ.
  13. Fiery
    In AIDA64 please press Ctrl+D --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. If possible, please try to find the screen in the USB Dump or let us know the USB vendor ID + product ID pair of it if you could find it out. Thanks, Fiery
  14. Fiery
    We've tested it but couldn't reproduce the issue about AIDA64 waking your system up from sleep mode
  15. Fiery
    Well, it actually was already possible with other kind of external (USB) LCD displays like BeadaPanel, Matrix Orbital, etc.
  16. Fiery
    Thank you! We have tons of new features and improvements implemented since AIDA64 v5.99 (which was released almost 7 years ago) so it's very difficult to narrow it down just based on that info However, we can continue with your USB devices: in AIDA64 please press Ctrl+D --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thank you in advance!
  17. Fiery
    Thank you! It's great that you've had a chance to check both those video cards, because it rules out that the culprit is the video card in this case. Please try to disable (uncheck) Low-level SMBus operations in AIDA64 / Preferences / Stability. Wait a bit after closing the Preferences with its OK button, then restart AIDA64 to apply the changes. If it still triggers a BSoD that way, then please try to disable (uncheck) Low-level sensor operations in AIDA64 / Preferences / Stability. Wait a bit after closing the Preferences with its OK button, then restart AIDA64 to apply the changes. Let me know if disabling any of those options would help to get rid of the BSoD. And I'm sorry for the pain and difficulties this issue is causing you, but we need to dig down deeper to find where the issue is.
  18. Fiery
    What video card do you have? Do you have all updates and security fixes available to Windows 10 installed via Windows Update?
  19. Fiery
    It's supposed to still be there. If you cannot see it listed on the Computer / Sensor page, then in AIDA64 please press Ctrl+D --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  20. Fiery
    Sadly we don't have neither of those platforms. Can you please ask Intel whether the issue affects only ARL-H and PTL-H platforms, or is there any other platform we can use to replicate the issue?
  21. Fiery
    The imported layouts always completely overwrite the existing layout, regardless of how many items you have on each imported page. If you want to join or merge two layouts, then you need to export them into separate LCD layout files, and do the merging process manually by editing the layout files with Notepad (or any other text file editor).
  22. Fiery
    Previously you've claimed that you had already paid for AIDA64.
  23. Fiery
    Please send me your AIDA64 product key in private message.
  24. Fiery
    Yes, higher update rate (in terms of how many updates per second) demands more resources. But it's not possible to pick & choose what sensor items do you want to have updated more frequently than others. So when it's a 100 msec, every sensor items are updated 10 times a second and the SensorPanel itself is rendered and updated 10 times a second. That's of course the ideal case when the sensors update and rendering would take no time at all So for example, if polling all sensors takes 100 millisec, rendering the SensorPanel takes 50 milisec, then a 100 millisec update rate means only 4 complete updates per second.
  25. Fiery
    Our summer sale campaign not yet started
×
×
  • Create New...