Fiery

I'm sure it's just an inaccurate reading. Are you running the latest AIDA64 beta release? http://www.aida64.com/downloads/aida64extremebuild1412vs6dflky0szip

The license count will not count down.

It's normal, since the NVAPI I2C layer issue only affects such GeForce cards that have an onboard sensor chip (e.g. ADT7473) and/or an onboard voltage regulator chip (e.g. Volterra). Anything below the top level (under GTX470/480/570/580/590) should still be fine.

That's normal, since Everest uses direct I2C communications. However, nVIDIA strongly advises against using direct I/O on GeForce 400 and GeForce 500 Series, so with AIDA64 we've switched to using the driver-level I2C I/O by default, via ForceWare's NVAPI layer. You can still switch back to the direct I/O with AIDA64 if you want --> AIDA64 / main menu / File / Preferences / Stability / disable the option called "nVIDIA GPU SMBus access through nVIDIA ForceWare", and restart AIDA64. We've already started performing test runs using ForceWare 275.xx drivers. The new drivers seem to have a broken NVAPI I2C interface. We'll need a bit more time to find out more about the root of the problem, and to possibly implement a workaround.

Thank you. I think it may be due to a broken I2C API of ForceWare's NVAPI module. We'll check it out.

Okay, so the previous fix didn't solve it We'll work on it, and I'll let you know in this topic once we have a solution. Thanks, Fiery

Can you please tell us more about the issue? Or maybe a link to a forum topic where users discuss it? Thanks, Fiery

That bug has already been fixed in Build 1334. Are you using an AIDA64 build newer than that?

Thank you for the feedback

Do you mean AIDA64 only detects one GPU on the Display / GPU page? Or you mean AIDA64 only measures one GPU temperature on the Computer / Sensor page? If the latter, then it's normal, since most IGP chips do not feature a thermal diode.

You can either use the External Applications feature (AIDA64 / main menu / File / Preferences / Hardware Monitoring / External Applications) to export the temperature, voltage and fan RPM values to WMI, shared memory or Registry. Processing those values from a Windows program should be relatively easy, and you can pick whichever method you prefer to process from your program. Or you can also save those values to a CSV or HTML log file in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging. The CSV log file is also easy to process from another program.

That date is encoded into the AMI BIOS motherboard ID. AIDA64 has no control over that entry. You can check the actual system BIOS date (detected by AIDA64) on the Computer / Summary and Motherboard / BIOS pages.

Thank you for the feedback

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.