Surface pro 4 - clock speed of CPU keeps the same

Anonymous
2016-08-03T03:19:10+00:00

After updating to windows 10 (1607), I find that the clock speed of the CPU keeps to be 2.92GHz when plugged, and to be 2.47GHz when using battery. My surface pro 4 has a core i5 CPU. It seems strange because the clock speed of CPU should change with the workload in the Task Manager. Does anyone have the same problem?

Surface | Surface Pro | Display and screen

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2016-08-31T01:11:30+00:00

Fixed with today's update. Thanks, MS!

NOTE: I had to reboot twice after updating. So if anyone is not seeing the fix try a restart.

Was this answer helpful?

0 comments No comments

92 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-08-11T06:06:20+00:00

    I've now installed the Windows 10 Anniversary Update again via normal Windows Updates and the CPU scaling issue appears to be fine now on my SP4 i5. I've checked it's still OK after a few restarts and whether it's on mains or battery power. There were some new 1511 updates installed first so that may have made the difference unless they have changed the anniversary update.

    Edit: A day later and my i5 is stuck at 2.47 GHz again!

    However, I'm still getting the very irritating clicking noise from the CPU area. It very briefly stops when you give the machine something to do but then appears again as soon as the machine is slightly less busy. The best way to describe it is as being like a mechanical hard disk. I'm sure it's far louder a noise than it was before the anniversary update which as I've mentioned I was able to stop with a registry setting preventing certain c-states. Again, this same registry setting no longer stops the noise. I'm going to start a separate thread about this noise.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-08-10T11:46:44+00:00

    M3 stuck at 1.50 GHz. What a bunch of clowns. It makes you wonder why they have these insider previews with months of evaluation and still a major bug like this slips through. How can the Surface team not discover something like this before release? Unfathomable.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-08-09T18:15:50+00:00

    CPU clicking / screeching / buzzing noise?

    When I installed the Windows 10 Anniversary Update on my Surface Pro 4 i5 I noticed two big issues so I rolled it back.

    The first was that the fan was on nearly all of the time which was probably due to the issue this thread is about.

    The second was a clicking / screeching / buzzing noise from the CPU. I've heard this before and was able to resolve it with a registry edit which apparently prevented the CPU from entering certain "c-states" when idle. However, after the anniversary update this noise not only came back but was way louder and audible all the time, certainly not just when the CPU was not busy. In addition, applying the same registry edit that had previously fixed it had no effect after the anniversary update.

    I'm wondering whether the two issues are related. Has anyone else noticed this weird noise from the CPU area (top right when facing the screen)? And have they found that the fix to correct the CPU scaling also fixed this noise?

    Makes you wonder what Microsoft are playing at, how can such issues get through their "testing"?

    I really want to re-install the anniversary update but not until I can be sure these issues are fixed.

    Thanks,

    Andrew

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-08-09T13:32:36+00:00

    It seems a regedit issue, I got an experimental fix from here(https://www.reddit.com/r/Surface/comments/4wfish/progressfix\_for\_the\_anniversary\_update\_cpu/) and it works fine until now, mine is surface book i5/dgpu/256g, hope it works for you

    This seems to have worked for me. Thanks for sharing!

    Was this answer helpful?

    0 comments No comments