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
Surface Book 2 GPU Driver disappears randomly after May 2019 update
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
Answer accepted by question author
Anonymous
Answer accepted by question author
Barb Bowman
80,805
Reputation points MVP
Volunteer Moderator
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> |
496 additional answers
Sort by: Oldest
-
Barb Bowman 80,805 Reputation points MVP Volunteer Moderator
2019-10-09T14:35:10+00:00 PS: In production I will NEVER enable the Insider version of Windows. I don't understand how it can be suggested as a solution ...
Not to mention that Eddy does not appear to know which OS builds are in what Insider's ring. 1909 started rolling out in August to Release Preview. Makes me wonder how they even analyze results from "testing" with Insiders. Surface should have their own test/Insiders program. Many of the people already joined to Insiders probably don't even know they are testing Surface firmware.
-
Anonymous
2019-10-09T21:33:52+00:00 Hello. Could you please just simply explain why it is not recommended to update to the beta version? Because I do not understand what the problems will be there if I do this to settle my gpu issue. Please just explain this matter as simple and understandable as you can for me computer idiot. Thank you so much.
-
Anonymous
2019-10-09T21:42:09+00:00 There are probably at least a dozen reasons why. 1) its beta - its not tested / your computer could completely break especially on early beta builds, 2) there could be security issues, 3) software could be incompatible, 4) most companies prohibit running 'beta in production', 5) many vendor / third party contracts prohibit running un-tested/beta software for certain processes, 6) you may not be able to easily switch to non-beta in the future and have to re-install from scratch, 7) certain hardware could be incompatible, 8) Microsoft won't even support beta OS try getting support on your SB2 running beta OS, 9) etc
Its really unacceptable for Microsoft to suggest switching to a Windows Beta build to solve the problem. They should have offered the driver for download by itself to be tested. Methinks they had to tweak some code in Windows and that is why it may not only be an updated driver but also updated Windows required for the fix...