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! With TB3 disabled we can still experience the same issue on our own Asus Prime X299-A motherboard based test system. In your dump you can see the anomaly as: Time #3 = 0.230 / 0.272 / 0.269 / 0.225 / 0.258 / 0.241 / 0.266 / 0.230 / 0.230 / 0.301 / 0.218 / 262.524 / 0.338 / 0.443 / 0.230 / 0.246 msec AIDA64 reads 16 registers from the EC there, and one case out of 16 it slows down tremendously. The chances of that happening seems to be similar on our Prime X299-A motherboard. So typically once per every 10 or 20 EC register accesses gets a penalty that way. We'll contact Asus to find out what can we do on our end to avoid the penalties.
  2. Fiery
    I'd second an3k's suggestion on trying to disable both EC options on the Stability page: Embedded Controller (EC) sensor support Embedded Controller (EC) bank switching Aquasuite is supposed to work well together with 3rd party applications about ISA based sensor chip access, but maybe it collides with AIDA64 if it also tries to read EC registers.
  3. Fiery
    The above mentioned new AIDA64 beta build is available at: https://www.aida64.com/downloads/latesta64xebeta
  4. Fiery
    The above mentioned new AIDA64 beta build is available for download at: https://www.aida64.com/downloads/latesta64xebeta The 6 temperature readings come from the onboard sensor chip. The chip (IT8686E) supports 6 temperature readings, but only 4 is utilized by your motherboard.
  5. Fiery
    Thank you for the info. We'll do relevant test runs tonight as well. Meanwhile, we've added more debug information to the Embedded Controller dump. Please post an updated such dump using the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta Thank you in advance!
  6. Fiery
    There's no technical solution to the issue.
  7. Fiery
    Yes, we're planning to develop the GPGPU benchmarks further, but we currently have no definitive roadmap on your ideas I'm afraid.
  8. Fiery
    I'm not sure what Gigabyte G7 refers to. Is it a Gigabyte motherboard with Z370 chipset? If yes, then which one? Do you have any special sensor devices connected, like via USB? Do you have any RAID arrays defined? Please also let me know what version of ForceWare do you have installed.
  9. Fiery
    Do you have any special desktop extensions installed?
  10. Fiery
    First of all, please upgrade to the latest version of AIDA64, v5.97: https://www.aida64.com/downloads/latesta64xe If it doesn't help, please try to disable Embedded Controller (EC) support in AIDA64 / main menu / File / Preferences /Stability. Maybe without it you won't have sound drops. Let me know if it helps. Note that you need to restart AIDA64 after altering the EC stability option.
  11. Fiery
    We cannot see any changes that would impact legacy Windows compatibility. The strangest thing is that not even the splash screen appears. If it did, we could at least have the last init message displayed on the bottom of the splash screen, and that would lead us to the part of the code that is to blame. One thing you can check is startup logging. Please try the following: 1) Download AIDA64 Engineer v5.97 from: https://www.aida64.com/downloads/latesta64ee 2) Install it, and go to its installation folder using Command Prompt. 3) From Command Prompt launch: AIDA64.EXE /STARTUPLOG 4) After recovering from the lockup, check if you have a file called StartupLog.txt on your Windows Desktop. If you do, please attach the file to a forum post so we can check it out.
  12. Fiery
    While AIDA64 is running, right-click on the bottom status bar of AIDA64 main window --> HWMon Modules --> Aquaero. You may need to enable status bar in AIDA64 / main menu / View first. That will temporarily disable the Aquaero monitoring module, so you can see if something in that module causes the issues. Let me know how the test goes. BTW, what devices from AquaComputer do you have installed in your system? And what version of AquaSuite do you have installed?
  13. Fiery
    Thank you for the info and data. We'll implement support for negative CPU temperature for Asus motherboards in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new beta build is available for download.
  14. Fiery
    No, unless its Windows device description can be altered in the driver of the device.
  15. Fiery
    Thank you. We're investigating this issue. Apparently something makes the EC register readout slow down tremendously on certain Asus motherboards, but only intermittently. Sometimes it's lightning fast (like 0.2 millisec), but in other cases it can be 1000 times slower (over 200 millisec).
  16. Fiery
    Thank you for the screen shots, they were very helpful. In the next AIDA64 beta update we'll remove the 2 incorrect thermal readings (PCI-E and Aux).
  17. Fiery
    On the Computer / Sensor page AIDA64 displays a hint (in brackets) for each such generic sensor readings. We've put those hints to make it easier to figure out their assignments.
  18. Fiery
    It means you have an Asetek LC based water cooling system in your system ... somewhere
  19. Fiery
    There are many ways of allocating huge chunks of memory actually. We're already working on a proper solution.
  20. Fiery
    We'll update the users manuals in the next AIDA64 beta update.
  21. Fiery
    Make sure to also enable Asetek LC sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Fans connected to non-motherboard-related sensor devices (like external / USB connected sensor devices) are numbered starting from Fan #21. This is a pecularity of the AIDA64 hardware monitoring module.
  22. Fiery
    This is a new phenomenon to us. Previously we've seen no such issues about ASRock motherboards. We suspect the issue is a system component that keeps altering the sensor registers, and sometimes that activity collides with AIDA64 about sensor register access. It would be important to find out what system component may be responsible for the collision. Are you sure you don't have any monitoring software or a component (like a service module) of them left over after the uninstallation of the mentioned 2 software? Please also try to ask ASRock's Tech Support, maybe they know what the collision is caused by.
  23. Fiery
    It's not our ETA I'm afraid. The work has to be done by Asus who is responsible for coming up with a sensor interface that enables 3rd party applications like AIDA64 (and HWiNFO, HWMonitor, SIV, etc) to work stable, without them interfering with the BIOS and AI Suite.
  24. Fiery
    I have no idea why they've decided to cripple the thermal subsystem like that. Google did the same with Nexus and Pixel devices, so it's sort of an unfortunate trend
  25. Fiery
    Sensor readings on the SensorPanel can be renamed anytime
×
×
  • Create New...