bulbau Posted October 22, 2021 Share Posted October 22, 2021 hello, having updated my aida 64, my frequencies on the cpu and the ram are not correct, version Win 11 pro and aida 64 with valid license key. what can I do to fix the problem? thank you. ps: sorry to use a translator, but i don't speak english. Quote Link to comment Share on other sites More sharing options...
bulbau Posted October 22, 2021 Author Share Posted October 22, 2021 Re, CPUID & MSR Dump text provided cpuidmsrdump.txt Quote Link to comment Share on other sites More sharing options...
usm22 Posted October 24, 2021 Share Posted October 24, 2021 Same issue on my Core i5 10400F. Because of not detecting correct clock speeds, the latency is huge, above 200 ns. With old version, everything is fine and latency is correct as well. Quote Link to comment Share on other sites More sharing options...
usm22 Posted October 24, 2021 Share Posted October 24, 2021 Difference of latency and memory read/write between old and new version. Quote Link to comment Share on other sites More sharing options...
Arctucas Posted October 24, 2021 Share Posted October 24, 2021 I wonder if it is W11 causing the issue? My 9900K CPUID (on the right) screen side-by-side with yours, but I am running W7: Quote Link to comment Share on other sites More sharing options...
Arctucas Posted October 24, 2021 Share Posted October 24, 2021 Looking around the interwebz, seems others are having issues with monitoring software, e.g.CPU-Z, HWiNFO, using W11. You know Microsoft's motto is; 'If it ain't broke, fix it 'til is.' Quote Link to comment Share on other sites More sharing options...
Fiery Posted October 25, 2021 Share Posted October 25, 2021 19 hours ago, Arctucas said: Looking around the interwebz, seems others are having issues with monitoring software, e.g.CPU-Z, HWiNFO, using W11. You know Microsoft's motto is; 'If it ain't broke, fix it 'til is.' It's indeed because of Windows 11. It uses sandboxing which prevents several low-level calls that would be required to measure BCLK properly on certain Intel processors like Skylake, Kaby Lake, Coffee Lake, and Comet Lake. We haven't found a proper workaround or fix yet. What works is to disable Memory Integrity in Windows Settings / Security. Quote Link to comment Share on other sites More sharing options...
bulbau Posted October 26, 2021 Author Share Posted October 26, 2021 the problem is that the integrity of the memory is already disabled ... Quote Link to comment Share on other sites More sharing options...
Casidy Posted October 29, 2021 Share Posted October 29, 2021 The problem is with VBS (virtualization based security). You can verify that by using "msinfo" utility (just search "msinfo" in start menu). Long story short, if you have enabled "Virtual machine platform" (which is an additional windows feature needed for WSL2 for example), most probably this feature (VBS) is also running. Once turned off, AIDA benchmark works fine. Quote Link to comment Share on other sites More sharing options...
usm22 Posted November 6, 2021 Share Posted November 6, 2021 Working fine now. Showing correct readings and latency is also correct. In my case, I've to disable Windows Sandbox feature to fix this issue. If Windows Sandbox is enabled, VBS will run irrespective of the state of memory integrity. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.