Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12228

  • Joined

  • Last visited

  • Days Won

    539

 Content Type 

Everything posted by Fiery

  1. Fiery
    In AIDA64 please press Ctrl+Alt+D --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  2. Fiery
    Yes, but you can use multiple LCD devices and the SensorPanel in the same time too.
  3. Fiery
    In order to support that display, we need programming information, SDK or some other guidelines from the manufacturer of your device.
  4. Fiery
    Do you have the same motherboard, X670E Steel Legend?
  5. Fiery
    Thank you, we'll fix the issue in the next AIDA64 beta update.
  6. Fiery
    You can enable multiple LCD modules in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD. You can for example enable both BeadaPanel and AlphaCool, and use one device of each kind. Several LCD modules support multiple devices of the same kind too.
  7. Fiery
    Please try to disable Low-level SMART operations in AIDA64 / main menu / File / Preferences / Stability.
  8. Fiery
    Let's see if the developers of BeadaPanel @beada have a solution for this issue
  9. Fiery
    1) What do you mean by that? 2) Multiple LCD displays are supported. 3) It is supported via Odospace (developed by a 3rd party) and RemoteSensor (our own solution, via web client).
  10. Fiery

    Валерий

    Fiery replied to Valera's topic in Android Forum

    Thank you for your feedback. Please note that ever since Android 7.0 (for whatever reason) Google decided to block apps from accessing several system files that were previously readable. That includes the files apps would need to show thermal sensor readings. Battery temperature reading is still available fortunately.
  11. Fiery
    @Cleanhead The mentioned new AIDA64 beta build is now available for download at: https://www.aida64.com/downloads/latesta64xebeta
  12. Fiery
    No problem, we'll swap them in the next beta build.
  13. Fiery
    Thank you! Are you sure you're not using custom labels for the fan readings? To me it looks like you've renamed one of the fan readings to "CPU #2". AFAIK we never use such label for fans.
  14. Fiery
    Thank you for your feedback, I'm glad we're making progress. About the fan labels, we're puzzled, it shouldn't look like that. In AIDA64 please press Ctrl+Alt+D --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. We will be able to fix the fan labels using that registers dump. As for OctalCore, that is phrased in different ways. OctalCore, OctoCore, and OctaCore are all in use, not to mention whether you use a dash before Core Soon, as 10+ core processors become more and more common, you won't see that since above 8 cores AIDA64 use numeric core count, as in "10-Core" and "16-Core" We're working on the rest of the missing Ryzen CPU sensor readings.
  15. Fiery
    @Cleanhead We've fixed the first issue and implemented support for Ryzen CCD temperatures measurement in the following new beta update of AIDA64: 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
  16. Fiery
    Please go to the Computer / DMI page in AIDA64, click on Motherboard, and make a screenshot of the page and post it here. Then on the same DMI page click on System, and make a screenshot of the page and post it here.
  17. Fiery
    Maybe there's a security layer that prevents direct access to disk drives. Either Windows Defender or some other security software that you've got installed. Or virtualization is enabled.
  18. Fiery
    @Luckyluke I've responded in your other topic. Let's continue investigating the issue you're having with AIDA64 in your other topic. This topic locked.
  19. Fiery
    Can you please check the memory consumption of AIDA64.EXE process when you first start it, and after around 15 minutes and then around 30 minutes of gaming? I'm wondering if this is due to a memory leak caused by improper communication between the AMD video driver hardware monitoring layer and AIDA64.
  20. Fiery
    In AIDA64 please press Ctrl+Alt+D --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  21. Fiery
    I've pinged our support dept about this issue. Please let me know here in this topic what the issue is about and I will try to resolve it for you. Do NOT publish your product key here.
  22. Fiery
    Quite frankly it consumed a lot of development and QC resources on our part to finalize the new UI before the previously set launch date of 04-Dec, and we simply had no time left to update the user's manuals. We will do that soon
  23. Fiery
    Thank you for your feedback! We'll fix the first issue in the next AIDA64 beta update, and will work on the rest too.
  24. Fiery
    We haven't added labels because it would greatly reduce the number of icons that would fit on the toolbar. We are now collecting ideas on how to step forward and enhance the new UI, and we're open to discussing various concepts and wishes about the new toolbar. BTW, if you move the mouse cursor above an icon and let it hover, a hint bubble is displayed with the icon caption.
  25. Fiery
    I've sent you an email about this.
×
×
  • Create New...