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
    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.
  2. 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?
  3. Fiery
    I just did. I apologize for the delays.
  4. Fiery
    Do you use DPI scaling (DPI zoom) for your monitor?
  5. 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:
  6. 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?
  7. 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:
  8. Fiery
    Thanks for the feedback
  9. 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).
  10. 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.
  11. 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
  12. 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
  13. 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.
  14. 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.
  15. 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
  16. 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.
  17. Fiery
    Thank you for the dumps. To me it looks like as if some of the GPUs in your system simply went to sleep after a while, due to lack of activity or load. Have you tried to disable ULPS?
  18. Fiery
    Thank you for the details. We suspect it can be due to the video driver, so if it's possible, please try to downgrade ForceWare, to a late-2017 WHQL release, 388.31 for example. Let me know if it makes a difference. If not, please post a screen shot showing the error message that comes up when AIDA64 crashes.
  19. Fiery
    We suspect it can be due to the video driver, so I'd try to downgrade ForceWare, to a late-2017 WHQL release, 388.31 for example.
  20. Fiery
    I don't think so
  21. Fiery
    What Windows version+build are you using?
  22. Fiery
    You have too much free time
  23. Fiery
    Exactly
  24. Fiery
    Very strange. We've tried, but were enable to reproduce the issue with our SQL databases. Can you please check what happens if you purge your database (with either AIDA64 Database Manager or using a custom SQL query), and insert the report files to your database using the AIDA64 Database Manager?
  25. Fiery
    Please avoid posting a single issue into multiple topics. I've replied you in your other topic.
×
×
  • Create New...