Jump to content

Fiery

Administrators
  • Posts

    11186
  • Joined

  • Last visited

  • Days Won

    475

Posts posted by Fiery

  1. Cooling Fans:

    CPU 1771 RPM

    Chassis #1 954 RPM

    Chassis #2 860 RPM

    Power Supply 1611 RPM

    Thank you for the data. However, I can see 4 motherboard-connected fans monitored there, just like in the ATKEX dump above:

    ------[ Asus ATKEX ]------

    Chassis fan 1: 986 RPM

    Chassis fan 2: 870 RPM

    CPU fan OPT : 0 RPM

    CPU fan : 1755 RPM

    Power fan 1 : 1097 RPM

    It means AIDA64 already shows all 4 spinning fans that Asus AI Suite can monitor. Please check if your BIOS Setup shows the same 4 fans as well or not.

  2. I have a similiar motherboard. ASUS P8Z68-V Pro GEN 3.

    I updated to the latest beta but there are still some sensors missing.

    Power fan 1 (Has fan connected)

    I think there is an Power fan 2 as well.

    /Urban

    Power Fan 2 doesn't seem to be monitored by Asus AI Suite, so I guess it's not monitored by your motherboard at all.

    Thanks for the dump. Please also copy-paste the AIDA64 Computer / Sensor page content here, so we could compare the current readings against Asus AI Suite readings.

  3. If you have contacts at Asus, try to convince them to work with us ;) Otherwise, without the necessary documentation it would be quite risky to access modern EPU and ROG chips, just by guessing register indexes and stuff :(

  4. We've updated the temperature labels. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at:

    http://www.aida64.co...64cxyfsvqwmnzip

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

    Let me know how it works now ;)

    As for the CPU Package vs. Core#3 temperature, they are measured very differently, but they are both provided by the CPU itself using its on-die temperature diodes. So the explanation of the matching lies deep in your CPU ;) Probably Intel simply uses the Core#3 temperature reading to report CPU Package temperature.

  5. As djmorgan stated, you don't have to have administrator or any other special privileges to let AIDA64 start at Windows bootup. You however need to make sure you don't have any 3rd party security solutions installed that may prevent AIDA64 from registering it in Win7 Scheduled Tasks to launch at Windows bootup.

    Regards,

    Fiery

  6. AIDA64 already supports older EPU capable motherboards (ie. it measures CPU power draw). We've requested Asus to provide us the necessary information to read more values from Asus EPU and ROG chips in AIDA64, but they refused to work with us on that. They simply want to protect their unique hardware and software features to make sure they can keep their technological "edge" over their competitors.

    Regards,

    Fiery

  7. PCH, OPT1, OPT2 and OPT3 temperatures could be measured via a bank switching in the Embedded Controller. It is however a risky method that may cause serious conflicts (collision) with Asus' own software (AI Suite 2) or even the BIOS. An Embedded Controller collision may cause a system lockup or voltage spikes that may harm the CPU, PCH or memory modules. In AIDA64 we simply cannot risk that :( So I'm afraid those temperatures will not be measured in AIDA64.

    Regards,

    Fiery

  8. AIDA64 Extreme Edition is not capable of producing reports automatically, since it lacks of command-line or other sorts of automation. You'll need to purchase AIDA64 Business Edition to let you automatically collect reports of a whole network, put an audit together, and analyze an audit snapshot, or find changes between audit snapshots.

    Regards,

    Fiery

  9. I'm afraid AIDA64 may not be useful for such a specific purpose :(

    1) AIDA64 has no FPS measurement capability -- but I suppose you have figured this out already ;)

    2) Logging cannot be started with a key combination or via any other shortcut I'm afraid. We may add this feature next year, but it's not on our short-term roadmap.

    3) The minimum polling frequently in AIDA64 is 1 second. That is because reading some of the sensor values may take up to 500 milliseconds, so having a lower polling frequency may cause serious issues or even deadlocks. Of course if you develop a separate software that only polls CPU usage, it would be possible to measure that more frequently. Although the millisecond basis sounds a bit too "ambitious" for GPU utilization measurement.

    Regards,

    Fiery

  10. I'm afraid it's not AIDA64. FX processors feature a temperature diode that measures wrong temperatures in basically all conditions. Usually that temperature is unrealistically low, well below ambient temperature. So far noone seems to have an idea on how to implement a workaround. It already happened before, with some AM2 processors, and there a simple offset helped to get proper temperatures. Maybe this time it's the same, but AMD didn't provide any useful information on the issue.

    Regards,

    Fiery

×
×
  • Create New...