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
    The new AIDA64 beta build is available for download at: https://www.aida64.com/downloads/latesta64xebeta
  2. Fiery
    We'll work on it soon. First we need to roll out a new stable update to AIDA64
  3. Fiery
    Thank you all for your comments. I'd like to ask you all to right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus 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. We need that dump in order to filter out the affected video cards from the nVIDIA SMBus scanning module. This is the first step we can take to get to the bottom of the issue.
  4. Fiery
    Yes, I think that will solve it.
  5. Fiery
    Thank you for your feedback
  6. Fiery
    Thank you. For me it looks as if the Aquaero monitoring module causes the latency issues. Can you please try to disable the Aquaero module and check if it makes it any better? You can do that by right-clicking on the bottom status bar of AIDA64 main window --> HWMon Modules --> Aquaero/b]. You may need to enable status bar in AIDA64 / main menu / View first.
  7. Fiery
    Thank you. I think the issue is that for some reason your Optane drive is part of a NVMe RAID array, and that makes the Computer / Summary page list only the RAID array device and not the individual drives that are part of the RAID array. With RAID arrays the individual drives (the RAID array members) are only listed on the Storage / ATA and Storage / SMART pages.
  8. Fiery
    Thank you. The problem is that due to the way drives are enumerated, AIDA64 needs to sort the list in an alphabetical order (although it's a bit more complicated than that, but let's gloss over the non-important part here). That makes your Evo drive appear in the list first. The alphabetical order is necessary for AIDA64 to properly filter out redundant entries in the list of drives.
  9. Fiery
    Thank you for your test runs and detailed feedback, it's very helpful.
  10. Fiery
    Thank you for your report. Let me know what exactly happens when you try to open the Preferences. Does the main window simply become unresponsive? Or first the Preferences window appears?
  11. Fiery
    Let me know what app do you have on your screenshot. Also let me know if your device is rooted or not. Thanks, Fiery
  12. Fiery
    We've just checked it on a Pixel 2 device running the latest Oreo update (8.1.0), and it works fine. Are you using the latest AIDA64 build of 1.50, downloaded from the Play Store?
  13. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART 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 --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  14. Fiery
    The ordering is determined by the order in the list of physical drives. If you're unsure about why the ordering works the way it is on your system, please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Based on that dump we can provide you further details on the order of your SSDs. Thanks, Fiery
  15. Fiery
    Is your PC overclocked or otherwise specially tuned?
  16. Fiery
    Please note that it's not possible to diagnose such issues remotely. You may want to take your phone to a local specialist and have it checked out.
  17. Fiery
    1) You don't need to deactivate your license. Just take the PKEY.TXT file that holds your license information, back it up and restore it on your new system/SSD. You can also transfer your existing AIDA64 settings (incl. your LCD layout) by backing up the file called AIDA64.INI. You can find both files in your AIDA64 installation folder. 2) The USB display you've mentioned seems to work as a regular USB-connected monitor, so you can expand your Windows Desktop onto it. Hence you won't need to use the External LCD module of AIDA64, but instead the SensorPanel. You will need to migrate your LCD settings to SensorPanel. Let me know if you need assistance doing so.
  18. Fiery
    Thank you. Please note that Vcache voltage readout is only supported from BIOS version 1201.
  19. Fiery
    How much system RAM you've got? 32GB? 64GB? A lot rides on that, since it takes quite some time for Win10 to allocate big chunks of RAM. Windows, going from WinXP through Win7 through Win8 to Win10 tends to get slower and slower when it comes to allocating huge memory blocks. But, you may have a point there: we may need to add a new option in the System Stability Test Preferences to let you lower the default 95% memory allocation to 90% or 80%.
  20. Fiery
    The BIOS (at least on Maximus X Formula) uses a formula of x 24 / 1000 to get to L/M, but I don't think that that formula is correct. Unless we can come up with a proper formula that yields to values that make sense, I'd be hesitant to convert the raw RPM reading to anything else...
  21. Fiery
    It's cool then Please let me know what subtests do you have enabled in the System Stability Test when the "jumping" occurs. If you have the memory stress test enabled, please check it without it, and let me know if it makes a difference. If it does, let me know how much system RAM do you have installed, and whether you're running the latest Windows 10 stable build (of 16299) or an Insider Preview build.
  22. Fiery
    Thank you. I think the issue occurs because you didn't enclose the report file name with quotes (" characters) in order to mitigate the potential space characters that appears in the filenames after %dirname% is resolved. Do you think that it may explain the issues?
  23. Fiery
    Based on your experiences with your Rampage VI Extreme motherboard, what do you reckon the proper conversion formula from RPM to LPH would be?
  24. Fiery
    Have you tried it with the latest AIDA64 beta as well? https://www.aida64.com/downloads/latesta64xebeta I'm just asking because we've recently applied a workaround to mitigate the issue you've described.
  25. Fiery
    Thank you for your feedback. I don't think that that formula applies to this particular case. Asus seems to use a simpler formula of x 24 / 1000 to convert the raw RPM readings into LPM (L/M). The AIDA64 sensor module uses a fixed measurement unit of LPH (L/H) on the flow sensor readings, so we need to come up with a proper formula to convert the RPM value of Water Flow on your motherboard into the LPH reading that can be squeezed into the AIDA64 sensor module as a secondary measurement for the same reading for your motherboard.
×
×
  • Create New...