Fiery

We'll see

The bug will be fixed in the next AIDA64 stable release due tomorrow

Nothing is perfect, not even AIDA64's System Stability Test

FurMark is quite heavy on GPU stressing -- some say its test is overkill, and allegedly bricked some video cards already. Modern video cards and video drivers have built-in protection against Furmark: http://www.geeks3d.com/20101109/nvidia-geforce-gtx-580-the-anti-furmark-dx11-card/

Most AIDA64 users would want to stress the whole CPU, so the affinity configuration is only for power users. And power users can easily handle a bitmask

Yes, you gotta use a bitmask there. So if you want to use cpu0+cpu1, then the mask has to be 3 (1+2). If you want to use cpu0+cpu1+cpu2, then the mask has to be 7 (1+2+4).

Please try upgrading to the latest beta version of AIDA64 Extreme Edition available at: 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.

How can you tell it's not using the GPU? Have you checked the CPU GT Cores power draw on the Sensor page? OpenGL is not an option for us, simply because via OpenGL it's not possible to stress all GPUs simulatenously. E.g. with an iGPU + discrete GPU (video card) configration, you can only use OpenGL with one of the GPUs, but not with both. Via OpenCL you can stress every GPUs in the system.

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.