Fiery

Dedicated and dynamic video memory usage are detected via an undocumented KMT call under Windows Vista and Windows 7, and the detection is available for every individual video adapters in use. On nVIDIA cards the info displayed on the Direct3D page is the video memory info for the primary video adapter, provided by the nVIDIA ForceWare driver via NVAPI calls. Since the manner of the KMT call (it's an undocumented call) I'm not sure how to compare its results to any other calls. Regards, Fiery

We'll do test runs in a hope that we can reproduce the issue you experience. If you've already made a decision on asking for a refund, then please make sure to notify ABSEIRA, our distributor for AIDA64 corporate products. They are the ones that need to process the refund and return your money back. Thanks, Fiery

AIDA64 has to provide a reading that is easy to read and "easy to digest" for most users. Since these days people download hundreds of MegaBytes of data from the internet every day, using at least 1 Mbps internet connection, the proper resolution simply cannot be KBytes. By using KBytes measurement unit the total downloaded data would quickly become very long and hard to interpret. E.g. if you have downloaded 2 GBytes since your computer is online, the total downloaded amount of KBytes would be 2097152. And after you've downloaded one GByte or more, the KBytes resolution simply becomes irrelevant. Just like these days people count HDDs and SSDs in GBytes, and noone cares about how much is it in MBytes or KBytes

Thank you for the feedback

I'm afraid it's not possible, because the hardware monitoring module of AIDA64 only supports a fixed measurement unit. So it's either KBytes, MBytes, or GBytes, but the unit cannot change as the value grows. Regards, Fiery

We've implemented GPU video memory usage monitoring in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...78fs2kxzgp9tzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. The measured values are listed on the Display / GPU page, and of course they can also be displayed on the OSD Panel, SensorPanel, Logitech LCD, or logged into file. Please note that GPU video memory usage data is only available under Win7 and Win8 (Windows Developer Preview). We might add Vista support later. Thanks, Fiery

We've fixed the memory clock measurement in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...78fs2kxzgp9tzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. This new beta implements GPU video memory usage monitoring as well The measured values are listed on the Display / GPU page, and of course they can also be displayed on the OSD Panel, SensorPanel, Logitech LCD, or logged into file. Please note that GPU video memory usage data is only available under Win7 and Win8 (Windows Developer Preview). We might add Vista support later.

AIDA64 System Stability Test only uses high-level file system read operations. It scans all local disk partitions for files, and then it randomly opens a file and reads a random amount of data from it. It then closes the file and steps on to the next one. A separate processing thread is started for each local partition, hence e.g. if you have C:, D:, E: and F: local disk partitions, then it will use 4 threads in parallel to read 4 files simultaneously. It will effectively put stress on every local disk drives in parallel. AIDA64 only destroys data in its Disk Benchmark module, if you issue any write tests. But, first you have to manually enable write tests there, and even after that you will be warned 3 times before starting a write benchmark. You will have to press "Yes" button 3 times before your data gets destroyed. Regards, Fiery

We've already submitted a form to ask Symantec to whitelist AIDA64 files. We're awaiting their response. We too have noticed that unlike previous high-end GPUs HD7970 doesn't seem to support 3 diode temperature readouts, but I'm afraid it seems to be a hardware limitation. Even GPU-Z reports only 1 diode temperature for HD7970.

On our test card actual memory clock and the clock reported by AIDA64 doesn't have a direct association. E.g. even if we set 1100 MHz, 1200 MHz or 1300 MHz memory clock via Catalyst Control Center, the memory clock reported by AIDA64 is a constant 1775 MHz. We'll work on it, although this part seems a bit trickier than the rest As for VRAM usage, it's still a mystery. It's possible to do it, since GPU-Z can do it, but we have no documentation and no pointers on what ADL calls or registers we need to use.

It's a false alarm, just ignore it. We're already in contact with Symantec to make sure they won't report any more false alarms about AIDA64 files in the future. We're currently working on the memory clock issue, so stay tuned for new AIDA64 beta updates And feel free to report any other issues you may find about AIDA64 Beta 1773 and HD7970 in this topic.

Thank you for the feedback

Thank you. We've tweaked the RAID enumeration for Intel chipsets, but I'm not sure if it would help to eliminate the freeze on your system. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1773d6b3jpkrmfzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

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

We've fixed the DIMM temperature refresh issue. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1773d6b3jpkrmfzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Please note that on a lot of LGA2011 motherboards the DIMM temperature readout looks weird, or it is simply not implemented by the motherboard. So in case you get weird or unreal temperatures, then just ignore the values. Regards, Fiery

Thank you. We've fixed it up, so please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...73d6b3jpkrmfzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps

We've implemented full support for Radeon HD 7900 Series in the following new beta release of AIDA64 Extreme Edition: http://www.aida64.com/downloads/aida64extremebuild1773d6b3jpkrmfzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. The only slight issue remains is the memory clock calculation. Unfortunately it will come out wrong in both 2D and 3D mode. We'll work on that. The rest should be accurate Thanks, Fiery

Similar license keys are usually provided by Microsoft when volume licensing (VLM) is chosen (e.g. Corporate Edition products). So far we haven't seen AIDA64 reporting a wrong license key. Can you please double-check whether the reported key is really not belonging to your corporation? Is there a chance the key is provided by Microsoft's own VLM server perhaps?

1+2) GPU and memory clocks are throttled down to low values automatically by AMD Catalyst video driver in 2D mode. Clocks should "jump" up to the factory default values once you start a 3D application or a game. 3) We've double-checked it, and AIDA64 accurately follows Intel's specifications on DX79SI/DX79TO sensors layout. We've asked Intel about this issue, and awaiting their reply. Once we have an update to this, I'll drop a message into this topic. 4) DIMM numbering may look a bit weird, but it's the best we could come up with so far. It's because the memory controller of your processor supports up to 3 DIMM slots per memory channel, but on your motherboard only 2 DIMM slots are utilized. The physically not present 3rd slot is skipped from the list of DIMM modules there. It looks normal from a technical point of view, but I admit, it looks a bit odd from a user's point of view 5) We'll work on this issue too. I'll let you know in this topic once we have a new beta with this bug fixed. Thanks, Fiery

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

Are you sure you've performed the update to Beta 1770? That output looks like it was done using a previous AIDA64 version. Does AIDA64 show "AIDA64 v2.00.1770 Beta" on the main screen?

Thank you for the feedback That's normal. When AI Suite says "Power", it means "PSU", so Power Supply.

We've got our own HD7970 card only yesterday, so that's when we had a chance to start working on it. It seems a lot of things have changed, so we need a couple of days to implement the necessary changes in AIDA64 to support all aspects of the HD7900 Series. I'll drop a message in this topic once a new AIDA64 beta becomes available. Regards, Fiery

The DDraw method doesn't work under Vista and Win7 anymore. AIDA64 uses that method under WinXP on both AMD and nVIDIA cards. As for the undocumented driver method, yes, GPU-Z most likely uses such trick. Most probably it uses an undocumented ADL call, but we don't know more than that I'm afraid

Yes, we've renamed the NIC Download Rate and NIC Upload Rate items, so you have to reconfigure that on the LCD, OSD or SensorPanel. Regards, Fiery