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: Most helpful
-
Anonymous
2019-09-25T18:08:49+00:00 Where can I find the build to re-install old version.
I Just cant believe the bad luck I got, I bought this when attended GDC on March and I spent two weeks in San Francisco, tested the device and was really good, performance on the 1060 GPU not as fast as other laptop with similar graphic card, but really close.
Im from Argentina, came back here and after a few month and updates started to get the disconection of the GPU, solved using some of the tips on this forum but performance is awfull.
I dont know what to do with this, its still in warranty period but I dont know what to do with this device, spent a lot of money as in Argentina the dollar is very expensive but I did love the previous Surface Pro 2017 version I had.
Would love to know if anyone has any advice, if its better to wait and ask for replacement in short ... maybe I would be able to send it to US or wait hopefully for a fix.
Thanks.
-
Anonymous
2019-09-20T18:56:38+00:00 Yes, Thank you. Just installed the previous version of windows and prevent updates (but it's a bit uncomfortable without them). Just that night I haven't usb to write a windows image and after that I need to reinstall all apps. situations like this tickle nerves of course. I had a lot of problems with 2 1080ti and 1 quadro p400 about this spring. As can see keep nvidea working with windows required to take care of it now and then
-
Anonymous
2019-09-20T17:55:54+00:00 Because I work in the software industry, the longer this goes on, the more interested I become in what the root issue is. MS knows this bug exists and knows its impact to their premier device so I'm sure this is categorized as a Sev 1 or Sev 2 customer reported issue. They will be taking it seriously and prioritizing resources to fix it. The fact that it is taking this long must mean it is a difficult or risky fix. We'll never know the technical details but I'm sure they would be interesting. If there was a quick easy fix, MS would have delivered it by now.
You are making some probably incorrect assumptions. Microsoft was alerted to issues for months before they acknowledged (at least publicly). You dont know how Microsoft prioritizes stuff. They have cut back on a lot of teams over the years (i.e. testing). My general opinion is that it seems they may have putter a bigger emphasis on working on their new product line rather than testing/fixing/maintaining their existing. I have worked on plenty of projects where there are quick and easy fixes that take months or even years to push through. I have also worked on some stuff where there are extremely complicated fixes that get completed/tested/moved into production extremely quickly.