- Jun 30, 2004
- 16,429
- 1,933
- 126
I continue to use a utility called HWINFO64, still offered as a freeware download.
The computers -- I have one system with ASUS mobo, Z170 chipset and Kaby Lake CPU -- configured to Win 11 Pro. The other system has the WS version of the Asus Z170 board and a Sky Lake CPU.
The Sky Lake system is still running Windows 10 Pro -- assured for updates with the ESU subscription.
The Kaby Lake system received a successful installation of Windows 11 Pro using a single registry hack, and appeared to be running just fine, getting updates and so forth.
Now I look at how the voltages and processor speed(s) rise and fall. ALL of the "Tweaker" settings for both motherboards are identical. I had applied "Auto" option to the same settings, notably "Multi-core enhancement" and the feature that allows cores to be synched. The only fixed settings for both boards/processors were the DRAM voltage and VCCIO voltages, because I'm using G.SKILL DDR4 3200 RAM kits in both systems -- one using the TridentZ model and the other using the Ripjaws. But the RAM and its settings wouldn't affect the behavior I'm about to describe.
On the Windows 10 Sky Lake system, the VID and speed (Mhz) readings vary as we'd come to expect from a time just a year or two after the release of the processor and chipset.
On the Windows 11 Kaby system, the VID stays parked at 1.22V (plus or minus a sliver), and 4400 processor speed.
First, has anyone else noticed the difference in the Win 10 and Win 11 treatment of nearly identical systems? Second, realizing that some overclockers override the EIST and other features that allow the voltage and speed parameters to vary according to their specs, what are the implications? And why would the OS treat the processor differently, except of course that these two models just preceded the Coffee Lake -- which was the earliest processor in the Windows 11 "eligible" list.
Hyperthreading is turned on for both processors, and there are eight "processors" which show up under Device Manager's "CPU" item -- reflecting the HT. At this point, I am ABSOLUTELY SURE that EIST is enabled in the BIOS for both systems, but I will check again.
One more thing I might do is run the update on HWINFO64, having downloaded the installation file.
UPDATE: DONE THAT. NO CHANGE. The Kaby and Sky processors should behave the same. I checked the EIST and other settings, but they are identical between the two systems.
SO AGAIN! Anyone else -- if you were equipped to notice this -- DID you notice it? And also again -- what are the implications? Perhaps I should revert to using Windows 10 on the Kaby system, but it is otherwise behaving just fine. The temperatures are what you would expect, even if the CPU speeds are all "stuck" at 4,400 for all four cores.
The computers -- I have one system with ASUS mobo, Z170 chipset and Kaby Lake CPU -- configured to Win 11 Pro. The other system has the WS version of the Asus Z170 board and a Sky Lake CPU.
The Sky Lake system is still running Windows 10 Pro -- assured for updates with the ESU subscription.
The Kaby Lake system received a successful installation of Windows 11 Pro using a single registry hack, and appeared to be running just fine, getting updates and so forth.
Now I look at how the voltages and processor speed(s) rise and fall. ALL of the "Tweaker" settings for both motherboards are identical. I had applied "Auto" option to the same settings, notably "Multi-core enhancement" and the feature that allows cores to be synched. The only fixed settings for both boards/processors were the DRAM voltage and VCCIO voltages, because I'm using G.SKILL DDR4 3200 RAM kits in both systems -- one using the TridentZ model and the other using the Ripjaws. But the RAM and its settings wouldn't affect the behavior I'm about to describe.
On the Windows 10 Sky Lake system, the VID and speed (Mhz) readings vary as we'd come to expect from a time just a year or two after the release of the processor and chipset.
On the Windows 11 Kaby system, the VID stays parked at 1.22V (plus or minus a sliver), and 4400 processor speed.
First, has anyone else noticed the difference in the Win 10 and Win 11 treatment of nearly identical systems? Second, realizing that some overclockers override the EIST and other features that allow the voltage and speed parameters to vary according to their specs, what are the implications? And why would the OS treat the processor differently, except of course that these two models just preceded the Coffee Lake -- which was the earliest processor in the Windows 11 "eligible" list.
Hyperthreading is turned on for both processors, and there are eight "processors" which show up under Device Manager's "CPU" item -- reflecting the HT. At this point, I am ABSOLUTELY SURE that EIST is enabled in the BIOS for both systems, but I will check again.
One more thing I might do is run the update on HWINFO64, having downloaded the installation file.
UPDATE: DONE THAT. NO CHANGE. The Kaby and Sky processors should behave the same. I checked the EIST and other settings, but they are identical between the two systems.
SO AGAIN! Anyone else -- if you were equipped to notice this -- DID you notice it? And also again -- what are the implications? Perhaps I should revert to using Windows 10 on the Kaby system, but it is otherwise behaving just fine. The temperatures are what you would expect, even if the CPU speeds are all "stuck" at 4,400 for all four cores.
Last edited:
Facebook
Twitter