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.
HWINFO detecting wrong RAM frequency info.. ?!
- Thread starter DarkCod3r
- Start date
That could be due to HVCI (Core isolation in Windows): https://www.hwinfo.com/forum/threads/core-frequency-reading-in-windows-11.7537/
Seems like this core isolation thing is related to windows 11. I am using windows 10..
System specs are
I'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.
Anyway, I can see that Hyper-V is active on the system. That could be causing the issue as well.
kindly check the below video and file.. and Hyper V is not active
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...
will try to figure out on my own. thank you
no.. video is working fine..
i shared two links...
this was the video link..
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.
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.
problem solved... i disabled hyper v using cmd using "bcdedit /set hypervisorlaunchtype off".. everything fine now..