Surface Book 3 Throttling at 0.19 GHz

Anonymous
2020-06-08T03:02:54+00:00

Hello,

My 2 week old surface book 3 ( i7-1065G7) is now throttling at a very low speed of .19GHz.  

I have a standard mouse plugged in, and a Microsoft USB-C Travel hub connected.  To the travel hub, i have a 2nd monitor connected via VGA cable.  This system worked well until i plugged in an Ethernet cable to the hub from my router.

I have unplugged the travel hub, and have restarted the computer 2 times now with no luck.

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

104 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-07-10T07:52:35+00:00

    Fully agree, this firmware _seems_ to have fixed the issue. But let's wait for more testing. Some hot days approaching, I'll keep you posted!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-07-09T22:26:38+00:00

    Hi, 

    Also with similar issues, my SB3 13'' is painfuly slow. I simply cannot make a teams call and work at the same time, cpu at 0.2ghz.

    How did you manage to update to 2004 version? I've tried to disable Memory Integrity but update still fails...

    Thank

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-07-07T19:12:51+00:00

    Thanks for the link, the download has the name "SurfaceBook3_Win10_18362_20.051.9924.0.msi" which is the same as I downloaded a month ago, and when I install it, it says I already have the "20.051.9924.0"-update, so that doesn't look like a new July-update...?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-07-07T19:12:24+00:00

    Anyone tried running LatencyMon.  The results for me where exceptionally unimpressive... I spend a lot of my life on Teams (who doesn't these days) and it's basically unusable when on big conferences due to this.  I was getting massive spikes in interrupt to process latency for the NVIDIA drivers... weirdly by forcing Teams to run using the Nvidia card this resulted in DPC sorting itself out... I actually think the issue is the Intel gfx drivers (notorious on machines with a dGPU and Intel iGPU).... not sure why I think this but seem to remember something about the Intel iGPU driver constantly polling the dGPU driver which causes the DPC issues.

    I'd be interested to see if any of you having this issue are also heavy Teams users (or similar e.g. Zoom etc... anything doing voice/video encode/decode and offloading to the GPU to do it) and find that by forcing your Teams (or similar) client to use the dGPU you get better results.  Naff workaround and shouldn't have to be... especially not on a flagship MS branded device!

    ![](https://learn-attachment.microsoft.com/api/attachments/2246c9f9-a429-4c44-90c3-7fcb593ff88d?platform=QnAI'm also interested to know if any of you are seeing not only the throttle down to 0.19ghz issue but also Power Limit Throttling resulting in the CPU being throttled to base frequency.  This is on the i7 32gb 13 inch model.  As you can see from good old Throttle Stop (not doing anything just monitoring... not doing anything as voltages are locked on these things!):

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-07-07T18:54:46+00:00

    Based on my experience after switching from a 13.5" SB2 to 13.5" SB3, the SB3 is significantly faster. Especially in development workloads -> see https://www.hanselman.com/blog/ReviewOfTheSurfaceBook3ForDevelopers.aspx

    I'm currently using 20161 Windows 10, because of WSL2 - I believe that the SB3 runs even faster than on 1909.

    However, if you want to upgrade to 2004 and beyond I have learned that you have to disable Memory integrity in order to allow the Intel graphic drivers to work accordingly. Just use Settings -> Update&Security -> Windows Security -> Device Security -> Core Isolation details -> Memory integrity OFF (until appropriate drivers are available).

    For me the only showstopper was the throttling, which - I still have not seen this since applying the July 3 firmware - leaves the device pretty unusable.

    HTH

    Chris

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments