Fiery

Thank you for the feedback

We've fine-tuned the sensor information to better support your motherboard. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1412vs6dflky0szip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Please note that the CPU fan RPM may be lower under Windows than in the BIOS Setup due to the fan controller logic used by your motherboard. Thanks, Fiery

We've fixed the temperatures for your motherboard. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1412vs6dflky0szip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery

The bug is due to the pecularities of UEFI BIOS. We've applied a workaround to make sure AIDA64 detects the correct system date on all systems. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1412vs6dflky0szip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery

AFAIK OCZ Vertex3 drives haven't got a working temperature sensor.

I'm sorry, but I can't promise you a fan controlling feature for the upcoming months We're focusing at other AIDA64 improvements and new features for 2011.

Thanks for the dump. The fix will be included in the next AIDA64 beta release.

We already have an option in AIDA64 / main menu / File / Preferences / Stability called "SMBus access through ACPI" to avoid conflicts with Asus' own monitoring and tweaking software. Please try to enable that option, restart AIDA64, and check if fixes the issues. Please note that it may or may not work on your motherboard, due to differences in ACPI implementation by Asus across various Asus-made motherboards. BTW, just like most Windows monitoring, tweaking and oveclocking software, AIDA64 uses standard mutexes to avoid conflicts with other similar purpose Windows software: http://www.techpowerup.com/wiki/doku.php/systool/mutexes_to_avoid_collisions Even though the developers behind those synchronized software asked Asus numerous times to implement those mutexes in Asus monitoring software, Asus still refuse to do so. It makes avoiding such conflicts a very tough, almost impossible job

You can actually do both of those if you right-click on the "Benchmark" group in the left window, and select "Quick Report" Regards, Fiery

Core temperatures are read from the CPU. AIDA64 uses the core temperature measurement method that AMD recommends, so in case the measured values are off, it's not the fault of AIDA64. We'll fix the voltages in the next AIDA64 beta.

Maybe some Registry values have been left there on your system. Please try the following to remove any residual Registry entries: 1) Close AIDA64 2) Start Registry Editor (REGEDIT.EXE) 3) In the Registry Editor navigate to the following path: HKEY_CURRENT_USER\Software\FinalWire\AIDA64 4) If you have a folder called VistaSidebar inside that path, then delete it completely. 5) Then Navigate to the following path in Registry Editor: HKEY_LOCAL_MACHINE\Software\FinalWire\AIDA64 6) If you have a folder called VistaSidebar inside that path, then delete it completely. 7) Then restart your computer, and check if that fix made any difference. Thanks, Fiery

Thank you, we'll fix the voltages (thanks Mumak ) Can you please tell me what's wrong with the temperatures? Are they too high? Or too low? Or they show the right values, but they're labelled wrong? Please note that in the BIOS Setup the CPU is running at 100% load, while under Windows it can switch down to power saving states. Hence in the BIOS Setup the temperatures will always be higher than under Windows.

1) First of all, please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1405bd3cym9gvszip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. 2) Then 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. Based on that output, we can check out what's wrong with the CPU sensor. Thanks, Fiery

Maybe these days WD have come to their senses and use unique model names for each drive, but it wasn't the case for many years. When we've started to build our hard disk drive database, it was terrible, so we gave up. We may get back to WD drives if they survive the ongoing "who buys who" game in the HDD industry

Thank you, we'll fix it in the next AIDA64 beta release. Regards, Fiery

We've tried to replicate the issue, but it worked flawlessly on our test systems. Please let us know more about your system: 1) Windows version, kernel type (32-bit or 64-bit) 2) Motherboard model, CPU type 3) Do you have UAC enabled? 4) Do you have "Use HKLM in Registry" option checked or unchecked in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Vista Sidebar? 5) I suppose you configured AIDA64 to start itself automatically at Windows boot. Have you tried to close AIDA64, remove its scheduled task using Task Scheduler, and then start AIDA64 again to let it re-create its scheduled task? Thanks, Fiery

WD has a habit of assigning the same model ID to different products. And that makes it impossible to build an accurate WD hard disk drive database. We currently have no plans to extend our hard disk drive database with further fields. Regards, Fiery

Thank you for the dumps. To our knowledge MegaSR controllers have such RAID drivers that don't expose SMART attributes readout or ATA passthru interface Do you have any tools (either manufacturer supplied or 3rd party) that can read SMART attributes for your RAID member drives?

I think you basically have 2 options: 1) You can enter the AIDA64 product key in one of the AIDA64 copies. It will create a PKEY.TXT file in the AIDA64 folder on that specific computer. Then you can simply copy that file onto all other computers, into the local AIDA64 installation folder. 2) Or, better yet, you can switch from using 50 local copies of AIDA64, and launch AIDA64 from a central place (e.g. a shared folder on one of your file servers) using a UNC path. That way managing licenses, adjusting settings, and upgrading to new versions are very easy, since you only have to adjust a single installation of AIDA64. If you go for #2, make sure to properly set security options for the shared AIDA64 folder, providing read-only access (and not read-write access) to your network users. Regards, Fiery

You need to have AIDA64 running in the background to measure various values and put them on the Sidebar gadget. It cannot work without having AIDA64 running. You can however hide AIDA64 main window if you want, by e.g. double-clicking on its System Tray icon.

You need to have AIDA64 running in the background to measure various values and put them on the G19 LCD screen. It cannot work without having AIDA64 running. You can however hide AIDA64 main window if you want, by e.g. double-clicking on its System Tray icon.

I'm not sure what is your existing license, so I cannot give you a definitive answer now. It would be best if you could contact our Licensing Department at: upgrade AT aida64.com (replace AT with @) In your email make sure to indicate your full name, the date of purchase, and your existing product key(s).

Have you tried to enable RAID SMART support in AIDA64 / main menu / File / Preferences / Stability? After altering that option make sure to restart AIDA64. If that option is enabled, and you still don't get SMART values for your RAID member drives, then please do the following: 1) Right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic. 2) Also right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> Disk Controllers Dump. Copy-paste the full results into this topic. Using those outputs we can check whether any existing AIDA64 RAID controller methods would be applicable by the RAID controller of your motherboard. Thanks, Fiery

You didn't put a smiley there, so I wasn't entirely sure how you meant it So I felt it was best to clarify the logic behind the visibility of the BIOS & driver updates toolbar buttons.

Those buttons promote eSupport services, and not our services or our products. And the links are also accessible from various other pages in AIDA64 in both legal and illegal copies of AIDA64.