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
    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.
  2. 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>
  3. 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.
  4. Fiery
    What motherboard do you have? Rampage VI Extreme?
  5. Fiery
    I have no idea. HWiNFO is not our software, so we don't have deep understanding on the way it handles your system.
  6. 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?
  7. 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.
  8. 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.
  9. Fiery
    We're not sure why that happens. Our best guess is that there must be a bottleneck about memory write bandwidth in the IMC (Integrated Memory Controller) of Skylake-X processors. And that bottleneck may work differently in 12+ core versions (HCC) than 10-core and lower SKUs of Skylake-X (LCC).
  10. Fiery
    No, language should have no impact on that feature. Does your Windows user have administrator privileges?
  11. Fiery
    Thank you for your feedback
  12. Fiery
    No, it's not the same thing. The EC warning is due to EC bank switching, which is indeed a dangerous thing to perform when AI Suite is installed.
  13. Fiery
    Make sure to always use the latest AIDA64 beta build on Asus ROG products -- although in this particular case it wouldn't help much I'm afraid. As a temporary workaround you can try disabling EC (Embedded Controller) support in AIDA64 / main menu / File / Preferences / Stability, but that may still not get things 100% stable. We've discussed the issues and came up with a possible solution with Asus' engineers. So yes, they are absolutely committed now to fix the collision issue.
  14. Fiery
    Asus is working on the solution as we speak. We need to give them a few more weeks to come up with a BIOS update that would solve the collision issues.
  15. Fiery
    The difference may be because of the throttling activity. BTW, we've already seen reports of incorrect CPU utilization reported by Windows Task Manager...
  16. Fiery
    Yes, it should work with any Asus ROG motherboard. We haven't tested the OLED screen yet. You need to check if Live Dash requires any AI Suite components that may collide with the EC layer of AIDA64.
  17. Fiery
    We're not quite sure why the DIMM numbering is illogical.
  18. Fiery
    1) I'm not sure, since it's not a quick project 2) Already replied above
  19. Fiery
    As I've explained above, the Sensor page is not meant to be customized. Use one of the listed features if you need to have the layout customized.
  20. Fiery
    Only the labels, but not the grouping logic
  21. 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. In order to make it easier for you to configure the SMTP parameters, we've added a new Provider option to the Preferences / E-mail/ SMTP page. That way you can select your email provider (e.g. AOL, Gmail, GMX, Outlook, Yahoo, etc) to limit the number of options you need to properly adjust. We've of course fixed the issues related to how AIDA64 handles SSL and the way it explicitly issues the STARTTLS command. Let me know how it works with both your providers.
  22. 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.
  23. Fiery
    I know. But the Sensor page was not designed to be customizable. If you need to customize the readings, you can do that via multiple other methods So there's a solution for everyone.
  24. Fiery
    You can already do that if you use any of the OSD Panel, Desktop Gadget, SensorPanel, or External LCD modules
  25. Fiery
    We've tried to reproduce the issue under Windows Server 2008 R2, but for us it worked flawlessly. It must be due to a special configuration setting on your system that prevents AIDA64 from accessing the necessary counters to measure disk activity. Do you know what setting might cause that?
×
×
  • Create New...