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

Please have this option enabled, and right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic. BTW, what version of Intel RST drivers do you have installed? Thanks, Fiery

No correction applied, so those values represent the actual desktop (X,Y) pixel position.

Thank you for the feedback

Thank you for the feedback

Please enable the option RAID SMART support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it helps. Thanks, Fiery

AIDA64 uses the industry standard GlobalMemoryStatusEx Windows API call to detect memory status. That function returns a structure called MEMORYSTATUSEX. The swap space info is taken from the structure entries called ullTotalPageFile and ullAvailPageFile. You can read about their meaning and purpose at: http://msdn.microsoft.com/en-us/library/windows/desktop/aa366770(v=vs.85).aspx Regards, Fiery

Thank you for the feedback

Thank you for the dump. 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 how it works. Thanks, Fiery

Thank you. We've fixed the Vcore reading, so 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 how it works. Thanks, Fiery

Thank you. We've fixed the sensor readings, and also implemented a series of new readings for your board. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...54ks2vmhxr7dzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

I'm glad you worked it out. Thank you for letting us know

Write benchmarks on disk drives are not used by most AIDA64 users, mostly because they erase all data from the tested drive. And also, using write benchmarks on SSD drives will shorten their lifespan. We already have separate write tests for disk throughput and access tests, so you can use them if you need to test write performance. Regards, Fiery

We currently have no tutorial made for the remote features of AIDA64, but please feel free to ask questions or ask for guidelines here, or via email: support AT aida64.com

Thank you for the dumps. If it's possible, 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. Thanks, Fiery

No, you don't have to unlock the position. Just make sure to close AIDA64, then you can alter the mentioned Registry entries.