Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11546

  • Joined

  • Last visited

  • Days Won

    489

 Content Type 

Everything posted by Fiery

  1. Fiery
    Thank you for your feedback! We're planning to roll out a new stable update sometime next month.
  2. Fiery
    Thank you for your feedback! AI Suite can indeed collide with other software that also polls the EC (Embedded Controller) chip for sensor registers. Sadly, Asus still haven't made any steps to synchronize AI Suite or other software of theirs with 3rd party monitoring applications. Other than uninstalling AI Suite and all its background services there's no solution to this issue I'm afraid. As for CPU Package, there's no offset to use on any processors, as far as we know. So AIDA64 should report the accurate readout as it is provided by the CPU. If you however are adamant that there's an offset to be applied, then you can configure it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction.
  3. Fiery
    The following document should help you: http://download.aida64.com/resources/lcd/aida64_lcd_guide.pdf As for the mentioned device, that is not supported by AIDA64 currently. To me it looks like a SPI connected device, in which case you need to find a way to connect it to your computer at first. Most likely you would want to connect the device to a USB port, using e.g. a FTDI FT232H bridge chip.
  4. Fiery
    It says:
  5. Fiery
    Such things could happen when the text simply doesn't fit on the screen of the mobile device, and so the browser will wrap the text into multiple lines. Did you configure the right resolution for your browser? Also, I think the font is also incorrect. It could happen when the browser running on the mobile device doesn't support the selected font. In which case you should simply use a different font, like Arial.
  6. Fiery
    Please try the following new AIDA64 beta build, where we've tweaked on the CPU power reading for Asus X99 Series motherboards: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  7. Fiery
    The above mentioned new AIDA64 beta build is now available for download: https://www.aida64.com/downloads/latesta64xebeta
  8. Fiery
    The above mentioned new AIDA64 beta build is now available for download: https://www.aida64.com/downloads/latesta64xebeta
  9. Fiery
    All I know is that VIN0 is Vcore But at idle its value shouldn't be used.
  10. Fiery
    If you purchase a USB-connected device from Crystalfontz, it should be supported by AIDA64 right out of the box. It's up to you to decide which Crystalfontz display is best for your needs.
  11. Fiery
    VIN0 line holds VCore, not VCCIN.
  12. Fiery
    We may enable that in the near future, but only via a Stability option as you've suggested.
  13. Fiery
    Thank you for your feedback. Measuring W_IN and W_OUT would require EC (Embedded Controller) bank switching, which is a dangerous procedure to perform on Asus motherboards. EC bank switching may collide with Asus' own AI Suite software package or its underlying service components, or the BIOS itself, and could cause system lockup or other stability issues. T_Sensor is a generic label, meaning Temperature Sensor, that's why AIDA64 also uses a generic label for it. It's correct that way. On your motherboard Fan #4 will be renamed to "Water Pump" fan in the next AIDA64 beta update due in a few days from now.
  14. Fiery
    AIDA64 CPUID Panel shows Vcore, matching the "CPU Core" voltage reading on the Computer / Sensor page. There's no separate CPU VRM voltage rail that one could measure on your motherboard AFAIK. We'll add +3.3V readout in the next AIDA64 beta update due in a few days from now
  15. Fiery
    As long as your CPU works stable at those high temperature levels, and your CPU isn't throttling, you have nothing to worry about. AIDA64 System Stability Test -- especially its FPU subtest -- puts the worst case scenario on your system, so it's normal that it heats up immensely during the test.
  16. Fiery
    Thank you. We'll implement advanced support for your motherboard in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new AIDA64 beta build is available for download.
  17. Fiery
    Thank you. We'll implement advanced support for your motherboard in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new AIDA64 beta build is available for download.
  18. Fiery
    There's nothing wrong with the actual benchmark results on your system. The warning message pops up simply to remind you that it doesn't use the full potential of your CPU, since it doesn't utilize AVX-512 yet, but only AVX2+FMA. We're still working on AVX-512 optimizations, and hope to be able to roll it out in mid-January.
  19. Fiery
    It's best to try to run the FPU subtest alone first, for a few hours. If your system can stand that, then without stopping the test just enable all the others, and let it run for a few more hours. If no error message, no sudden system restart, power-off or lockup occurs, then your system is considered pretty stable
  20. Fiery
    The "CPU" power reading should match the one measured by Asus' own software. The "CPU Package" power doesn't work because of the mentioned SVID configuration issue.
  21. Fiery
    All I can tell you about the Vcore issue is that AIDA64 does what the BIOS does on your motherboard. If the logic behind it seems odd, well, then the BIOS works odd too We've added the requested CPU Cache voltage reading 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. Let me know how it works
  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
    Not recently, no...
  24. Fiery
    I'm glad you've found a useful tool for your purposes
  25. Fiery
    Thank you for the data. It seems to me that the problem is that your CFA634 display is not the CFA634-USB display that is supported by AIDA64. Our software currently only supports factory USB variants of Crystalfontz displays. It doesn't support serial displays connected with proprietary (or 3rd party) solutions like what you seem to be using. Or maybe you have a factory (Crystalfontz made) CFA634 version that predates the CFA634-USB variant that we are aware of?
×
×
  • Create New...