-
Posts
11186 -
Joined
-
Last visited
-
Days Won
475
Content Type
Profiles
Forums
Events
Posts posted by Fiery
-
-
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.
-
You have misunderstood me
"CPU Aux=(translation)" already present in the language modules for AIDA64, but not "CPU2=..."
We'll fix that in the next beta release of AIDA64.
-
Thank you for the feedback
-
I apologize for English. Yesterday at last after inquiry in support service Asrock they have sent BIOS. It most likely a beta or something like it but the problem in it is corrected.
Thank you for letting us know.
-
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.
-
It seems that everything is working properly.
Thank you!
ps: Rename the "CPU2" in "CPU Aux" and will no longer need the localization of the term
Thank you for the feedback. We'll work on improving the labelling of Asus-related sensor readings
-
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
-
Thanks for the feedback
-
Thank you for the data. We've added the missing cooling fan in the following new beta release of AIDA64 Extreme Edition:
http://www.aida64.com/downloads/aida64extremebuild1764cxyfsvqwmnzip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Let me know if it helps.
Thanks,
Fiery
-
Thank you for the data. We've fixed the voltages in AIDA64 about your motherboard. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:
http://www.aida64.com/downloads/aida64extremebuild1764cxyfsvqwmnzip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Let me know how it works.
Thanks,
Fiery
-
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.
-
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
-
Please check the following topic on the CPU Fan #2 issue about your motherboard:
Regards,
Fiery
-
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
-
1) Do you use Windows 7 64-bit?
2) Did you have a previous version of Logitech LCD drivers installed before installing v8.20? Did AIDA64 work properly before installing v8.20?
Thanks,
Fiery
-
Please avoid posting multiple topics for the same issue. I've replied in your other topic. This topic closed.
Regards,
Fiery
-
Do you have a Logitech keyboard with a LCD display? E.g. G13 or G15 or G19?
Thanks,
Fiery
-
Do you mean thumbnails on this forum, or on the Screen Shots page of AIDA64 website?
http://www.aida64.com/product/aida64-extreme-edition/screen-shots
Thanks,
Fiery
-
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
-
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
-
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
-
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
-
Thank you for the feedback
-
Please upgrade to the latest beta version of AIDA64 Extreme Edition available at:
http://www.aida64.com/downloads/aida64extremebuild1754ks2vmhxr7dzip
After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
Let me know if it helps.
Thanks,
Fiery
CPUTIN temperature bug? (Asus P8H61-M LE/BR)
in Bug reports
Posted
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.
Thanks,
Fiery