Fiery

Maybe it's because the sensor polling requires cca. 2 seconds to complete on your current system. Which is quite unusual, and would usually mean there's a particular sensor component in your system that can provide sensor readings to AIDA64 very slowly. It would be necessary to know more about your system, and the difference to the previous system: 1) Do you have any RAID arrays defined? Did you have before? 2) Do you have any external storage devices (either USB, eSATA or FireWire) or special sensor devices (via USB) connected? Did you have before? Have you tried to disconnect them? 3) What Windows version do you have installed? What was on your previous system? 4) What video card(s) do you have? Do you have the same than before? Thanks, Fiery

In Beta Build 2622 we've adjusted the RAID enumeration module to give the Intel RAID enumeration part more priority. It helps in a few cases, but it seems in your case it made things worse. We'll need to re-adjust the RAID enumeration, based on the following data of your system: 1) Please let me know what HDD/SSD drives do you have in your system, which one is connected to which SATA controller, and whether those controllers are in IDE, AHCI or RAID mode. 2) What motherboard do you have? Which Windows variant? 3) Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> ATA Dump. Copy-paste the full results into this topic. 4) Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic. Thanks, Fiery

Thank you for the feedback

Ah now I know what it is You have the hardware monitoring item called External IP Address in use. In order to detect your external IP address, AIDA64 needs to ping an internet server that sends the external IP address back to AIDA64. We use our auto-update server for that purpose as well. It's a similar service that others provide at e.g. http://whatismyipaddress.com/ or http://www.whatsmyip.org/ If you prefer AIDA64 not to communicate with any internet servers, then you need to disable the External IP Address hardware monitoring item.

Thank you for the feedback

Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2622dmr7jqwpnyzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2622dmr7jqwpnyzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

We've tried it with KIS 2013, and neither TCPView or KIS built-in Network Monitor tool could register any network traffic done by AIDA64 when the auto-update feature was disabled. Can you please check it with KIS Network Monitor as well? And make sure to double-check if the auto-update feature is disabled in AIDA64 Preferences.

Thank you for your feedback, I'm glad you've found the root cause of the anomalies

Thank you for the screen shots. It's quite surprising to see such results. But since you've stated that in other software (WinRAR) -- that happens to be latency and cache sensitive -- you can also see a drop of performance, it must be the Windows 8 kernel that does things a bit differently on your system. BTW, you mentioned you've got 3 memory modules in your system. Have you tried to install just 2 identical modules, in the favorable (primary) DIMM sockets, just to make sure there's an optimal dual-channel operation for your motherboard? I wonder what sort of performance would you get with such changes.

That sounds quite odd. Can you please copy-paste the full content of the Motherboard / CPU page of AIDA64 into this topic?

Please refer to the two PDF manuals published here: http://www.aida64.com/downloads/aida64business320zip In case you've got additional questions after going through those manuals, please let me know in this topic.

Windows 8 shouldn't have such an impact on system performance. It could either be that your hardware configuration/setting has changed somehow (due to a BIOS update for example) between the two operating systems. Can you please post a screen shot of the Cache & Memory Benchmark Panel, showing all system parameters and all memory/cache benchmark results? (under Windows 8)

What version+build of AIDA64 are you using? Did you use the same AIDA64 version under both operating systems? Thanks, Fiery

Just to make sure it's not a bug in AIDA64 that is related to KIS, please let us know the KIS version+build you currently have installed. We'll try to reproduce the issue on our test systems. Please also let me know if you have the traffic to our update servers indicated by TCPView only once a day, or every time you launch AIDA64 by starting AIDA64.EXE?

It means avp.exe was trying to probe the AIDA64 update server. It's not AIDA64 -- which would have the process name of aida64.exe. We've checked it with TCPView, and no traffic was detected between AIDA64 main process or any other components and any internet hosts/servers when the auto-update feature is disabled in AIDA64 / main menu / File / Preferences / General.

If you want to stress your processor's thermal capabilities (to check whether its cooling is adequate), you should only use the FPU subtest and nothing else. Otherwise, if you would like to check your system's overall stability, then you can enable all subtests. Let it run for at least a few hours to make sure your system gets warmed up properly Modern Intel processors have a built-in facility to prevent overheating and physical damage, even when the processor is under an extreme load -- like the FPU subtest of AIDA64 System Stability Test Additionally, most system BIOSes also have a feature that shuts the system down automatically if the overall case temperature gets too hot.

Do you have the 2 RAID-related options enabled in AIDA64 / main menu / File / Preferences / Stability? Thanks, Fiery

AIDA64 Extreme Edition was a single product, but you could either purchase a license for home use, or a so-called Engineer License. The Engineer License would entitle you to use AIDA64 Extreme Edition for business purposes, e.g. troubleshooting or diagnostics in a corporate environment. At the next AIDA64 update we're forking AIDA64 Extreme Edition into two products: AIDA64 Extreme will be the same product that previously the Extreme Edition was (it just got renamed). The new AIDA64 Engineer will be a brand new product based on AIDA64 Extreme. The Engineer product will have a few additional features useful for hardware technicians, but nothing groundbreaking. Note that the "Edition" word is dropped from the product names.

We've tested it, but with disabled automatic updates (that you screen shot reflects) AIDA64 doesn't perform any network traffic to our update servers. Your screen shot shows avp.exe, and not aida64.exe, maybe that's the difference?

Have you tried it with the latest AIDA64 beta release? http://www.aida64.com/downloads/aida64extremebuild2613qm7ngcy8lkzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

That's another issue that we have to fix. It will be resolved in the next AIDA64 beta release due next week

Thank you for the feedback

Yes, it is still on our roadmap

Updating your video driver may well have caused the difference. I suppose the old driver didn't enable (didn't activate) the Optimus feature.