Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12569

  • Joined

  • Last visited

  • Days Won

    563

 Content Type 

Everything posted by Fiery

  1. 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
  2. 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
  3. 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.
  4. 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
  5. 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?
  6. 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?
  7. 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
  8. Fiery
    I've sent you a private message about this, responding to your private message
  9. 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.
  10. Fiery
    We've already added a disk health sub-window to the Storage / SMART page
  11. 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.
  12. Fiery
    Yes, we're working on it. It may be a bit difficult to implement support for that hardware without having a sample hardware at hand, but we'll do our best.
  13. 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
  14. Fiery
    One day we'll get to joining the other hardware monitoring modules with the Sensor page, and use just a single module. That will simplify everything, and also will make it possible for you to rename or rearrange the readings on the Sensor page.
  15. Fiery
    No, renaming is not simple at all. The main issue is that the Sensor page is not linked directly with the other hardware monitoring modules (e.g. OSD Panel, SensorPanel, External LCD, etc). Hence what you can do with all the other hardware monitoring modules, you cannot do to the Sensor page. But, you can switch to using the SensorPanel or OSD Panel anytime And with those you can rename and shuffle the readings any way you want.
  16. Fiery
    Well... It was a very stupid mistake. I was lazy to properly assemble a PC, and left the SSD on top of a HDD. I thought after installing the OS and drivers, I'll remove the HDD and install the SSD in its drive bay. The two device heating themselves up ended up in a disaster, even though it was only for a few hours...
  17. Fiery
    Thank you for your feedback
  18. Fiery
    Thank you, we'll add VCCST (VCC Sustain) voltage to the next AIDA64 beta
  19. Fiery
    Once I've had a SSD heating up over 100 Celsius, and that killed it. Not immmediately, but shortly it just died. I'd definitely get Corsair's take on the subject. If they fail to respond in a few days, then I'd get a refund and look elsewhere.
  20. Fiery
    Can you see the missing set of voltages in the UEFI Setup or in ASRock's own monitoring software? As for the PCH temperature, we will add it in the next AIDA64 beta update due next week. We will also check how to detect the chassis intrusion state.
  21. Fiery
    Amazon sells illegal (pirate) AIDA64 license keys. We've already notified them about this, and they said they're investigating the fraud. If you bought a license at Amazon, make sure to ask for a refund ASAP.
  22. Fiery
    On the SensorPanel and also LCD devices, you can enter "Mbps" into the unit field to make it the measurement unit. Let me know if you meant a different place in AIDA64. In which case please let us know on what page or in which module do you see the MB/s measurement unit. Regards, Fiery
  23. Fiery
    I suppose Corsair's own SSD software doesn't support NVMe drives yet. Hopefully in a few weeks they can get that done, along with a new firmware for the MP500 family. As for the operating temperature, I suppose they mean ambient temperature there. If not, and it's actually the operating temperature range of the MP500, then the drive may be working out of spec under heavy stress/load... According to our test runs, the MP500 heats up to 70+ Celsius when there's a heavy flow of outgoing data (ie. copying a lot of large files to the drive).
  24. Fiery
    Thank you. Please 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. Let me know if it helps
  25. Fiery
    The mentioned new AIDA64 beta update is now available for download at: https://www.aida64.com/downloads/latesta64xebeta
×
×
  • Create New...