Fiery

We've tried to replicate the issue, but it seems it may not be related to the original issue that we've already fixed in Build 1334. Do you have those fans (pumps) spinning before you open the AIDA64 Preferences? If yes, then approx. what RPM can you see for them on the Computer / Sensor page?

I'm sorry for the delays, we've tried to replicate the issue on multiple configurations this time, but without success There's one more Registry path that may worth trying to delete though, so please do the following: 1) Close AIDA64 2) Start Registry Editor (REGEDIT.EXE) 3) In the Registry Editor navigate to the following path: HKEY_LOCAL_MACHINE\Software\Wow6432Node\FinalWire\AIDA64 4) If you have a folder called VistaSidebar inside that path, then delete it completely. 5) Then restart your computer, and check if that fix made any difference. BTW, if you don't use EVEREST anymore, then please remove all "Lavalys" folders (including all their subfolders) from the Registry as well, by scanning the Registry for "Lavalys" in REGEDIT. Thanks, Fiery

AIDA64 can measure CPU utilization for all cores on the Motherboard / CPU page. You can also put the per core utilization to the OSD Panel, Sidebar Gadget and Logitech G13/G15/G19 LCD (AIDA64 / main menu / File / Preferences / Hardware Monitoring). The graph in the System Stability Test shows only a sum of CPU utilization, because it's there only to let you check whether your overall system utilization is really 100% while you're running the AIDA64 stress test.

Something is not right about this monitor. Samsung tends to fill in all fields correctly, and so this monitor cannot be a 943N or any other 19-inch LCD, since the size field indicates it is a 17-inch monitor.

Thank you, we've added it to the AIDA64 monitor database. Regards, Fiery

That's normal, since Asus EeePC netbooks are not equipped with a sensor chip that would be capable of monitoring voltages. Regards, Fiery

In case it doesn't work as expected, then 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 --> Sensor Debug --> ISA Sensor Dump, and copy-paste the full results into this topic. Thanks, 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.