Surface Book 2 GPU Driver disappears randomly after May 2019 update

Anonymous
2019-05-26T20:23:51+00:00

Hi, just recently installed the Windows 10 May update on my Surface Book 2. Now the GPU disappears randomly while in use. The only solution is to reboot the Surface Book 2, or go into the device manager and initiate a scan for the GPU to come back again. It has Nvidia Gforce GTX 1050 version 23.21.13.9140

Are there any plans for Microsoft to release an updated driver to fix this bug?

Surface | Surface Book | 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
2019-07-12T22:43:37+00:00

Thank you for reporting the issue. A fix is available through Windows Update.

For more information, please visit our Surface Book 2 Update History page.

Eddy

updated: 10/11/2019

Was this answer helpful?

7 people found this answer helpful.
0 comments No comments
Answer accepted by question author
Barb Bowman 80,805 Reputation points MVP Volunteer Moderator
2019-10-11T16:52:35+00:00

There are some updates that were pushed to PRODUCTION today https://support.microsoft.com/en-us/help/4055398/surface-book-2-update-history You do NOT need to join Insiders to get these.

October 2019 updates

The following updates are available for all Surface Book 2 devices running Windows 10 April 2018 Update, version 1803 or greater:

Windows Update History Name Device Manager Name
Surface – System – 1.75.139.0 Surface Base 2 Firmware Update – Firmware<br><br><ul><br><li><span><span><span><span><span>1.75.139.0 <span>improves battery stability.</span></span></span></span></span></span></li></ul>
Surface – Firmware – 182.1004.139.0 Surface System Aggregator – Firmware<br><br><ul><br><li><span><span><span>182.1004.139.0 resolves an issue where the CPU will throttle down to .4GHz, and <span>improves battery stability.</span></span></span></span></li></ul>
Surface – Firmware – 389.2837.768.0 Surface UEFI – Firmware<br><br><ul><br><li><span>389.2837.768.0 resolves an issue where the display adapter disappears from Device Manager.</span></li></ul>

Was this answer helpful?

5 people found this answer helpful.
0 comments No comments

496 additional answers

Sort by: Most helpful
  1. Anonymous
    2019-10-10T11:37:16+00:00

    Eddy's original response was in July, but it was updated a few days ago with this new information.

    Was this answer helpful?

    0 comments No comments
  2. Barb Bowman 80,805 Reputation points MVP Volunteer Moderator
    2019-10-10T10:00:32+00:00

    JayJay,
    With all due respect, there are customers who don't have the skills to deal with
    pre-release software. The other piece is that Microsoft won't support
    pre-release builds of Windows on Surface in this Forum AND should a customer
    call support with ANY problem on a non released version of Windows, they are
    told to reimage back to a released, supported version.
    While this is a catch 22 in this context, many business users will want to stay
    on 1809 or even 1803 for some time to come and if Microsoft is testing in
    release preview, they have no test data on current production builds, and it is
    not clear if there is an OS dependency for the firmware fixes (which would
    create some issues for these customers).
    I'm very happy that the release preview route is a good fit for your situation
    and for others who feel it is appropriate.
    My concern is that Microsoft did not properly frame their "answer". They wrongly
    stated that Release Preview would keep them on their current version of Windows
    and only give them drivers and firmware. And that pre-release versions of
    Windows are not officially supported through regular channels. Nor did they
    state it was for more advanced users who understood these and other risks.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-10-10T09:36:29+00:00

    Eddy's advice was dated July; with a Windows Update fix "coming soon".

    Does anyone know, has it since been subsumed in any 'standard' Windows update?

    Was this answer helpful?

    0 comments No comments