Hi. i am seeing wrong ram frequency info. in cpuz , DRAM frequency never goes down below 1596 but hwinfo detecting 1499Mhz (sometimes 1500Mhz).. Why.?! I noticed this behavior after updating HWINFO.
SS attached.
SS attached.
Seems like this core isolation thing is related to windows 11. I am using windows 10..That could be due to HVCI (Core isolation in Windows): https://www.hwinfo.com/forum/threads/core-frequency-reading-in-windows-11.7537/
Bus Clock of 93.9 MHz is the problem but I'm not sure why this is reported as such.
Please attach the HWiNFO Debug File for analysis.
Debug file linkBus Clock of 93.9 MHz is the problem but I'm not sure why this is reported as such.
Please attach the HWiNFO Debug File for analysis.
kindly check the below video and file.. and Hyper V is not activeI'm sorry but that's the LOG file, not the Debug File. See here: https://www.hwinfo.com/forum/threads/read-this-before-submitting-a-report.241/
Anyway, I can see that Hyper-V is active on the system. That could be causing the issue as well.
kindly check here..Sorry, but it says "The transfer you requested has been deleted."
not sure why it is still not debug even though i did everything as per instructions (can be seen in video). and as you can see in video (which i attached), hyper V is already inactive...Sorry, but that's still not the Debug File. And besides that it says:
Virtual Machine Warning: Microsoft Hyper-V is active. Some results may not reflect real hardware !
no.. video is working fine..I'm sorry but I can't see the video as it also says it has been deleted.
problem solved... i disabled hyper v using cmd using "bcdedit /set hypervisorlaunchtype off".. everything fine now..Oh sorry, I missed that.
For the Debug File - after closing HWiNFO64 you also need to grab the HWiNFO64.DBG file located in its installation folder.
I can also see that on the main screen HWiNFO detects presence of Hyper-V so even though the system says the Hyper-V component is not installed, there must be something else in the system keeping it active. Maybe try to enable Hyper-V and then remove it.