Fiery

Based on your email address I cannot find your license. In private message please send me your full name, an alternative email address (that you might have used during the purchase process) and an approx. date of purchase, and I will look it up.

None of our benchmarks are memory bound. The PhotoWorxx however relies heavily on the CPU caches, not just the data crunching power of the CPU cores.

But, you can consider going for just a 2nd hand 15-inch of 17-inch LCD monitor as well that you can connect to your PC via DSub, HDMI or DVI, and extend your Windows Desktop on it. Then you can switch from the external LCD module to the AIDA64 SensorPanel.

Not many. One example is BeadaPanel:

The above mentioned new AIDA64 beta is available for download at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.

1) That is usually due to the fact that Intel disables SPD polling on their DP/QP Xeon platforms. AFAIK in such cases only the BIOS Setup (UEFI Setup) can talk to the SPD chip of the memory modules. You can check if other Windows software (like CPU-Z, HWiNFO64, SIV) can obtain SPD information, but I'm 100% sure they won't, since it's due to a platform limitation and not an AIDA64 bug. 2) 15 minutes seems quite excessive, but a shorter delay (1 or 2 minutes) is normal when you use the RAM test with 64+ GigaBytes of system memory installed. It's because AIDA64 allocates most of the system memory in its RAM stress test, and Windows sadly gets slower and slower allocating and locking system memory pages. The more RAM you've got in your system, the more time it takes for a Windows software to allocate the whole system memory. We're working on a new generation of AIDA64 System Stability Test that would use various workarounds to get rid of the responsivity issue while allocating system memory, so soon there will be a cure 3) A 12-channel DDR4-2667 system has a theoretical memory bandwidth of 250 GIgaBytes/sec, but it's a theoretical value that your configuration may or may not be able to provide. In case you deem the actual memory bandwidth you can utilize should be higher than 162 GigaBytes/sec, then make sure to ask Supermicro or Intel about their stance on the issue. We're confident that the AIDA64 version you're using (v6.20) fully supports your platform and provides the right benchmark scores reflecting the true performance of your system.

Well.. It's quite difficult to double-check your theory due to the lack of multi-threaded memory bandwidth benchmark software for Windows But either way, it would be best to populate all available memory channels for optimal performance.

I'm afraid we (the developers of AIDA64) don't know the answer to those, but maybe there're other forum users here who would be able to help you out.

The "CPU" temperature is measured by the onboard sensor chip, while the individual core temperatures are measured by the CPU itself. We consider the core temperatures more dependable and more accurate due to the fact that the CPU measures them for itself, without relying on an external hardware component of the motherboard. We don't have a manual that would explain that, but we're happy to answer your questions here.

I'm glad you've managed to solve it. Especially since most of the Haswell CPU based laptops will throttle no matter what you do about the heat conductor paste...

I'm glad you've managed to solve it. Especially since most of the Haswell CPU based laptops will throttle no matter what you do about the heat conductor paste...

Ah you mean such fluctuation. That cannot happen in AIDA64 because the BCLK is only measured once to avoid collisions between Windows 10 kernel and AIDA64. So the CPU clock speed will be fixed as long as the CPU clock ratio is fixed.

Thank you, we'll check it out.

Have you tried to change the LCD display page on the Aquaero device itself? After activating Aquaero LCD support in AIDA64, you need to select the relevant page on the Aquaero device as well.

That ratio between the read and write memory bandwidth is normal on the type of system you've got.

That is due to a limitation of server-class Intel systems that AFAIK it's not possible to get around. Intel simply puts the IMC (Integrated Memory Controller) of such Xeon processors into a mode that prevents Windows software from polling the SPD chips connected to those IMC's.

Hacking into other software is not something we'd like to pursue.

Please avoid posting a single issue into multiple topics. The fix we've implemented for Asus M4A88TD-M motherboard doesn't apply to other motherboards made by Asus, Dell or others.

In your case, DirectX 12 is the highest installed DirectX version, so it's completely static. Unfortunately showing the currently utilized DirectX (Direct3D) version -- while running a game for example -- would require developing separate plugins for at least D3D9, D3D10, D3D11 and D3D12. Which is quite a challenge and quite a lot of work to detect such information that we deem would only be useful for a handful of AIDA64 users Sometimes the amount of work needed to come up with a new feature makes it only feasable to perform the job when there's a greater demand for it.

Thank you. Maybe the CPU clock is static because you've got all CPU power-saving features (like SpeedStep, C1E, etc) disabled? Maybe the power profile in Windows (or a BIOS overclock setting) dictates that the CPU should be running at a fixed frequency all the time?

No, your computer doesn't shut down because of the unconnected thermal wires of the IT8772 sensor chip. AFAIK there's no way to fix the thermal readings, but they also aren't supposed to cause any issues. If you need further clarification or explanation on the thermal readings or the onboard sensor chip, please try to ask Dell support about it. Only Dell knows why not all the features the sensor chip has to offer are used by the motherboard implementation on XPS 8500.

Yes, AIDA64 v6.20 (latest version) supports all Matrix Orbital EVE2 and EVE3 device variants, including EVE2-50G.

I'm afraid we don't know of a way that is stutter-free and also would keep all sensor readings.

Thank you. It means the Asus WMI ACPI interface fails to provide a meaningful chipset thermal reading. It's most likely due to a BIOS bug that Asus will fix (and soon, hopefully).

We haven't found a reliable way to do that yet.