Jump to content
AIDA64 Discussion Forum

Fiery

Administrators
  • Content count

    7012
  • Joined

  • Last visited

  • Days Won

    342

Fiery last won the day on January 7

Fiery had the most liked content!

Community Reputation

316 Excellent

7 Followers

About Fiery

  • Rank
    AIDA64 Developer

Contact Methods

  • Website URL
    http://www.aida64.com

Profile Information

  • Gender
    Male
  • Location
    Budapest, Hungary
  • Interests
    AIDA64 :)
  1. Asus Maximus X Hero missing VRM temp

    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.
  2. 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
  3. Thank you for your feedback
  4. 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.
  5. Thank you. Here's a new AIDA64 beta where we've fixed the voltage readings for your motherboard: https://www.aida64.com/downloads/latesta64xebeta
  6. 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.
  7. 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.
  8. I'm afraid we are still unable to reproduce the issue on your test systems, even with KernelEx installed
  9. 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.
  10. Open report after generation

    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>
  11. 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.
  12. What motherboard do you have? Rampage VI Extreme?
  13. I have no idea. HWiNFO is not our software, so we don't have deep understanding on the way it handles your system.
  14. 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?
  15. 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.
×