Fiery

I'm afraid it's still the same issue. We've contacted Asus and requested permissions to gain access to their Thermal Radar programming manuals, but they're reluctant to provide such documentation to other companies. So we still have no documentation on the Thermal Radar hardware, and we cannot figure it out on our own If someone can explain how to activate the special Thermal Radar temperature readings without installing Asus Thermal Radar software, we would be glad to implement that in AIDA64. Regards, Fiery

I'm sorry, but we do not make custom Sidebar Gadgets for our software. But maybe another forum user would be able to help you out. Regards, Fiery

Please check it with other tools (e.g. CPU-Z) as well. Also, make sure to disable C-States support (in the BIOS Setup) as well, since that may also cause clock variation.

I'm not sure what's wrong with the computer you benchmark, but many hardware reviewers from review portals think AIDA64 as a diagnostic software, and the benchmarks it offers are very useful and properly represent CPU and memory performance: http://www.aida64.com/testimonials Maybe if you could show us actual screen shots of benchmark results obtained with AIDA64 would help. Make sure to also explain what system it is, and whether it is overclocked or not. Please note that the reference benchmark results are always obtained on non-overclocked and non-tweaked systems, to represent "out of the box" performance of average PC systems. Regards, Fiery

No, it won't ask for a reboot. But from now on, with the Automatic Update feature things will improve, since before the actual update takes place, AIDA64 will unload the kernel drivers to avoid such issues.

It's working, since at least 4 fans are displayed on your screen shot But as I've stated above, it's not possible to detect all fans, due to the ASRock fan mux logic.

Kernel drivers have been revamped in AIDA64 v2.00, which means after upgrading to this new version you need to restart Windows to get the kernel drivers replaced. Regards, Fiery

On certain ASRock motherboards it's not possible to detect all fans, but only 5 out of 6 for example. This is due to ASRock using a special mux for fan speed logic, which can only be properly handled by their own software (AXTU or F-Stream). Also, make sure to use the latest AIDA64 version of v2.00: http://www.aida64.com/downloads Regards, Fiery

We can only do what you do, which is submitting the file to Symantec, so they can take a look at it...

Don't worry, it's a false alarm. Make sure to submit the file to Symantec, and they will fix their anti-virus engine. BTW, recently we've got various false alarms from Norton AntiVirus, on AIDA_DISKBENCH.DLL, AIDA_UPDATE.DLL and other components of AIDA64. Our products are verified and 100% free from malware. But in case you have doubts, let Norton AV remove those files. Even without them most functions of AIDA64 will still be operational Regards, Fiery

We provide a 2-week grace period for such situations. Hence even if the maintenance period of your license is expired on October 11, 2011, you will be able to upgrade to AIDA64 v2.00. Regards, Fiery

AIDA64 v2.00 stable release is out, with the official debut of the new Automatic Update feature: http://forums.aida64...64-v200-is-out/

The new AIDA64 offers a fully automatized online update, AVX-optimized 64-bit benchmarks for the upcoming Intel Core i7 “Sandy Bridge-E” processors, and further extends its exhaustive hardware database with Western Digital hard disk drives to cover 133.000 devices total. New features & improvements - Automatic Online Update - Support for LGA2011 Intel “Sandy Bridge-E” processors - Preliminary support for AMD “Krishna” and “Wichita” APUs - Preliminary support for Intel Atom “Cedarview” processors - Preliminary support for Intel “Ivy Bridge” and Intel 7-Series chipsets - Enhanced support for Western Digital hard disk drives - Revamped ACPI table enumeration and decoding - Support for VMware Workstation v8 - GPU details for AMD Radeon HD 6625M and nVIDIA GeForce GTX 570M [ Press Release ] [ What's new in AIDA64 v2.00 ] [ Download ]

For smart batteries such info should be listed on the Computer / Power Management page in AIDA64. Regards, Fiery

Please choose your words more carefully, and do not call anyone here a "dummy". I don't mind critical observations about AIDA64, but: 1) You don't seem to be using a legal copy of AIDA64 2) By stating "this sensorpanel thing its nothing else than the sidebar gadget just without the support for transparency" you clearly admit you don't know what these features are about, and how much more advanced the SensorPanel is, compared to the Sidebar Gadget feature. BTW, by cutting the underlying part of the Windows Desktop wallpaper and adding it as a background image on the SensorPanel, you can actually make the SensorPanel sort of "transparent". 3) Most of our customers actually prefer the clean, easy-to-use interface of what AIDA64 currently features. We could add more "bling", more "explosions", more colours, but a lot of the people who use AIDA64 focuses on what really matters for them: accurate sysinfo, cutting edge benchmarks, wide-range of hardware monitoring features.

Converting that (as is) into a SensorPanel may be considered a copyright violation. Making something that looks close to it would be okay though

We'll do more test runs with an Optimus capable system as soon as we can get one. Maybe there's room for tweakings, although the way Optimus works, there may never be a perfect way to monitor the nVIDIA GPU as part of an Optimus system. As for the ACPI issue, it is due to either a BIOS bug or a not-properly-written Windows 7 activation crack.

Thank you. The Aux temperature looks like an invalid reading that should be ignored. We'll remove that reading in the next AIDA64 release.

Thank you. I'm afraid without the SMBus Dump we cannot do more at this time. We'll do more investigations as soon as we can get a non-reference HD6950.

You can remove AIDA64.INI file in AIDA64 folder to reset settings to their default. Regards, Fiery

A quick idea: try disable Multi-GPU support in AIDA64 / main menu / File / Preferences / Stability, then restart AIDA64. In case on your system the nVIDIA GPU is the secondary GPU on the PCI bus, then activating that option will effectively disable GPU support for the nVIDIA GPU, hence the reported issues should go away. Let me know how it goes

It's normal. On Intel chipsets AIDA64 may enable certain devices (like SMBus or thermal controllers) to let it read SPD memory module information or chipset/CPU sensor readings. Regards, Fiery

1) Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers. Copy-paste the full results into this topic. 2) Then right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI SMBus Dump. Copy-paste the full results into this topic. Thanks, Fiery

We've implemented that on the Storage / Windows Storage page in the following new AIDA64 beta release: http://www.aida64.co...61g6r3qtbpklzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. However, the new feature will only work under Windows 2000, XP and 2003. We haven't yet found a way to detect the same properties under Vista and Win7. We'll work more on it after the next AIDA64 stable release. Thanks, Fiery

Good idea, although please note that Corsair Link is not officially released yet. We're working with Corsair on implementing Corsair Link support in AIDA64. We'll contact Antec to find out if we can do the same with their products as well. Thanks, Fiery