Jump to content

Fiery

Administrators
  • Posts

    12558
  • Joined

  • Last visited

  • Days Won

    562

Posts posted by Fiery

  1. Confirmed, happens if sensor page is left open when AID64 is minimized to taskcbar.

     

    It only started to occur after installing the latest 13.6 AMD drivers, It may help you to know the latest 13.6 set require an updated VC runtime (included with package).

    capturedsc.png

     

    Since the exception seems to be related to NTDLL.DLL, we've added stronger exception handling for every calls in AIDA64 that uses NTDLL.DLL.  It will be implemented in the next AIDA64 stable release due tomorrow ;)

  2. Please note that when you install an IPMI driver, the sensor readings should appear on the Computer / IPMI page in AIDA64.

     

    If you ask a technical person at Asus, please try to find out what methods are necessary to perform to read fan speeds (RPM) on your motherboard from a 3rd party software.  As far as we can tell, none of the known methods apply to your motherboard, so it's quite a special piece of kit ;)  Usually there are 5 different ways to acquire sensor readings:

     

    1) ISA port I/O

    2) SMBus

    3) Embedded Controller

    4) IPMI Sensor

    5) ACPI query

     

    Some motherboards use just a single method, while on others one needs to combine multiple methods to read all sensor readings.  If Asus tech.support could tell us which method to use, and which registers belong to the fan speeds, then we can implement that in AIDA64 to let you measure fan speeds in AIDA64.  However, based on our previous experiences with Asus, I doubt they would reveal their "cards" about this or any other Asus motherboards :(  Asus tends to use proprietary methods about sensors, and they almost never publish any technical details on what they do and how they do it.

  3. Any news?

     

    We've tried to replicate the issue on our test systems, but with no luck.  Can you please post a RAID Dump and a SMART Dump using the latest AIDA64 beta?

     

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

     

    Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> RAID Dump.  Copy-paste the full results into this topic.

     

    Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump.  Copy-paste the full results into this topic.

     

    Thanks,

    Fiery

  4. Switching the mux is slow and readings tend to be unreliable.  For example, you switch to CPU Fan2, then you have to wait 3 or 4 seconds (which is unacceptably long), and even after then sometimes the reading comes from CPU Fan1 -- and in such case there's no way to know which fan do you get the readings from.

  5. On several ASRock boards 2 fans are muxed a single fan connector (fan header).  Since the mux is implemented improperly, AIDA64 cannot switch them.  Try to connect the fan to another fan header, and it will then show up in AIDA64 ;)

     

    BTW, on your particular motherboard CPU Fan1 and CPU Fan2 are muxed together, so you have to use the other connector to make sure it appears in AIDA64.


    Regards,

    Fiery

  6. Such 0-byte long tables are usually there because of either a BIOS bug, or because of a disabled ACPI table (e.g. HPET).  The memory address matching with other tables could just be a coincidence.

  7. AFAIK the VRM chip on your video card is only responsible for providing voltage for the GPU itself, and not for other components of your video card, e.g. the memory chips. Plus, as you mentioned, it may only account for the power flowing through the +12V PCIe power connector(s), and not include the power drawn from the PCIe slot.  But all those things heavily depend on the actual video card design, and the type of VRM used.

     


    Regards,

    Fiery

  8. First, try to do the following:

     

    1) Close AIDA64

     

    2) Go to AIDA64 installation folder, and delete the following files:

     

    AIDA_CPUID.DLL

    AIDA_ICONS7.DLL

    AIDA_ICONSXP.DLL

    AIDA_UIRES.DLL

     

    3) Manually download the latest beta ZIP package from:

     

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

    Extract the ZIP into the AIDA64 installation folder.  Let it overwrite any existing files.

     

    4) Restart Windows, and start AIDA64

     

    -------

     

    If the above steps do not resolve the icons issue, then do the following to revert back to AIDA64 v2.85 stable:

     

    1) Close AIDA64


    2) Manually download the v2.85 stable ZIP package from:


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


    Extract the ZIP into the AIDA64 installation folder.  Let it overwrite any existing files.


    3) Restart Windows, and start AIDA64

     

    Please note that by extracting the ZIP package and overwriting existing files will keep your Preferences settings.  If you want to specifically backup AIDA64 settings, just backup the AIDA64.INI file from the AIDA64 installation folder.



    Regards,

    Fiery

  9. Just reporting a minor issue with my AIDA64 Extreme v2.85.

    Occasionally I get a popup message that says:

     

     

    Everything seems to be running fine otherwise.

    The program runs at startup and I have the sensor panel shown too.

     

    Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:

     

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

     

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

     

    Let me know if it helps.

     

    Thanks,

    Fiery

×
×
  • Create New...