Fiery

You can set the CPU afffinity for the AIDA64 System Stability Test (SST) if you press the Preferences button in the SST window --> General --> CPU Mask --> Manual. You can enter the mask in a decimal or hexadecimal format (e.g. 0xFF). Make sure to use the latest AIDA64 beta release: http://www.aida64.com/downloads/aida64extremebuild2594k7t3njqszhzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

How many OpenCL devices are reported on the Display / GPGPU page of AIDA64? And which ones are those?

We may add that there, but as I mentioned above, this is an experimental feature so far. We'll need to test it more before making it an official feature.

System Stability Test doesn't support that, but you can design a SensorPanel layout (using graphs) that can do that Regards, Fiery

In which window would you like to see those readings?

We've checked it, and it seems it's quite complicated to determine the WDDM driver compliance. We have to come up with several code paths, e.g. one for WDDM 1.3, one for WDDM 1.2, etc. We'll work on it soon Thanks, Fiery

I'm sorry, I forgot to mention that you have to use the latest AIDA64 beta release: http://www.aida64.com/downloads/aida64extremebuild2594k7t3njqszhzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

It may be because your drive reports two different firmware dates via SPTI Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> ODD SPTI Dump. Copy-paste the full results into this topic. Thanks, Fiery

We have an experimental feature in AIDA64 called CPU Clock Monitor. You can start it by right-clicking on the bottom status bar of AIDA64 main window --> CPU Clock Monitor. Please note that it uses a clock measurement method that isn't compatible with all systems out there. If you get a blank window, it means your system isn't compatible with the CPU Clock Monitor. Regards, Fiery

You can download the previous AIDA64 versions from: http://www.aida64.com/downloads/aida64extreme285exe (AIDA64 v2.85) http://www.aida64.com/downloads/aida64extreme280exe (AIDA64 v2.80) http://www.aida64.com/downloads/aida64extreme270exe (AIDA64 v2.70)

Thank you for the data. I'm afraid your tablet doesn't implement a sensor solution that would be compatible with existing AIDA64 sensor modules It may be possible to measure fan RPM via an ACPI call, but we've got no documentation on the ACPI layout of your system Regards, Fiery

1) 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. 2) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. 3) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic. Thanks, Fiery

Please try to reinstall AIDA64, and in the same time upgrade to the latest beta release: http://www.aida64.com/downloads/aida64extremebuild2594k7t3njqszhzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery

Thank you for the feedback

What kind of GPU is your GPU1 and GPU2 GPUs?

I'm sorry for the late reply. I'm afraid we haven't yet been able to come up with a proper rendering to display a hovering bubble over the SensorPanel We'll keep trying.

Quite frankly, we've never seen such anomaly. All benchmark scores seem to be in line with the expected performance from an oveclocked 3770K, except for the AES score. If possible, please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic. That data will hopefully reveal something about your CPU that could explain the AES anomaly.

The current multiplier the CPU is running at may be difficult to measure ot detect. For example, at idle it may be running at 45x, under partial load (like running a game) it may be working at 42x, while under full load it may switch down to 40x or so because of power (TDP) limits. Turbo Boost is a very complicated technology in modern Intel processors BTW, between BIOS updates such settings like max. Turbo Boost multiplier or power limits may change.

Haswell processors tend to reach very high temperatures under heavy load, and in many cases they start to throttle. It's a drawback that comes from the combination of the FIVR (integrated voltage regulator) and the inadequate heat dissipation from the CPU core to the heatspreader. In case you want to test your CPU for maximum thermal stress, then only enable the FPU subtest in the AIDA64 System Stability Test, and disable the rest of the subtests.

Thank you for the feedback We'll roll out a new update for Business Edition soon

1) What version of AIDA64 are you using? 2) Are you sure your CPU isn't throttling (slowing itself down) while running the benchmarks, due to overheating?

91 Celsius is quite high for a CPU, and throttling activity (be it 0% or more) is never good. BTW, 0% throttling means "sub-1%" throttling, so it's still a bit amount of throttling. If it's possible, you should definitely try to improve the cooling of your system. Regards, Fiery

In that case the lag you're experiencing is just the usual lag because of the heavy load AIDA64 System Stability Test puts on the computer. The stress test module uses up all available system resources, that's normal.

The Windows UI elements lagging is caused by ForceWare video drivers. ForceWare slows down quite a bit once you put a heavy load on the GPU via OpenCL GPGPU code. So what you are experiencing on your system is absolutely normal. I suppose the work computer you mentioned has no nVIDIA GPU. Regards, Fiery

1) & 2) On which page of AIDA64 do you miss those information? 3) On your system it's not possible to measure Vcore via direct CPU VID detection or via a classic sensor chip register readout. As for DMI, please check Q#10 at: http://www.aida64.com/support/knowledge-base 4) It's because there's no classic sensor chip in your system. IPMI Sensor is not supported by the AIDA64 hardware monitoring module. 5) Thank you, we'll fix that. 6) Changing between IPMI subdevices causes that. It comes from the logic how AIDA64 hardware detection engine works, but we'll check if it's possible to improve on it. Thanks, Fiery