Fiery

The French translator doesn't handle the localization properly at times. We'll fix the line Thanks, Fiery

In order to give you a proper explanation, please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. Also right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic. Thanks, Fiery

Thank you, we've added the listed 3 extensions, and also 26 more extensions related to OpenGL ES. It will be rolled out as a new beta release soon. Regards, Fiery

GPU Ambient is usually the temperature of the GPU sensor chip. It is also known as GPU Environment temperature or Video Card PCB temperature. Regards, Fiery

That's not necesserily the case when special tricks make it more complicated, e.g. CrossFireX, DualGraphics, HyperMemory, etc. We'll try to figure out a reliable method.

The Direct3D KMT calls AIDA64 use are undocumented, and as far as we know, they do not provide a specific "total video memory" info. Hence we cannot calculate video memory utilization at this time

Yes, we recommend you to watch the core temperatures measured by AIDA64.

Thank you for the feedback

It is already available for over a year now You can buy a new license for 12 months, 24 months or 36 months; and you can extend an existing license with +12 months or +24 months or +36 months. 24-month licenses cost 50% more than standard (12-month) licenses. 36-month licenses cost twice as much as standard (12-month) licenses. Regards, Fiery

Sandy Bridge processors provide quite a few sensor readings (e.g. core temperatures, CPU Package temperature, etc), so it's best to watch them and ignore the rest of the readings provided by motherboard sensors (e.g. "CPU" temperature). For the most accurate sensor readings, make sure to upgrade to 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. Regards, 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