Fiery

Exactly. Some hardcore overclockers swear by using 3 to 5 instances of Internet Explorer or Mozilla, and simply browse the web in them on heavy Flash utilizing sites. They say it sometimes gets such issues come up that no other stability testing methods can.

Please let us know more about your hardware configuration. Motherboard model, CPU type, any external drives connected (USB, FireWire, eSATA), any RAID arrays defined? If no RAID, then what kind of AHCI driver do you have installed? You seem to have multiple ATI/AMD GPUs, what video cards are there exactly? Any APUs or integrated video chips? Make sure to use the latest AIDA64 beta version for further test runs: http://www.aida64.co...47lcsxfgtjmzzip Please also try to right-click on the bottom status bar of AIDA64 main window --> HWMon Modules --> GPU. That will effectively disable GPU monitoring, so you can see if it is the GPU monitoring that causes AIDA64 to "eat up" one of the logical processors and fall into an infinite loop. Let me know if it helps. Thanks, Fiery

The gadget will be updated in the next beta. We'll also remove APIC clock measurement in the next AIDA64 beta, since that -- under Win8 Consumer Preview -- causes issues with CPU core clock measurement and benchmark results calculation as well. A bit more things have changed between Win8 Developer Preview and Win8 Consumer Preview than we expected. Who knows, maybe the Win8 Release Candidate will revamp even more things internally, on the Windows kernel level... Anyway, I'll post a message into this topic once the new AIDA64 beta is available.

Yes, I'm afraid a slight issue has slipped into Build 1847 about that. It sometimes works, but other cases it fails. We'll fix that in the next AIDA64 beta release. Thanks, Fiery

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

AIDA64 detects NOD32/ESS version by checking the version number of EGUI.EXE. If that fails, it will detect version using the Registry path: HKLM\Software\Eset\Eset Security\CurrentVersion\Info\ProductVersion I guess one of those places contain an incorrect product version. It's not the fault of AIDA64, but a slight mistake by Eset. Regards, Fiery

Thank you for the feedback

We've just released a new AIDA64 beta with the updated gadget: http://www.aida64.com/downloads/aida64extremebuild1847lcsxfgtjmzzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

Thanks for the info. It's quite odd that noone else (out of those users you mentioned) reported this issue to us. And stating that all of them face this issue is even more odd... Just to clarify: if you start AIDA64 on such notebooks with its default settings (so OSD Panel not activated, Sidebar support not activated), and you just leave it sitting on the main screen, does it still lock up after a while?

Does it lock up while it is measuring some sensor values? In other words, do you have such features like the OSD Panel, Logitech LCD, Vista Sidebar, Logging, Alerting, SensorPanel, or External Applications activated?

Please post a screen shot that shows all settings of the Stability page (AIDA64 / main menu / File / Preferences / Stability). Also, right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic. Finally, right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic. Thank you for your time.

AIDA64 fully supports the Core i7-2700K processor. Please start Task Manager (e.g. by using the Shift+Ctrl+Escape key combination), click on the Performance tab, and count the number of logical processors in the CPU Usage History box. There should be 8 graphs there, associated with the 8 threads your processor supports. If you can see less than 8 threads there, then it means one or more of the CPU cores are disabled in the BIOS Setup. Alternatively, you can check in the BIOS Setup whether core disabling is activated there. Regards, Fiery

Thanks for the feedback

Please send me your full name and email address in private message to me. I'll find your key and send it to you. Regards, Fiery

Thank you. Please note down all voltage values you can see on the PC Health Status page in the BIOS Setup, and copy the values here. Also, please start AIDA64, right-click on the bottom status bar of its main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. Thanks, Fiery

CPU VID and NB VID are shown on the Computer / Overclock page. They aren't measured values, but detected values, hence they don't fit on the Sensor page. DRAM Voltage can only be shown if it is a sensor reading. Did you see that value on the PC Health Status or HW Monitor page in the BIOS Setup? I'm sorry, but we have no plans on making a DLL or other component just to read sensor information. Compared to how much system memory modern computers have (typically 2GB or more), the memory footprint of AIDA64 is negligible (less than 1 or 2 percent). Regards, Fiery

It's normal. When AIDA64 is not running, the default Blue colour schema is used.

We're currently working on improving the AIDA64 Sidebar Gadget. You can develop your own gadget that has advanced features, but I'm afraid due to intellectual property rights and other boring legal issues we cannot use external components in our software

It means you haven't upgraded to the latest AIDA64 beta available at: http://www.aida64.co...39s1y6ftjhwkzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. With that beta a new UPS entry should be available among the HWMon Modules.

If you have the GPU module enabled, but the UPS module disabled, then do you get latency issues?

Thank you for the feedback. Just disabling the UPS module didn't solve the latency issues, did it?

Please note that Turbo is engaged so quickly, and for such a small amount of time, then it is possible that for the fraction of time AIDA64 (or CPU-Z) measures the CPU clock the processor switches up to Turbo clock, and while Intel's tool measures the clock it switches back to non-Turbo clock. Even though it looks as if those tools work in parallel and measure the very same things, all those low-level clock measurements are done exclusively, without multi-tasking, for a very short amount of time. It's not easy to explain all that without using deep technical terms. The whole point of Turbo Boost and other performance enhancement and power saving "magic" of Nehalem and later Intel processors are designed to work very fast, by switching clock speeds in a fraction of a second. Hence the CPU can adjust to the necessary workload with an extreme response time.

Thank you. We have different plans about the System Stability Test, which involves a complete redesign of the user interface, and also to make it easier to use while retaining the current layout with improvements. Stay tuned

Thank you, we'll fix that in the next AIDA64 beta release. It works fine in IE 9.0 and Chrome 17 for me. What web browser do you use? Thanks, Fiery

In order to find out whether it's a gadget-related issue or a flaw in AIDA64's engine, please check the UpTime on the Operating System / Operating System page of AIDA64 as well. Let us know what can you find out.