Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12281

  • Joined

  • Last visited

  • Days Won

    541

 Content Type 

Everything posted by Fiery

  1. Fiery
    Thank you. Please 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.
  2. Fiery
    Please 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.
  3. Fiery
    We've fixed the issue in 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. Regards, Fiery
  4. Fiery
    Thank you for your help! It's always great to work with guys skilled in both electronics and C++
  5. Fiery
    Please use MSI's own software as a reference on MSI motherboards, and Asus' own software as a reference on Asus motherboards. We'll add CPU VID voltage below the CPU Vcore reading to the Sensor page as well, so you can see both values listed.
  6. Fiery
    We follow MSI's recommendations on how to handle the sensor registers on MSI Z270 motherboards. What exactly is the issue about the Vcore? Does MSI's own monitoring software measure a different value or the same value?
  7. Fiery
    We've notified the authors of CPU-Z about this issue, asking them to implement the synchronization mutex that we've defined in order to avoid this issue. I'm not sure if it is already implemented in HWiNFO, so we'll ping its authors too.
  8. Fiery
    Meanwhile we've found a solution to fix the collision between AIDA64 and aquasuite 2017. It will be implemented in the next AIDA64 beta update. I'm not sure if it helps about the slow updates too, but it's worth a try
  9. Fiery
    The collision issue between AIDA64 and aquasuite 2017 will be fixed in the next AIDA64 beta update. I'll post a message into this topic once the new beta update is available for download. As for the 10 drives limit, yes, it's a limit built into AIDA64. Do you have more than 10 drives, so you would like to see the limit expanded? If so, how many drives do you have?
  10. Fiery
    The issue will be fixed in the next AIDA64 beta update. I'll post a message into this topic once the new beta update is available for download.
  11. Fiery
    I'm not sure what you're looking for. Can you please explain what exactly do you want to do about your E3815 CPU?
  12. Fiery
    Thank you. Apparently the 4 fan registers corresponding to Chassis #n fans are all zero after waking up from sleep. We suspect it's because the BIOS fails to properly re-initialize the sensor registers after the computer comes back from sleep. I would have suggested you to update the BIOS, but you seem to be using the latest version of it. Apart from asking Asus about this, and reporting them about this potential BIOS bug, I'm not sure what can be done to get around this issue
  13. Fiery
    The missing drives could be because of Aquasuite. The latest version of that software seems to open drives exclusively, and monitors them in a way that makes other software unable to access the drives
  14. Fiery
    Thank you. We'll check it on a similar Sandy Bridge configuration soon.
  15. Fiery
    Thank you. 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. Please repeat that dump after the computer wakes up from sleep and the fans already disappeared. Thanks, Fiery
  16. Fiery
    We've checked the foobar2000 SDK, but it seems quite complicated to use. For such a minor improvement we simply find it too awkward and complex to deal with. Maybe we're looking at the wrong bits and pieces though, so if you (or someone else) can provide a short source code to detect the information you're looking for, we'd be happy to implement it. I'm afraid we have no plans about an audio visualizer for AIDA64.
  17. Fiery
    We've checked the foobar2000 SDK, but it seems quite complicated to use. For such a minor improvement we simply find it too awkward and complex to deal with. Maybe we're looking at the wrong bits and pieces though, so if you (or someone else) can provide a short source code to detect the information you're looking for, we'd be happy to implement it.
  18. Fiery
    Thank you for your feedback
  19. Fiery
    T Thank you, the issue will be fixed in the next AIDA64 beta update due next week
  20. Fiery
    Do you mean the fans labelled by AIDA64 as Chassis #1, Chassis #2, Chassis #3 and Chassis #4?
  21. Fiery
    Thank you, that was very helpful. I've sent you an email about further details
  22. Fiery
    Aquasuite opens the drives and gains exclusive access to them, so that explains why AIDA64 cannot access the drive activity statistics. Aquacomputer needs to fix their service to enable concurrent access to drive activity statistics. Regards, Fiery
  23. Fiery
    No, we cannot replicate the issue on our own test systems. Have you verified the priority settings on your computer? Also, I don't think the difference between Windows 7 and Windows 10 across your computers is the key to this issue. It's rather the hardware difference. Can you please tell us more about your Windows 10 computer? Motherboard model, CPU type, video card(s) model?
  24. Fiery
    Thank you for the feedback
  25. Fiery
    Thank you for checking the latest beta. Please let us know what exact motherboard and video card you've got, and whether you have any external (USB) storage devices connected, or any RAID arrays defined. We'll build a similar configuration and try to replicate the issue.
×
×
  • Create New...