Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12179

  • Joined

  • Last visited

  • Days Won

    536

 Content Type 

Everything posted by Fiery

  1. Fiery
    We've added the missing bits & pieces in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
  2. Fiery
    Can you please check if the process priority settings are properly set while you're running the stability test? The main process (AIDA64.EXE) should be using Normal priority class, while the SST process (AIDA_BENCH64.DLL or AIDA_BENCH32.DLL) should use Below Normal priority.
  3. Fiery
    AIDA64 currently doesn't support command-line based automated benchmarking. If you're interested in having that feature enabled, please send me a private message about the details on your envisioned project and the number of AIDA64 licenses you have (or you're about to) acquire to complete the task. Thanks, Fiery
  4. Fiery
    If the drive has a very smart controller that desperately tries to hide the fact that the capacity is less than the advertised value, then for a while the Random Write + Verify test may not report any issues. Especially when the performance is that freakishly low With such an underperforming drive you would have to let the Random Write + Verify test run for at least 2 days to draw any meaningful conclusion. Good old fraudulent pendrives which perform adequatly (like 20-30 MB/s) are usually caught by the test in a matter of minutes, sometimes few seconds only. But it's always best to let the Linear Write + Verify test to complete to 100%, since that's the only sure way of knowing that the drive can be filled 100% with data, and all data is fully retained (stored) by the drive.
  5. Fiery
    I'd simply return the device and ask for a full refund due to a suspected fraud. I wouldn't try to fix the drive at all. Even if you could format it to its "right" capacity, the performance would still be abysmal.
  6. Fiery
    AIDA64 uses standard SMBus SPD commands to communicate with DIMM thermal sensors. There's no alternative way I'm afraid. And we sadly have absolutely no insight into how AI Suite works exactly about SMBus communication, and what and how Asus updated on the way it interacts with SMBus devices between AI Suite II and AI Suite 3 releases. Your new motherboard may simply have a SMBus based devices that AI Suite 3 now polls, and your old motherboard had no such device, so AI Suite II needed not to use its SMBus layer at all.
  7. Fiery
    You can switch off (hide) individual graph lines by removing the tick from their respective checkbox
  8. Fiery
    We've checked, and the high disk traffic is caused by the Logitech LCD API that AIDA64 uses to display sensor values on your G19 keyboard LCD. As you can see on your screen shot, LCore.exe (Logitech LCD Core) also shows the same anomaly. Make sure to ask Logitech about this, since only they can fix this in their LCD API. Thanks, Fiery
  9. Fiery
    Thank you. You're still using the latest AIDA64 stable version. But since your motherboard was released to the market recently, it's not supported by that AIDA64 version. You may need to manually upgrade to the latest AIDA64 Extreme beta build available for download at: https://www.aida64.com/downloads/latesta64xebeta Just download the ZIP package and extract all its content into the existing installation folder of AIDA64. Let it overwrite any existing files. Your previous settings and entered license will be retained. After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Alternatively, you can try to perform the automatic update again. Just make sure to enable updating to beta versions first, in AIDA64 / main menu / File / Preferences / General (the option is near the bottom of that page).
  10. Fiery
    I understand that the issue doesn't affect the older betas, but it would still be important to know whether you changed or updated any hardware in your system recently. In the past few beta updates we've been working hard on adding support for all the new Z270, H270, Q270 and B250 motherboards out there, as well as the upcoming AM4 motherboards. Maybe you've got a new Z270 motherboard recently which works fine with the older betas but not with the newer ones? Also, we've revamped the way AIDA64 handles DDR4 SPD on Haswell-E and Broadwell-E processors. So if your memory modules have DIMM TS (thermal sensing) capabilities, it may be worth trying to disable DIMM thermal sensor support in AIDA64 / main menu / File / Preferences / Stability, and see if it helps. You need to restart AIDA64 after altering that option.
  11. Fiery
    I guess either the AIDA64.EXE process or the SST/benchmark process (AIDA_BENCH64.DLL or AIDA_BENCH32.DLL) may get started with a sub-optimal priority setting through the Task Scheduler. The main process that also updates the SST interface (AIDA64.EXE) has to have a higher priority setting than the SST process. By default the main process uses the Normal priority level, and the SST process uses the Below Normal priority level. However, if for some reason they use the same priority level or the SST process uses a higher priority level than the main process, then the SST interface update will not get enough CPU cycles from the Windows kernel scheduler, which will make the SST interface jerky/lagging. Regards, Fiery
  12. Fiery
    Even if you have a 500 millisec or 100 millisec update rate, the clock will not go crazy. It will however not skip a second, so it will look smoother than with a 1 sec update rate. CL: Great to hear, thank you!
  13. Fiery
    You can get the informational blue box back on your tablet if you have the RemoteSensor feature enabled, but you hide all items in your layout. You don't have to remove those items, just select them all and press the Hide button to hide them. As soon as you get the blue box, you can unhide all items again, and continue tweaking your layout.
  14. Fiery
    Linear Write + Verify shouldn't take days to complete, as long as the drive performs at least as good as an average USB 2.0 pendrive. Even if the drive can do only 25 MB/s, filling the drive and verifying it would take "only" 23 hours. In case the drive performs considerably worse than that, that fact alone would make one suspicious about authenticity of the pendrive... BTW, a true USB 3.0 pendrive would do at least 100 MB/s, and so it would complete the Linear Write + Verify test in 6 hours (considering it's a 1TB capacity drive).
  15. Fiery
    If you use the automatic update feature, then that alone would explain the 783 MB write in a year. Since it first downloads the update package, then extracts the files. So at every update it writes cca. 120 MB on the disk right now. It was less than that before we've implemented DPI scaling though. Also, if you use the Logging facility or the disk write benchmark, those could write gigabytes on the disk very quickly Regards, Fiery
  16. Fiery
    Are you sure Corsair Link software has no background service that would keep monitoring your RAM modules and control their LEDs, even when the main application is closed? We've seen such issues with several other software, the prime example is of course Asus AI Suite
  17. Fiery
    Such 2-second steps are absolutely normal. The way it works is that for example when you have a 1 second update frequency set, the sensor values are updated in a 1 second step. But, that 1 second delay starts when the previous sensor polling is done. So when the polling itself takes more than zero seconds, the actual update rate will be longer than 1 second. When the polling of all sensor values take e.g. 600 milliseconds, the effective update rate will be 1600 milliseconds or 1.6 sec. The solution to that pecularity is to lower the update frequency to e.g. 500 miliseconds.
  18. Fiery
    Did you configure the resolution that was indicated by RemoteSensor in a blue box on your Android tablet? It may or may not be 800x1280 pixels, but smaller. On our 8-inch 800x1280 resolution Android tablet (Asus MeMO Pad 8) the right resolution to have configured is 980x1292. We've also checked the font size issue, and 72 seemed quite large already. However, in order for you to have more flexibility, we'll unlock setting the font size to even larger values in the next AIDA64 beta update due next week
  19. Fiery
    There could be 2 reasons behind that. Either your RAM modules fail to provide a stable and accurate reading sometimes; or there's a SMBus access collision between another software and AIDA64. Do you have any other software installed that may also poll the SMBus?
  20. Fiery
    Maybe it's the sensor thread that freezes. Did you change anything in your computer recently? I mean like a hardware replacement, hardware upgrade? Can you please check what happens if you leave the Computer / Sensor page open for a few minutes? Or if you leave the System Stability Test window open for a few minutes, without starting any stress tests?
  21. 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. Thanks, Fiery
  22. Fiery
    I've sent you a private message about this, responding to your private message
  23. Fiery
    IMHO having a single status is fine. If any of the disks fail, the status will show "FAIL", and then you can dig deeper by navigating to the mentioned Storage / SMART page. Yes, the SMART status should be available fro M.2 SSDs and NVMe SSDs as well. However, please note that not all SSD controllers are supported, so your particular SSD may need further adjustments/tweaking.
  24. Fiery
    We've already added a disk health sub-window to the Storage / SMART page
  25. Fiery
    When you have that done, please drop me a private message. We're not skilled with Labview, so any direct source code that is Delphi, C, Visual Basic (etc) -- tested to be working under Windows -- would be extremely helpful to have.
×
×
  • Create New...