Surface Book 2 throttles excessively, often down to 0.4 GHz

Anonymous
2018-05-30T14:41:18+00:00

I've recently purchased a 15" Surface Book 2.

When compiling large projects in Visual Studio 2017, I find that the processor often throttles excessively, often down to 0.4 GHz. As a result, compilation takes several times longer than it does on my 5 year old MacBook Pro. 

The Core Temp app shows that the CPU at this point is at 50-55 degrees Celcius or so.

The following question touched upon this problem, but the proposed solution did not work for me:

https://answers.microsoft.com/en-us/windows/forum/windows\_10-performance-winpc/cpu-clock-speed-sometimes-capped-at-04ghz/315d06ac-a40a-41f8-8314-b370f8b51618

Any ideas on how to fix this?

Thanks.

T

Surface | Surface Book | Power and battery

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

111 answers

Sort by: Most helpful
  1. Anonymous
    2018-11-03T12:46:25+00:00

    Has anyone managed to solve this issue?

    November 2018, brand new SB2 with the same issues.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-11-01T05:58:25+00:00

    Same problem here, and now it is November 2018, Microsoft still ignore our demands to fix this throttle bug. So what the **** were surface book and windows engineers doing during the last half year?

    Maybe I will not buy surface book any more

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-10-06T08:36:26+00:00

    The summer weather is no more and I'm able to run the SB2 without the need for a fan at the moment.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-10-03T07:52:00+00:00

    Yep, could be wrong, but I think it happened right around then.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-10-03T02:00:56+00:00

    Oh right you didn't experience this issues until the spectre/meltdown update? hmm the timing kinda fits.

    Was this answer helpful?

    0 comments No comments