Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11334

  • Joined

  • Last visited

  • Days Won

    476

 Content Type 

Everything posted by Fiery

  1. Fiery
    Thank you. We've already come across the same issue about the EC register readout causing latency spikes. But sadly, so far we haven't found a solution to this We'll keep looking into this.
  2. Fiery
    Thank you. It seems to be due to a motherboard BIOS bug about handling the MMIO (memory-mapped I/O) portion of the motherboard sensor chip (IT8655E). Please report the issue to Asus, I'm sure they will know how to fix it in an upcoming BIOS update for your motherboard.
  3. Fiery
    Thank you for the feedback
  4. Fiery
    It's not that difficult to rename any of the readings, but it involves allocating newer and newer sensor slots. New sensor slots mean the whole monitoring module gets bigger and slower (by a tiny bit) everytime we add more, so we gotta be careful not to carelessly add everything that Asus comes up with Watercooling section doesn't make much sense, since that's not how the sensor readings are grouped on the Sensor page anyway. When you have a dedicated liquid flow meter (Aquaero, T-Balancer, etc), it will be slotted into the Flow Sensors group though.
  5. Fiery
    Since only the base frequency is guaranteed, indicating the turbo frequency would be less relevant IMHO. Not to mention the fact that modern processors have different turbo frequencies defined for different workloads (e.g. AVX-512 turbo is different to SSE turbo, etc). Only the base frequency is somewhat constant as a single MHz value. Our benchmarks do not enable or disable Turbo Boost, so the benchmarks are performed at whatever frequency the CPU chooses to operate on. Most of our benchmarks complete in 10 seconds, but we're planning to implement some sort of long-haul benchmarks in the future in order to better measure the long-term performance you can expect from such low-TDP parts that turbo like crazy in the short run Exactly as the graph from the TechSpot article shows.
  6. Fiery
    Probably the secondary temperature shows a diode that is placed close to the SSD controller chip, while the first diode is placed far from it. In which case the first temperature would be considered or better labelled as "enclosure temperature"; while the second temperature should rather be called "SSD controller chip temperature" for example.
  7. Fiery
    AIDA64 v1.50 is a very old version. Make sure to use the latest version of 5.95: https://www.aida64.com/downloads/latesta64xe Let me know if the problem persists.
  8. Fiery
    Please note that AIDA64 (for Windows PCs) is already localized to Spanish. Our Android mobile app (AIDA64 for Android) is also localized to Spanish. Regards, Fiery
  9. Fiery
    DIMM slot numbering is quite tricky with Skylake-X processors, and we haven't yet found a way to properly reorganize the DIMM slots to suit all motherboard layouts. Water In and Water Out temperatures do not have a dedicated temperature slot in the hardware monitoring module of AIDA64. That's why they use a generic temperature label. Asus uses a lot of different sensor labels on its ROG products. And that single motherboard vendor alone bloats up our list of dedicated sensor slots quite a lot BTW, when you have both T Sensor 1 and Water In thermal readings available, the first one would appear as Temperature #1, and the second one would appear as Temperature #2. They wouldn't use the same generic temperature slot, so it wouldn't overwrite each other at all. When a water flow reading is available through a fan slot, RPM is the measurement unit that AIDA64 would use. You can use the Correction facility (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction) to convert the readings to a different format, but that wouldn't change the displayed measurement unit at all. Happy New Year!
  10. Fiery
    That's normal. Some Asetek based liquid coolers require manual fan setting in AIDA64 Preferences in order to work properly.
  11. Fiery
    SPP (System Platform Processor) is the north bridge component of nVIDIA chipsets. MCP (Media & Communications Processor) is the south bridge component of nVIDIA chipsets.
  12. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling 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
  13. Fiery
    It's a really cool panel, great job! The only issue I could spot is "CPU TEMERATURES", that misses a "P"
  14. Fiery
    Thank you We'll order an iCX capable EVGA video card in early January to help us diagnose this. Something really weird is going on about iCX: in the registers dump everything looks great, but when AIDA64 tries to read individual registers (just the ones that are necessary for measuring iCX temperatures and fan RPMs), those registers do not seem to return proper values. We've never seen such anomaly about nVIDIA I2C sensor devices...
  15. Fiery
    Does the 2nd temperature readout ever change? If not, then it indicates the maximum temperature the SSD could operate at, or the maximum temperature the SSD ever reached.
  16. Fiery
    Thank you. Please also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  17. Fiery
    We don't have such a field in our database, but we can add it as soon as we come across such a display. If you submit data on such a display, make sure to indicate that it's a multitouch one.
  18. Fiery
    We'll check it soon. Meanwhile, please try to download AIDA64 Engineer, and use the following command-line to start it: AIDA64.EXE /STARTUPLOG It should create a log file on your Windows Desktop. Please attach the file to a forum post here in this topic, so we can check where exactly the startup process breaks down.
  19. Fiery
    I guess START.EXE interprets the line incorrectly, so you may need to get rid of the quotation mark characters inside the AIDA64 command-line, and close the whole thing into a single pair of quotation marks, like this: Start "\\nas\test\Script\Development\AIDA64-JH\AIDA64\Aida64.exe /CUSTOM \\nas\test\Script\Development\AIDA64-JH\fulrep.rpf /LANGEN /R \\Directory\specs\Logs_PCd_Burn\%serial%\%serial% /XML" Of course if you do this, make sure to not have any space characters anywhere in the AIDA64 command-line.
  20. Fiery
    Thank you for your feedback
  21. Fiery
    To me it seems there's a missing quotation mark (" character) there, before /XML. A fixed command-line would look like this: "\\Directory\Directory\Directory\Directory\AIDA64-JH\AIDA64\Aida64.exe" /CUSTOM \\nas\test\Script\Development\AIDA64-JH\fulrep.rpf /LANGEN /R "\\Directory\Directory\Directory\R90KLBTM\R90KLBTM" /XML
  22. Fiery
    Thank you for your feedback
  23. Fiery
    Who says that? AIDA64?
  24. Fiery
    If you set the Environment variable serial to the right value, you can use it in your command-line as you've proposed (%serial%).
  25. Fiery
    Just post them here in case you cannot find the panel type for the displays on the Monitor page of AIDA64. The same screen shot than what you've posted above would work great in those cases as well, although a copy-paste of the textual information would be even better
×
×
  • Create New...