Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12284

  • Joined

  • Last visited

  • Days Won

    541

 Content Type 

Everything posted by Fiery

  1. Fiery
    Most non-ATA-compliant storage devices do not feature a proper model ID that would let us add them to our storage device databases. And it's already very difficult and time consuming to maintain the HDD and SSD databases, so we're not really keen on piling up even more tasks over that already huge pile of things to do every day...
  2. Fiery
    Make sure to 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.
  3. Fiery
    Just a sidenote: a process can load a DLL (in this particular case the one for NVAPI) which can issue kernel driver calls (exactly what happens in this case) which can then cause a BSoD. Sometime it's difficult to go through that chain of calls to find the culprit
  4. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> Battery 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. Thanks, Fiery
  5. Fiery
    Since the issue affects any software that uses NVAPI (nVIDIA's own API), it should be pretty easy to reproduce it in nVIDIA's own labs. We can however be of assistance if asked. We're always open to work with hardware manufacturers, but nVIDIA is not famous for being open to such cooperations I'm afraid.
  6. Fiery
    It's best if you leave the main window open and the Computer / Sensor page showing to make sure the readings are constantly updated/polled. If hiding the main window is a key requirement, then it's best to enable one of the External Applications modules to make sure the sensor readings are polled in the background.
  7. Fiery
    Thank you for your feedback
  8. Fiery
    We're already working on it The new WMI interface will be implemented in other AM4 and TR4 Asus motherboards as well, so hopefully soon all such motherboard owners will have a stable monitoring solution.
  9. Fiery
    That happens when the report creation process was interrupted, or when AIDA64 is not able to modify the previous SQL record in the Report table. Make sure to provide both write and modify (update) privileges to the SQL user that you use for report insertion.
  10. Fiery
    AIDA64 doesn't calculate or average the clocks over a period of time, but instead it detects the current CPU ratio (multiplier) at any given time point, and multiplies it with the current BCLK to get the CPU core clock. You can monitor the CPU clock for all CPU cores individually if you right-click on the bottom status bar of AIDA64 main window --> CPU Clock Monitor. You may need to enable status bar in AIDA64 / main menu / View first.
  11. Fiery
    We've done extensive test runs with Ryzen 1000 and Ryzen 2000 Series processors, and couldn't reproduce the issue Have you tried to use the latest AIDA64 beta build? https://www.aida64.com/downloads/latesta64xebeta Also, do you still have the MSI B350 Tomahawk motherboard and AMD Ryzen 5 1600 CPU? Do you have any nVIDIA video cards in your system?
  12. Fiery
    I just did. I apologize for the delays.
  13. Fiery
    Do you use DPI scaling (DPI zoom) for your monitor?
  14. Fiery
    I'm sorry for the late reply. We've already got a few topics about the same bug of the recent ForceWare drivers. The issue is not related to AIDA64 at all -- which can be considered a problem since we cannot fix it in our end. Downgrading ForceWare to 388.31 solved the issue:
  15. Fiery
    The issue seems like a collision between the manufacturer's own monitoring software and AIDA64. Have you tried to uninstall ASRock's own monitoring utility?
  16. Fiery
    We still believe the issue is with the video driver (ForceWare) and not AIDA64. Try to downgrade to an older ForceWare release, and check if it helps. I know you've mentioned that you've tried that path with no success, but maybe you've downgraded to a too recent version that already has the bug? For others 388.31 solved the issues:
  17. Fiery
    Thanks for the feedback
  18. Fiery
    Please let me know what motherboard, CPU and video card(s) do you have, and whether you're using the latest Windows 10 build (17134).
  19. Fiery
    Thank you for your feedback. The test is the same as before, it's only the amount of memory to be stressed that you can now adjust.
  20. Fiery
    We've implemented the requested Memory allocation % option in the Preferences of the AIDA64 System Stability Test. https://www.aida64.com/downloads/latesta64xebeta Let me know how it works
  21. Fiery
    Thank you, that's a very useful breakdown of the labelling issues. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works
  22. Fiery
    Thank you. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  23. Fiery
    I'm sorry, I messed up the info on the alphabetical order. It is sorted, but since the drives are numbered with indexes, those indexes override the model ID of each drive. So if we gloss over the 3 groups issue (since your system only has drives in the first group), the order is the order that is dictated by the physical order of drives, as they are connected to their respective drive controllers, as well as the order of controllers. Since Windows may or may not enumerate drive controllers in the same order as AIDA64, only the order of drives connected to a particular drive controller should match between AIDA64 and Windows. Renaming of labels is available in OSD Panel, Desktop Gadget, SensorPanel, and external LCD modules.
  24. Fiery
    We've tried to reproduce the issue on our own Ryzen test systems, but with no luck. Please do the following: 1) Before sleep, when benchmark scores are normal (lower), please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR 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. 2) After waking from sleep, when benchmark scores are higher, please create a second CPUID & MSR Dump, and copy-paste the full results into this topic, or attach the results as a TXT file to your post. For those test runs, make sure to use the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta Thanks, Fiery
  25. Fiery
    I'm afraid on some Asus motherboards the activity that AIDA64 needs to communicate with the EC (Embedded Controller) causes latency spikes. So far we haven't been able to solve the issue on our end So if you want to avoid the sound glitches, you need to disable EC support in AIDA64.
×
×
  • Create New...