Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11334

  • Joined

  • Last visited

  • Days Won

    476

 Content Type 

Everything posted by Fiery

  1. Fiery
    Thank you. Please check if the DIMM slots numbering is correct on the Motherboard / SPD page. Maybe it's correct there, and is only wrong on the Computer / Sensor page?
  2. Fiery
    Thank you for your feedback. I'd say the values reported by AIDA64 are closer to the truth than SIV's
  3. Fiery
    Does AIDA64 report Quad Channel DDR4 on the AIDA64 CPUID Panel? If yes, then please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). 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. Thanks, Fiery
  4. Fiery
    Are you sure your DIMM slots are properly populated in order to have all 4 memory channels enabled? If yes, then it means LGA2066 motherboards do not use a single layout for DIMM slots assignment -- in which case we need to implement motherboard specific DIMM slot numbering logic
  5. Fiery
    Thank you for the tip and also for your patience about this issue. We've implemented RAID member enumeration, RAID SMART support for LSI "IR" SATA RAID controllers; as well as SMART support for drives connected to LSI "IT" SATA AHCI controllers. 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.
  6. Fiery
    Here's the above mentioned new AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta
  7. 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 how it works
  8. Fiery
    It is Here's the fixed AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta
  9. Fiery
    Using AIDA64 you can have FPS displayed on an external display as long as the tool (RTSS or Fraps) provides the readings to AIDA64. AIDA64 itself cannot monitor FPS directly.
  10. Fiery
    I'm afraid we haven't been able to reproduce the issue on our test systems yet. We also haven't found a clear pattern in the various bug reports about slow EC communication issues.
  11. Fiery
    AIDA64 doesn't monitor mouse activity.
  12. Fiery
    As far as I can understand, that picture frame isn't capable of transferring full bitmap frames from a computer to the digital picture frame. So it cannot be supported by AIDA64 or any other monitoring software.
  13. Fiery
    Yes, those spikes are because LiveDash also fiddles around the EC, and switches EC banks back and forth. There's no real solution to that issue I'm afraid. The only "solution" is to disable EC bank switching in AIDA64, that way you won't see any temperature spikes in LiveDash.
  14. Fiery
    Is your CPU or RAM overclocked, or has specially tuned settings applied in the BIOS Setup? (UEFI Setup)
  15. Fiery
    I'm not sure if it's possible. We'll try an older method that worked on previous Asus ROG motherboards, and we'll see A new AIDA64 beta build should be ready sometime tomorrow. I'll post a message into this topic once the new beta build is available for download.
  16. Fiery
    The CPU Package value and the other 2 values (CPU VDD power and CPU VDDNB power) are measured using different interfaces of the CPU. Hence their values may not match each other, and one (or both) may well be inaccurate -- we've seen such issues with previous AMD processor generations like Kaveri already. BTW, VDDNB is the north bridge (memory controller and fabric) section of the Ryzen CPU.
  17. Fiery
    Detecting IMEI would require our app to request for special permissions. We try to avoid asking for too many permissions, so we skip IMEI detection. Regards, Fiery
  18. Fiery
    Some Maximus X Hero motherboards have VRM temperature readout, while others wouldn't. It seems there are multiple versions of seemingly the same motherboard are out there.
  19. Fiery
    Corsair decided to discontinue supporting the industry standard synchronization mutexes in the recent updates of their Corsair Link Software. So it may no longer work together with 3rd party monitoring software like AIDA64
  20. Fiery
    Thank you for your feedback
  21. Fiery
    Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Make sure to have both EC stability options enabled.
  22. Fiery
    Thank you. Here's a new AIDA64 beta where we've fixed the voltage readings for your motherboard: https://www.aida64.com/downloads/latesta64xebeta
  23. Fiery
    You need to enable both Embedded Controller (EC) support and Embedded Controller (EC) bank switching in AIDA64 / main menu / File / Preferences / Stability. That will unlock a few additional sensor readings on your motherboard. Make sure to not have Asus AI Suite or any of its background services installed on your system. If you have any of those left around, a collision may occur while AIDA64 tries to perform EC bank switching, and it may just cause a system lockup or sudden system restart.
  24. Fiery
    The time it takes for AIDA64 to allocate the RAM also depends on how fragmented the system memory currently is. So it's not possible to give a concrete number on that.
  25. Fiery
    I'm afraid we are still unable to reproduce the issue on your test systems, even with KernelEx installed
×
×
  • Create New...