Fiery

Exactly. The values listed in E-LEET are read using manufacturer-specific calls, usually some sort of SMI calls, directly from the BIOS. The actual calling method to retrieve those values is not only manufacturer dependant, but also custom to actual motherboard models, so such interface cannot be implemented in 3rd party diagnostic software like AIDA64. There're certain motherboards (e.g. Asus, Intel, some Gigabyte) that support standard interfaces like Asus ATK and Intel XTU, and so the BIOS settings can be read and displayed on the Motherboard / BIOS page in AIDA64. Unfortunately most motherboard manufacturers do not support standard interfaces

AIDA64 reads sensor information from sensor chips directly, except for the hard drives (and SSDs) It's not safe to communicate with disk drives directly, so AIDA64 uses standard Windows API calls to read SMART information and disk temperature. However, there are some SATA controllers that has such drivers that don't expose the standard Windows API interface necessary to read SMART information and disk temperature. In such cases AIDA64 will try to access the drives with alternative, manufacturer-specific SATA driver methods, but it won't work in every cases. In other words, reading SMART information and disk temperature is very much driver dependant, and that explains the differences you can see across various Windows versions and installations. BTW, SMBus has nothing to do with reading SMART information or disk temperature Regards, Fiery

Please note that certain SSD controllers may skip actually reading SSD sectors _if_ those sectors are still in their factory default state. In other words, if you don't fill (write) the drive completely with *some* data first (to initialize every flash chip blocks), the drive will know that those sectors are empty (not-yet-initalized, never written before), and it will simply give back zero values for all data in virtually no time at all. And that will effectively mean the drive will be able to "read" data at the throughput speed of the controller itself, which in the case of SATA 6.0Gbps (SATA3) controllers would be around 500 to 540 MegaBytes/sec. With SATA2 SSD drives that issue usually wasn't revealed, since the sequential read performance for many controllers almost matched the throughput of the SATA2 channel anyway Solution: before testing any SSD drives, make sure to create a maximum-size partition, and copy large files on it until it's completely full. Once the drive is filled, you can remove the partition, and start benchmarking the drive.

32:3 means 1066 MHz memory clock, since the base clock of Sandy Bridge processors is nominal at 100 MHz. So 100 x 32 / 3 = 1066.66 MHz, which is the clock speed of DDR3-2133 memory modules. We are not in a position to comment on values you obtain (the "8:1") using other software, since we're not behind those software in any ways. You can however contact the author of CPU-Z for clarification though. As for the voltages, make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1492kmc8wty1zbzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if you find any further issues in AIDA64 about your computer. Regards, Fiery

As IceMan suggested, upgrading to the latest AIDA64 beta should solve the issue. If not, then please let us know

In case your workstation computers do not log into a server, then the easiest way probably is to create a Scheduled Task on all computers, to launch AIDA64 Business Edition from a central location (e.g. a shared folder on your file server). Storing AIDA64 files in a central location is recommended because then it's easier to re-configure AIDA64, or to update to a newer version. Regards, Fiery

Please let us know more about your system configuration: 1) Motherboard model, CPU type? 2) Video card (or video cards) model? 3) Do you have any external disk drives connected? (e.g. USB, FireWire, eSATA) 4) Which version of Logitech gaming keyboard drivers do you have installed? Also, make sure to be running the very latest beta release of AIDA64 available at: http://www.aida64.com/downloads/aida64extremebuild1492kmc8wty1zbzip Thanks, Fiery

Thank you, but Sabertooth X58 is a different motherboard generation that does not support Thermal Radar.

I'm afraid you will still need Thermal Radar (part of Asus AI Suite 2) to be installed, in order to monitor the special temperatures in AIDA64. We've done numerous test runs, and tried several tricks on our own Sabertooth 990FX motherboard, but with no luck. Apparently Asus uses a special switch that is undocumented and one that we simply cannot figure out We've asked Asus for documentation on the Sabertooth sensors, but negotiations have broken down recently. We hope it's only because of the summer, and that negotiations will pick up in September.

Thank you for the feedback

Thank you. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1492kmc8wty1zbzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery

Please see post#3 above by Namuk.

That's rather odd. Do you have an AIDA64.INI file in the AIDA64 installation folder? If yes, then please try to rename it or delete it, to effectively reset AIDA64 settings to default values. Please also remove the whole AIDA64 key from Registry, including all its values and subkeys, using REGEDIT.EXE, at the path: HKEY_CURRENT_USER\Software\FinalWire\AIDA64

Thank you. I'm afraid something is going wrong with the sensor adjustments layer of AIDA64 on your motherboard. Even the voltages are off, but they all should be in line with PC Probe II, since your motherboard has already received "special treatment" in AIDA64. Maybe it doesn't work for some reason, or maybe your motherboard cannot be properly identified by AIDA64. Please do the following: 1) Copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. 2) Right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. Using that data we can continue investigating this issue. Thanks, Fiery

As I've stated above: In order to let us come up with our own AIDA64 plugin for AlphaCool, we would need either: 1) The source code or the uncompressed DLL image for acEverest.dll, or 2) Guidelines (SDK, programming documentation) on how to develop a new AlphaCool plugin from scratch

Then please try to close it, run REGEDIT.EXE again, and now try to change both the WindowPosX and WindowPosY values to zero (0). Hopefully that will make the window to appear in the top-left corner of either one of your monitors

Please try to close AIDA64, and start REGEDIT.EXE (Registry Editor). In REGEDIT navigate to the following path ... HKEY_CURRENT_USER\Software\FinalWire\AIDA64 ... and remove the following entries inside that path: WindowPosX WindowPosY WindowSizeX WindowSizeY WindowState Let me know if it helps. Thanks, Fiery

Most SSDs are equipped with a controller that is not capable of temperature monitoring. Even when a temperature readout is provided, in many cases it's stuck and shows a fixed value, no matter how cool or hot the SSD actually is.

Can you see a different "CPU" and "Motherboard" temperature in Asus' own monitoring software called Asus PC Probe II?

Thank you for letting us know

Due to limitations of ATA spec, most drives with 64MB cache cannot report their cache size in the ATA autodetect block. So what you see there is normal, unfortunately.

You seem to have posted an empty post with just a quote from me

1) What version of AIDA64 are you using? 2) Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. 3) Also copy-paste the full content of the Motherboard / CPU page of AIDA64 into this topic. Thanks, Fiery

Thank you for the feedback

Thank you for the feedback