Ronharr

Browsing further, I found that VBS is the “culprit “. Now disabled, Aida64 shows all the correct information. will any new version be designed to works when. VBS is enabled? Ron H.

Hi, On my Win 11 "test rig" the Memory Integrity feature is turned off, so I can't see this being a memory integrity issue. Nevertheless, Aida64 (v6.60.5900) is reporting a CPU clock of 946.5 MHz instead of the original 3.7 GHz, which is overclocked anyway to 4.9-5.0 GHz. It is reporting a CPU FSB of 18.6MHz rather than 100 MHZ etc. Consequently, all my benchmarks for memory etc., are completely wrong. It does recognize the default CPUID information accurately. It is also misreporting GPU memory clock, listing its minimum value as 50MHz instead of 405MHz on my RTX 3090 and GPU clock as 210Mhz but does not appear to track it accurately. CPU-Z accurately reports CPU, FSB, and GPU frequencies. Ron H

Hi Fiery, no, this particular problem only happens with the Aida64 benchmarks, Ron

Stability test with FPU only works without problem Ron

Running Aida 6.60.5500 on ASRock Taichi z490, Intel 10700K and MSI Ventus 3X OC RTX3090, Win 10 Pro 64x. My previous configuration differed only in GPU, I was running 2x EVGA 2080ti and Photoworxx benchmark ran without problem. With the MSI GPU, the only system difference, trying to run Photoworxx causes an immediate system restart. Is this a quirk of the new Ampere GPU? Ron H