Fiery

It doesn't give any scores. But it may display an error message (and paint the window to red) when it detects a CPU or memory error.

As I've stated above, AIDA64 is not designed to handle switchable graphics monitoring in any ways. When AIDA64 starts, it scans the system for available GPUs. When AIDA64 starts, and you have the Intel GPU enabled and the AMD GPU disabled, it will not be able to monitor the AMD GPU unless you restart AIDA64. I know it may be considered a limitation, but it's a sacrifice we had to make to make sure AIDA64 can monitor GPU sensors without too much overall system performance hit. We'll work on better supporting switchable graphics, as soon as that technology finds its way to desktop computers as well.

Fan PWM percentage (also known as fan duty cycle) can be configured independently from the fan RPM readout. In other words, you can even configure and then detect a non-zero PWM percentage for a disconnected or stopped fan. Thank you for testing the other software. When EVGA's own monitoring software (E-LEET) cannot measure the fan RPM, it means there's definitely something wrong with the sensor chip initialization by the BIOS

We don't have a first-hand experience on switchable graphics notebooks, so I'm not in a position to give you full technical details. What I can tell you though is that AIDA64 is not prepared to handle switchable graphics monitoring in any ways. You can monitor various details of the currently active GPU, but you cannot monitor the inactive GPU, because it shuts down. Regards, Fiery

The relevant fan RPM readout register of the secondary sensor chip shows an invalid RPM value. It looks like it's a BIOS issue -- maybe the BIOS only configures the sensor chips when you enter the BIOS Setup. We'll do more investigation about this issue, and will let you know in this topic if we could implement a workaround in AIDA64.

Clear indication of instability is an unexpected system reset, system freeze (lockup), BSoD, or an error message displayed by the AIDA64 System Stability Test or Windows itself. AIDA64 System Stability Test should drive the CPU constantly at 100% all the time, but when slight drop is detected, it is in most cases caused by a background process. Having no constant 100% CPU load doesn't mean there's anything wrong with your hardware, or with your overclocking settings.

AIDA64 supports multiple BMP images on the G13/G15/G19 LCD screen. You can add a BMP image if you go to Preferences / Hardware Monitoring / LCD / LCD Items, and press the "New BMP" button. The BMP you add may be 320x240 resolution or less, depending on whether you want to add a background wallpaper or just a regular image (e.g. a product logo). Regards, Fiery

I've put a smiley there for a reason. Apparently this topic is not about discussing technical issues anymore, so it's closed.

We indeed fixed one of the issues about the Alerting module, on March 23, 2011. We have a pretty accurate revision history that confirms that. We've done several test runs to assure the bug fix is working. Your issue may be another one, a new one, that the original bug fix didn't solve. If you don't want to help us track down the problem, then please let me know, and I'll close this topic. And once again, I'd like to remind you that this is a friendly forum, and no matter how frustrated you are, you should be more calm and talk more friendly with not just me, but everyone here.

If possible, please phrase your words more carefully and more friendly. I'm here for the sole purpose of trying to help you fix the issues you're having with AIDA64. In many cases a certain issue is not the fault of AIDA64, but due to other pecularities of the system configuration, or due to a misunderstanding of AIDA64 features. I of course understand your pumps are always spinning, although there could be more than 2 pumps in your system, so my question was actually valid, no matter how you interpret it. And my question was more about "Can you see them spinning on the Sensor page?" rather than "Are they actually spinning?". I'm sure you understand the difference between those 2 questions We need to make sure it's not a measurement issue in the first place. Because if for some reason sometimes AIDA64 is unable to measure the pump RPMs, it could easily explain the missing alerting items. Alternative method to check that is verifying that the two pump readings can be selected as an OSD Panel item or Sidebar Gadget item in the Preferences. If those readings are missing from all hardware monitoring modules in the Preferences, then it must be a measurement issue, and not actually an Alerting feature related bug.

No, you don't need to open the Preferences first. What I meant to check is whether your fans are actually spinning before you open the Preferences. Because if not, then those entries will be considered missing (invalid) by the hardware monitoring layer of AIDA64, and they will automatically be removed from the list of available hardware monitor items.

I'm glad it worked out

I'm sorry, but such feature is not available in AIDA64. You can get the very same feature from the Task Manager, actually

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.