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
    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.
  2. 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.
  3. 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.
  4. 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
  5. Fiery
    Sensor readings on the SensorPanel can be renamed anytime
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. Fiery
    It wouldn't make much sense to avoid using AVX-512 just because without it your CPU *seems* to be stable
  13. 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.
  14. Fiery
    Most likely Samsung decided to remove those temperatures from the latest Oreo update. You can verify the theory by checking other apps, e.g. HWMonitor. They should measure the same set of temperatures than AIDA64. If they do, it's a platform limitation, and not a bug in our app (AIDA64).
  15. Fiery
    With the latest version of AIDA64 (v5.97) please post an updated ISA Sensor Dump, so we can check the registers as they look now with the thermistor cable connected.
  16. Fiery
    Are you using the latest version of AIDA64, v5.97? CPU Package means the overall CPU temperature, as measured by the CPU itself, using its on-die thermal diode.
  17. Fiery
    CPU Current is measured directly on certain Asus motherboards. In other words, the Ampers value is directly read from the Embedded Controller, and no conversion is applied. So in case the values are all over the place, it's the fault of the motherboard sensor, since AIDA64 doesn't do anything else but read the value and show it.
  18. Fiery
    Bluetooth version cannot be detected directly on Android devices. We're planning to add that info using a backend hardware database in a future version of AIDA64 for Android.
  19. Fiery
    Once those temperature rails can measure a non-minus55C value, AIDA64 will automatically show them.
  20. Fiery
    Do you have DIMM thermal sensor support enabled in AIDA64 / main menu / File / Preferences / Stability? Please note that you need to restart AIDA64 after altering that option.
  21. Fiery
    Sometime this year... Hopefully
  22. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  23. Fiery
    Thank you for your test runs. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  24. Fiery
    That is not something we'd like to pursue in our software.
  25. Fiery
    You're not forgotten at all We just need to get a similar configuration to yours, install WinXP on it, and check out what could have gone wrong. It takes a bit of time to get that done, especially the "get a similar hardware" issue.
×
×
  • Create New...