Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12008

  • Joined

  • Last visited

  • Days Won

    525

 Content Type 

Everything posted by Fiery

  1. 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.
  2. 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.
  3. Fiery
    AIDA64 doesn't monitor mouse activity.
  4. 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.
  5. 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.
  6. Fiery
    Is your CPU or RAM overclocked, or has specially tuned settings applied in the BIOS Setup? (UEFI Setup)
  7. 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.
  8. 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.
  9. 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
  10. 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.
  11. 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
  12. Fiery
    Thank you for your feedback
  13. 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.
  14. 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
  15. 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.
  16. 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.
  17. Fiery
    I'm afraid we are still unable to reproduce the issue on your test systems, even with KernelEx installed
  18. Fiery
    I'd try to run another monitoring software and AIDA64 stress test in the same time, and see if the heavy stress makes the other software experience EC register readout glitches. If yes, then it's a hardware issue, and not an AIDA64 related issue.
  19. Fiery
    If you use START with /WAIT, you can add a new line after your quoted line to open the resulting report file. For example, something like the following line should do the trick: START reportfilename.htm BTW, your quoted command-line lacks the necessary report creation command, e.g. /R <reportfilename>
  20. Fiery
    I guess then either the BIOS itself interferes sometimes with the EC register readout activity of AIDA64, or the EC sometimes becomes slightly unstable in providing the right register values. Old older motherboards we've seen EC communication issues when the system is under heavy load -- but no glitches when the computer is idle.
  21. Fiery
    What motherboard do you have? Rampage VI Extreme?
  22. Fiery
    I have no idea. HWiNFO is not our software, so we don't have deep understanding on the way it handles your system.
  23. Fiery
    The difference (between your X99 and X299 systems) might be the Windows 10 build. In Windows 10 the higher the build number is, the slower some of the kernel calls get. So allocating the same amount of RAM in Windows 10 Fall Creators Update could well be slower than what it used to be with Windows 10 Creators Update or Anniversary Update. As for the EC register readout issues: do you have EC bank switching enabled in AIDA64 / main menu / File / Preferences / Stability?
  24. Fiery
    The invalid temperature readings are usually caused by another monitoring tool colliding with AIDA64 about EC (Embedded Controller) register readout. In your case the most likely candidate for such software is Asus' own monitoring application AI Suite. Currently there's no 100% reliable way to fix it up. So if you'd like to avoid such collisions, make sure to uninstall AI Suite, including its background services. As for the half a minute freezing after you start a stress test session: it's caused by Windows kernel which can get quite slow and bumpy when an application tries to allocate a huge chunk of system memory. And that's exactly what the memory subtest of AIDA64 System Stability Test initiates right after you press the Start button. As soon as all the system memory is allocated by the AIDA64 stress test, Windows should return back to normal responsivity. The duration of the "bumpy" phase depends on the amount of system RAM you have installed.
  25. Fiery
    I suppose the issue may not be your memory modules, but rather the timing settings you have configured in your BIOS Setup (UEFI Setup). Try to use less agressive settings, e.g. up the Command Rate from 1T to 2T as a start, and see if that helps. Also, make sure to update your BIOS to the latest stable release.
×
×
  • Create New...