Jump to content

Fiery

Administrators
  • Posts

    12639
  • Joined

  • Last visited

  • Days Won

    569

Posts posted by Fiery

  1. Thank you.  It seems your motherboard has a few tricks up its sleeves :)  The CPU Vcore seems to be influenced by the onboard CHL8326 VRM controller.  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.

     

    Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full).  Copy-paste the full results into this topic.

     

     

    Thanks,

    Fiery

  2. I'm sorry to hear about your issues and see that you're getting frustrated :(  Please try to give it a bit more tries, it really should work.

     

    If there's no AIDA64.INI file in the AIDA64 installation folder, then a default layout of AIDA64.INI file is created when you perform step #3.  If the file isn't created, then AIDA64 may not have the necessary rights to write a file in your AIDA64 installation folder.  Make sure to have administrator privileges, you need that to use AIDA64 low-level hardware features like sensors monitoring.

     

    Also, you can try moving AIDA64 files to C:\AIDA64 folder, it could make it easier to handle file permissions.

  3. In other Sabertooth Z87 logs the PCI-E #1 and PCI-E #2 temperatures are listed as "PCIE-1" and "PCIE-2".  Are you sure you haven't renamed those? :)  Or maybe between two BIOS updates Asus changed those labels?

     

    BTW, when it comes to sensor-related issues, AI Suite II = AI Suite III  ;)

  4. Thank you.  We've fixed the Chassis Fan #4 reading.  Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at:

     

    http://www.aida64.com/downloads/aida64extremebuild2522cfs6y7mpqjzip

     

    After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

     

    Let me know how it works.

     

    As for the temperatures, on your system AIDA64 gets confused, because you've got Asus AI Suite II installed, and -- I suppose -- you've renamed the temperature labels in it.  When AI Suite II is installed, AIDA64 doesn't use its low-level EC sensor functions, and relies on AI Suite II calls to gather sensor information.  And that only works properly as long as you use the default labels.  You can revert back to the default labels, or uninstall AI Suite II to make all temperatures appear properly in AIDA64.

  5. 1) Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> Battery Dump.  Copy-paste the full results into this topic.

     

    2) Then go to the Computer / Sensor page of AIDA64, and copy-paste the full page into this topic, using either the right-click menu on the Sensor page, or post a screen shot of the page.

     

    Make sure to have the battery charging (so connected to A/C power, and the battery being not fully charged) when you make those tests.

     


    Thanks,

    Fiery

  6. 1) 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.

     

    2) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full).  Copy-paste the full results into this topic.

     

    3) Finally, right-click on the bottom status bar of AIDA64 main window --> System Debug --> Asus SPD Dump.  Copy-paste the full results into this topic.

     

    Before running the 3rd test, please make sure to save your documents and close any applications you may have open, because there's a slim chance that it might cause a system lockup or BSoD.

     


    Thanks,

    Fiery
     

  7. That's because even when AI Suite II is installed, AIDA64 can still read the sensor values that are measured by the onboard Nuvoton sensor chip, but not the ones measured by the Embedded Controller.  When AIDA64 (or any other software for that matter) reads Embedded Controller registers while AI Suite II is also installed, a collision may occur that could cause system lockup or BSoD.  We -- and a few AIDA64 users as well -- have already contacted Asus and asked them to fix AI Suite II to make it synchronized with other monitoring software (like AIDA64, HWMonitor, HWiNFO, SpeedFan, SIV, etc), but they refuse to cooperate with anybody :(  Hence we had to implement the workaround to go through AI Suite II driver calls to get sensor readings -- but as you can see, it only works when the sensor labels aren't renamed.
     

  8. We've checked the Multi-Media Commands - 6 (MMC-6) specifications, but it seems M-Disc support cannot be detected using MMC or any other methods.  So what we've done is extended the optical drives database to cover M-Disc support as well.  We've added the drives listed on mdisc.com, and also a few other LG models.  The improved optical drives database will be rolled out in the next AIDA64 beta release due in a few days.

     


    Regards,

    Fiery

     

  9. I've got an Asus Sabertooth Z87 motherboard

     

    This beta update adds various temps that were unavailable before. Nice :D

    But there are still some issues:

    • Chassis fan #4 is incorrectly identified as a CPU OPT fan (i do not have a CPU OPT fan)
    • Several temperatures are still missing (the sabertooth series has a decent amount of these)

    See attached screenshot

    Sidenote: AdaptecRaid5805 = T_Sensor1

     

    1) 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.

    2) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic.

     

    Thanks,

    Fiery

     

  10. 1) On your system AIDA64 gets confused, because you've got Asus AI Suite II installed, and -- I suppose -- you've renamed the fan labels in it.  When AI Suite II is installed, AIDA64 doesn't use its low-level EC sensor functions, and relies on AI Suite II calls to gather sensor information.  And that only works properly as long as you use the default labels.  You can revert back to the default labels, or uninstall AI Suite II to make the fans appear properly in AIDA64.

     

    2) Minimum, maximum and average sensor readings are available in the System Stability Test (main menu / AIDA64 / Tools / System Stability Test).  You can use the Clear button there to reset the values.



    Regards,

    Fiery


     

  11. I just had another chat with the support over at Mad Catz/Cyborg Gaming, and I got bad news, they dont have any plans to release a SDK for this keyboard. I was told in December 2012 that they would release the SDK in early 2013, and now they dont have any plans for it, pretty bad move from them if you ask me.

     

    Anyone considering to buy this keyboard to use with Aida64, dont buy it, there are other keyboards with support for Aida64.

    That's bad news, but thank you for letting us know about their decision.

  12. Thank you for the feedback.  As I wrote above...

     

    "But please note that the core temperatures are measured via the on-die temperature diode of your processor.  And most FM1, FM2 and AM3+ socket based AMD processors feature a hardware issue in their temperature diodes that yields to very low temperature readouts at idle -- usually way below ambient (room) temperature.  The measured core temperatures only make sense when the CPU is under load"

     

    ... core temperatures are independent from motherboard sensor calibration, and the issue you experience cannot be fixed from software, since it's a hardware issue.

×
×
  • Create New...