honolulu Posted September 11, 2019 Share Posted September 11, 2019 1- When i enable virtualisation in the bios , i notice that the reported fsb and memory speeds are different than what is set in the bios . For example , i set 3200 mhz ddr4 in the bios and it will report as 3133 in aida64 with an fsb of 97.7 . FSB can not even be changed in the bios as it is always 100 (99.8) on this board . Happens on the 2 latest bios versions being 5204 amd 5216 . Disabling virtualisation in the bios makes aida64 report correct speeds . 2- This particular thing only happens on bios 5216 : Chipset temperature option in aida64 is lost , Custom temp sensor reading option in aida64 is lost , CPU_OPT fan speed is not shown anymore in aida64 . Motherboard is Asus Prime x470 Pro . Quote Link to comment Share on other sites More sharing options...
Fiery Posted September 11, 2019 Share Posted September 11, 2019 8 minutes ago, honolulu said: 1- When i enable virtualisation in the bios , i notice that the reported fsb and memory speeds are different than what is set in the bios . For example , i set 3200 mhz ddr4 in the bios and it will report as 3133 in aida64 with an fsb of 97.7 . FSB can not even be changed in the bios as it is always 100 (99.8) on this board . Happens on the 2 latest bios versions being 5204 amd 5216 . Disabling virtualisation in the bios makes aida64 report correct speeds . 2- This particular thing only happens on bios 5216 : Chipset temperature option in aida64 is lost , Custom temp sensor reading option in aida64 is lost , CPU_OPT fan speed is not shown anymore in aida64 . Motherboard is Asus Prime x470 Pro . 1) With both virtualization settings, 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, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. 2) With BIOS 5216 right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. 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, or attach the results as a TXT file to your post. Quote Link to comment Share on other sites More sharing options...
honolulu Posted September 11, 2019 Author Share Posted September 11, 2019 All 3 requested dumps attached . ecdump.txt cpuidmsrdump.txt isasensordump.txt Quote Link to comment Share on other sites More sharing options...
Fiery Posted September 12, 2019 Share Posted September 12, 2019 18 hours ago, honolulu said: All 3 requested dumps attached . ecdump.txt 2.09 kB · 0 downloads cpuidmsrdump.txt 65.93 kB · 0 downloads isasensordump.txt 15.9 kB · 0 downloads Thank you. Please repeat #1 with virtualization disabled, so we can compare the CPU registers output against the "virtualization = enabled" state. As for issue #2, try to enable Asus WMI sensor support in AIDA64 / main menu / File / Preferences / Stability. Quote Link to comment Share on other sites More sharing options...
honolulu Posted September 12, 2019 Author Share Posted September 12, 2019 #1 see attachment #2 it is already enabled . so i can not enable enable it see list of what's enabled (stability.png) cpuidmsrdump_virtualisation disabled.txt Quote Link to comment Share on other sites More sharing options...
Fiery Posted September 16, 2019 Share Posted September 16, 2019 On 9/12/2019 at 4:54 PM, honolulu said: #1 see attachment #2 it is already enabled . so i can not enable enable it see list of what's enabled (stability.png) Thank you. Everything looks fine there. I think with virtualization enabled, the APIC clock runs slower than the BCLK for some reason. Maybe because APIC is virtualized then as well. As for the missing sensor readings, in the case the rest of the readings are there, and AIDA64 uses the Asus WMI interface, it is then due to a BIOS bug. Quote Link to comment Share on other sites More sharing options...
honolulu Posted September 16, 2019 Author Share Posted September 16, 2019 It could very well be some bugs in the bios . I also notice a 10% performance drop in 3dmark firestrike with virtualisation enabled in the bios . I don't think that's normal either . 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.