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
    Do you have any special desktop extensions installed?
  2. 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.
  3. 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.
  4. 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?
  5. 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.
  6. Fiery
    No, unless its Windows device description can be altered in the driver of the device.
  7. 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).
  8. 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).
  9. 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.
  10. Fiery
    It means you have an Asetek LC based water cooling system in your system ... somewhere
  11. Fiery
    There are many ways of allocating huge chunks of memory actually. We're already working on a proper solution.
  12. Fiery
    We'll update the users manuals in the next AIDA64 beta update.
  13. 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.
  14. 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.
  15. 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.
  16. 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
  17. Fiery
    Sensor readings on the SensorPanel can be renamed anytime
  18. Fiery
    Are you sure the new optic connection uses the same network interface (network adapter) as your old ADSL connection? Make sure to check all network interfaces on the Network / Windows Network page of AIDA64.
  19. Fiery
    You've got valid points about both issues. The problem is that none of those seem to be something that could be solved with an easy or quick patch We're discussing these issues internally and will try to come up with a proper solution or an acceptable workaround soon.
  20. Fiery
    No, the issue seems to be more the combination of large amount of RAM and large amount of CPU threads. So when you use an ordinary system with 4 cores and 4 or 8 threads, with small amount of RAM (8GB or less), Windows 10 can quickly allocate the physical memory for the AIDA64 memory stress test. But as you increase the amount of RAM, and especially if you also increase the amount of CPU threads (logical processors), the issue gets a lot worse. To us it seems Windows 10 simply "gets too busy" for 10 or 20 seconds when an application uses too many concurrent threads where each of those threads tries to allocate a large portion of RAM. It becomes a "race for RAM" situation where Windows 10 gets unresponsive. It's not a bug in our software per se, but more a situation where Windows 10 is pushed to its limits. Which is what a stress test is supposed to do BTW ... ... but I understand that from an end-user's perspective it is annoying to experience. We're in discussion with the development team right now to try and find a workaround for this issue.
  21. Fiery
    tacal666 : do you have any other monitoring software installed? Like ASRock A-Tuning Utility? aTsgR : This is a known issue about Asus AM4 and TR4 socket based motherboards. Asus is already working on the fix that will deliver as a future BIOS update. When it becomes available, we will need to modify AIDA64 to work with the new sensor interface. The new interface will be a lot more solid and will finally prevent any form of collision between the ROG chips and 3rd party monitoring software like AIDA64.
  22. Fiery
    Make sure to check if you have a similar reading in the UEFI Setup (BIOS Setup) or in Gigabyte's own monitoring software. If you can find a thermal reading there with such high measured value, then AIDA64 indicates the right temperature values.
  23. Fiery
    We've tested AIDA64 v5.97 on over a dozen of Windows XP based systems, including ones with nVIDIA GeForce 8000 class video cards, P965 chipset, Core 2 processors, but found no issues whatsoever.
  24. Fiery
    It wouldn't make much sense to avoid using AVX-512 just because without it your CPU *seems* to be stable
  25. Fiery
    In AIDA64 v5.97 we've implemented AVX-512 optimizations in the FPU, Cache and RAM subtests of the AIDA64 System Stability Test. So all those subtests now may be a bit smarter to reveal a stability issue either related to a hardware failure or an excessive overclock.
×
×
  • Create New...