Fiery

Benchmark Results Manager was implemented on June 21, 2005

Yes, we've implemented that feature as per your request

I think it is possible Please do the following: 1) Run AIDA64 Extreme Edition 2) Navigate to the Benchmark / CPU Queen page 3) Click on the Results button on the tool bar 4) Select "Show Reference Results". That should remove all reference results from the list. If you haven't yet saved any of your own results, then the benchmark results list will be emptied. 5) Then run one of the benchmarks as usual 6) When the benchmark is finished, click on the Results button on the tool bar 7) Select "Add Result to User List". Then you will start building your own results. 8) Later on, if you want to manage your saved results (e.g. delete one or more results), you can click on the Results button, and select "Manage User Results". Regards, Fiery

No other tricks or software is needed. Make sure to enable the AIDA64 plugin in Rivatuner as well.

Such mixups can occur when a hot-pluggable (usually USB) device is connected while running AIDA64. We tweaked a lot about hot-plug support in AIDA64 v1.50, so hopefully it will work better than previous versions As for "ATA Device", that text is put there by Windows, and we have no control over that naming scheme. Windows uses "ATA Device" for both PATA and SATA drives. The "IDE" tag is detected by AIDA64, and it means the drive is either PATA or SATA, but a more precise identification is not possible.

I think both "CPU" and "Aux" temperature readings are invalid, and should be ignored. You can verify how many temperatures your motherboard can actually monitor, if you check the PC Health Status (or HW Monitor) page in the BIOS Setup. Regards, Fiery

I don't think you saw texture memory usage. Maybe it was local video memory and non-local video memory usage? Those values are listed on the DirectX / DirectX Video page. However, those cannot be detected under Windows Vista and Windows 7 anymore, due to architectural changes about how Windows handles video memory.

I've replied to that in your other topic. Please avoid posting the same issue into multiple topics (it's not easy to track things).

Please copy-paste the full content of the Display / Monitor page of AIDA64 into this topic. If it's possible, we'll add your monitor to the AIDA64 monitor database. FYI, not all monitors can be identified due to lack of identification data programmed into the EDID record of the monitor.

Maybe the mixup about the clocks comes from the fact that AIDA64 shows both real and effective clocks, while EVGA Precision only shows the effective clock? Slight difference between the configured clock and the actual clock may come from PLL inaccuracy. In other words, it's not always possible to configure the clock PLL to produce the requested clock, so 10-20 MHz difference is considered normal. As for the fan issue, you need to wait for EVGA to roll out a new Precision release that is properly synchronized with hardware monitoring software (e.g. AIDA64, HWiNFO32, SpeedFan, HWMonitor, etc).

Maybe EVGA Precision shows the effective clock, while AIDA64 shows the real clock. In fact, AIDA64 is supposed to show both real and effective clocks. Clock speeds for DDR memories can be interpreted differently

1) Please copy-paste the full content of the Computer / Sensor page of AIDA64 v1.50 into this topic. 2) Then right-click on the bottom status bar of AIDA64 v1.50 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. 3) Also right-click on the bottom status bar of AIDA64 v1.50 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. Based on that data we can check what happened to the temperature labels. Thanks, Fiery

Nothing has changed in AIDA64 v1.50 about the External Apps feature, so what worked with AIDA64 v1.20 should still work with AIDA64 v1.50. Make sure to enable that feature though, in AIDA64 / main menu / File / Preferences / Hardware Monitoring / External Applications.

Please check Q#10 in our Knowledge Base: http://www.aida64.com/support/knowledge-base Regards, Fiery

We've made an AIDA64 Rivatuner plugin that you can download from: http://www.aida64.com:8081/rivatuner_aida64_monitoring_plugin.zip

The requested items are implemented in the today's update for AIDA64: http://www.aida64.com/news/finalwire-rolls-out-aida64-v150 Regards, Fiery

It looks great, thank you for letting us know. Regards, Fiery

I guess the mixup came from the fact that you first obtained a free upgrade in our original campaign (that ran between Oct 06 and Oct 20). In that campaign EVEREST customers were entitled to receive a free upgrade to AIDA64 v1.00. The critical information there was: v1.00. Even though the free upgrade key then was intended to be used only for AIDA64 v1.00, it was good for AIDA64 v1.20 as well. But then it stopped working with AIDA64 v1.50. I guess your new AIDA64 upgrade license was then obtained using the current upgrade procedure, so it will be valid for the same maintenance period than your original EVEREST license. It means you can use it with AIDA64 latest version as well.

Please drop an email at the following email address, and our Licensing Department will check out what's wrong with your AIDA64 key. Make sure to indicate your name and AIDA64 license key, so our staff can identify you. upgrade AT aida64.com (replace AT with @)

Such temperature readings are usually read from the onboard sensor chip, but not from the usual CPU or Motherboard registers. So they could either mean a special temperature (e.g. PWM temperature, chipset temperature, DIMM temperature), or an invalid reading. You can check out the Computer / Sensor page to see if those 2 special readings are valid or not. Regards, Fiery

AIDA64 licenses are not limited by version number, but only by time constraints (maintenance limit). You can use AIDA64 v1.50 with the same AIDA64 license. You will also be able to upgrade to any AIDA64 beta or stable version that will be released before your maintenance period expires (Sept 2011). Regards, Fiery

Thank you for your kind words I'm sorry for the late reply, but we've been very busy with the new AIDA64 release we could finally roll out today: Regards, Fiery

The new AIDA64 update implements AVX-optimized benchmarks for the upcoming Intel Sandy Bridge processors, adds a brand new video encoding benchmark, and supports the latest AMD and nVIDIA graphics processors. New features & improvements - Support for the upcoming Intel Sandy Bridge desktop and mobile processors - AVX-optimized 64-bit fractal and security benchmarks - AVX-optimized System Stability Test module - 64-bit multi-threaded VP8 video encoding benchmark - Revamped ZLib data compression benchmark - GPU details for AMD Radeon HD 69xx and nVIDIA GeForce GTX 570 - Enhanced support for nVIDIA RAID controllers - Estonian localization Website enhancements AIDA64 Extreme Edition quickly became an indispensable utility for hardware reviewers all around the world. On the AIDA64 Testimonials web page professionals from Hungary, Romania, Russia, UK, and USA explain how AIDA64 helps their everyday job while analyzing and benchmarking various PC hardware components. [ Press Release ] [ What's new in AIDA64 v1.50 ] [ Download ]

Thank you. It's rather weird that it stalls at the nVIDIA RAID array. If it's not too much trouble, can you please try to perform the same HDD SPTI Dump with the USB card reader disconnected? It would be great if we can narrow this down to either the RAID array or the card reader. Thanks, Fiery

The confidential info may not need to be released. AFAIK DES 2 and DES Advanced applications use a NT service to measure power draw, and report it via a text file (INFO.DAT). Sounds like a way that could be used by 3rd party applications as well. However, the service stops reporting the values when the DES main application is not running So it's not really useful that way.