Fiery

1) The "Unknow" is part of what your BIOS provides under the DMI spec. Please see Q#10 at: http://www.aida64.com/support/knowledge-base 2) The 100% GPU duty cycle is provided by the video card itself, and such weird values are normal when the video card has no fan connected. 3) As for the CPU temperature, maybe the temperature labelled as "Aux" is the actual CPU temperature on your motherboard. Can you please check what happens to the 3 temperatures measured by your motherboard ("CPU", "Motherboard" and "Aux") once you start to load the processor? You can use e.g. AIDA64 System Stability Test to load the processor: go to AIDA64 / main menu / Tools / System Stability Test, uncheck all tests except for "FPU", and press the Start button. Follow the temperatures on the Sensor page, and let us know what conclusion can you draw out of that. Based on your test, we can adjust the temperature labels on the Sensor page. Thanks, Fiery

The new layout will allow not only multiple columns, but absolutely dynamic items placing. You can arrange them into 20 columns and 50 rows if you want We'd like to roll this out sometime in April, but don't take this as a promise It will be announced when it's ready -- although we'll roll it out as a beta feature sooner than that.

It seems your video card cannot monitor fan RPM, but only the fan duty cycle percentage (%). Regards, Fiery

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. Thanks, Fiery

Thank you, we've fixed that in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1314v5slkdn2mxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Instead of improving the OSD, we've already been working on a brand new, very flexible and highly customizable monitoring feature that we mentioned here: Regards, Fiery

We consider our solution more flexible and at least as dependable as OCCT and Prime95. Our System Stability Test is very unique, since it uses specific optimizations and adjustments for all modern CPU cores, including full AVX acceleration on capable Intel Core processors (codenamed "Sandy Bridge"). In case you want to put the most stress on the processor, and to heat the system up the most, then you should only have the "FPU" test enabled, and the rest of the tests disabled. However, if you want to reveal possible hardware flaws, you should also try running the test with all tests enabled. Running the test for at least 12 hours is recommended. You can still use the computer while running the test, just make sure to prepare yourself for any unexpected system restarts -- in case the system may be unstable.

That's a BIOS bug. Please check Q#10 at: http://www.aida64.com/support/knowledge-base Regards, Fiery

Thanks for the feedback. You may want to try switching the option "nVIDIA GPU SMBus access through nVIDIA ForceWare" in AIDA64 / main menu / File / Preferences / Stability. Maybe by disabling that you can re-enable the GPU module to get back GPU temperatures and voltages again. Let me know how it went.

Yes, it is still supported. There were no features removed.

Can you please show us how your settings on the Preferences / General and Preferences / Layout pages look like? Thanks, Fiery

That is due to a BIOS bug. What version of DX58SO BIOS do you have in your motherboard? Thanks, Fiery

There's a chance the lag is caused for both of you by ForceWare drivers, while AIDA64 tries to monitor your video cards via ForceWare driver calls. Please try to disable the GPU module by right-clicking on the bottom status bar of AIDA64 main window --> HWMon Modules --> GPU. You can enable and disable that module (or any of the other modules as well, if you'd like to do some more experimenting about this matter) on-the-fly while you keep AIDA64 running. Please let me know what can you find out, and also what version of nVIDIA ForceWare drivers do you both have installed. Thanks, Fiery

You need to backup the AIDA64.INI file that you can find in the AIDA64 installation folder.

The lag is caused by the Intel Rapid Storage Drivers. In fact, the lag occurs in the code of those drivers, so we cannot fix it from AIDA64. But you can disable RAID SMART support in the latest AIDA64 beta (in main menu / File / Preferences / Stability): http://www.aida64.com/downloads/aida64extremebuild1306w6ekj1ycvnzip

There's no way to check that from a software, unless you can connect an ExpressCard. I don't think it is mapped in any way, but you may want to check the list of devices on the Devices / PCI Devices page in AIDA64. Maybe the port replicator has a reference there...

Thank you for the feedback

The fact that the OS version is reported as v5.1.2600 definitely suggests that some kind of compatibility mode is activated for the AIDA64 process. I'm not sure why is that though...

Maybe AIDA64 is running in XP compatibility mode?

We've fixed the issue about SMART stability option not affecting the RAID SMART layer. We've also implemented a new, separate option to let you disable only the RAID SMART functions. That way, you can have SMART readout for non-RAID drives, and only disable the SMART readout for RAID array member drives. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1306w6ekj1ycvnzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

AIDA64 settings, including LCD configuration is stored in the AIDA64.INI file in the installation folder of AIDA64. You can backup that file to save your settings.

We may implement graphs for the OSD and LCD features later this year. Until then, you can track sensor values on a graph using the System Stability Test feature of AIDA64. Regards, Fiery

When ACC (Advanced Clock Calibration) is enabled, core temperature measurement is not possible. It is a hardware shortcoming that we cannot fix from AIDA64

In order to correct the measured core temperatures, you may want to adjust the TJMax temperature to a different value in AIDA64 / main menu / File / Preferences / Hardware Monitoring. Regards, Fiery

Does your Windows user have administrator privileges? AIDA64 needs administrator privileges to perform low-level hardware detection. If privileges are no problem, then please try to reinstall AIDA64.