Fiery
-
Posts
11186 -
Joined
-
Last visited
-
Days Won
475
Content Type
Profiles
Forums
Events
Posts posted by Fiery
-
-
Can I simply extract the new version into the same folder that I placed version 2.00 into? Will I need to reactivate with my license code?
Yes, you can. By performing the upgrade that way your existing license and settings will be retained. BTW, the built-in Automatic Update feature would perform the upgrade the same way automatically.
-
Thank you very much, Fiery. My situation was #1. I had everything but "stress local disks" checked. I might try the "Stress FPU" option by itself later to see what happens. Thanks again.
Make sure to upgrade to AIDA64 v2.20 once it becomes available (less than 24 hours from now). You'll then be able to activate FPU+GPU stressing to drive your computer to maximum power draw and maximum temperatures.
-
The AIDA64 System Stability Test (SST) can produce the following results:
1) No visual feedbacks -- it means everything went well. In your case this happened I guess.
2) AIDA64 displays an error message on the SST user interface, and the SST window becomes red -- it means AIDA64 revealed a hardware flaw that isn't serious enough to make the computer or Windows crash, but it's still considered an instability issue.
3) AIDA64 throws an application error or crashes; or Windows throws an error message -- just like #2, it is an instability that doesn't necesserily cause a system lockup.
4) Windows throws a BSoD; or the computer locks up / reboots / powers off -- serious instability is found, but of course AIDA64 cannot provide a feedback about such issues.
Please note that there are several modes in which the AIDA64 SST can operate. If you only have "FPU" (together with "GPU" with the upcoming AIDA64 v2.20 release) test enabled, SST will drive the system to its maximum temperature by executing such code that stresses the execution units of your processor (and GPU) to its maximum throughput. There are instable systems that only becomes instable when you run this kind of SST.
Another mode is by executing all possible subtests of the AIDA64 SST, by having CPU + FPU + cache + system memory + local disks (+ GPU) all enabled. In such case thermal stress will not be maximum, but the workload will stress all components of the system. In several cases the instability can only be revealed by running this kind of SST.
Please also note that instability is unfortunately not something you can accurately measure. It's not like universal truth of "2 + 2 = 4"
Some instability can be revealed by a specific approach, by running a specific workload on the system. Some workloads may reveal a certain instability in seconds or minutes, while with other workloads it will take hours or days to reveal the problem.Regards,
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
-
Anyway, since Windows reports file sizes in KBytes, would that not be more consistant?
Just my opinion, but it seems logical to me.
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
-
Can confirm that both Memory clocks and Video Memory Usage are working perfectly in Win7 (x64)
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
-
So got this working now since I had NIS ignore the two files in question. Would appreciate if you guys could post when Norton confirms they've updated their definitions to no longer flag these files as viruses so I can remove them from the exclusion list.
Now in terms of monitoring, this version is definitely limited compared to what I could read from my Radeon 6950. The main temps I used to use when I had a 6950 were the MemIO, ShaderIO, VRM and Diode/Core temps. Are these going to be added to a later revision of Aida, or are these temperatures just not possible anymore?
Thanks.
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.
-
Just so it's reported, the memory clock is 1/4 of it's true value in 2D clocks, and 1/2 it's true value at 3D clocks.
(Memory is double data rate, so the actual rate is twice that shown in CCC / Afterburner etc)
If we're talking about those rates, then at 2D clocks, AIDA is reporting half it's value, and 3D clocks AIDA is reporting 2x actual value.
(I re-read this and it's confusing, but I can't explain it any better
)Also, any plans to implement the VRAM usage, if it is indeed possible?
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.
-
Is there a reason why Norton Internet Security 2012 is detecting trojans/viruses in aida_update.dll and aida_diskbench.dll?
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.
AIDA64 v2.20 is out!
in General Discussion
Posted
The new AIDA64 update further enhances its System Stability Test module with OpenCL GPGPU stress test, and implements optimized 64-bit benchmarks for Intel Atom“Cedarview” processors and for the upcoming Intel Core "Ivy Bridge" APUs.
New features & improvements
- OpenCL GPGPU Stress Test
- Support for Intel Atom "Cedarview" processors
- Support for Intel Core "Ivy Bridge" APUs and Intel 7-Series chipsets
- ACPI 5.0 and OpenCL 1.2 support
- GPU details for AMD Radeon HD 7970 and nVIDIA GeForce GT 640
[ Press Release ]
[ What's new in AIDA64 v2.20 ]
[ Download ]