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
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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?
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.
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
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> |
Older Nvidia drivers were blocked, but they've been open to install for over a year now. It's perfectly safe to install newer Nvidia drivers. Consdiering how out of date the package Microsoft is offering, it is probably expecting customers to install drivers from NVidia directly. It's the Intel driver for the iGPU that is still blocked and requires certification.
There is a known issues page published for Windows 10 v1903. Once this problem is acknowledged, I expect it this disconnect issue to show up there.
Microsoft has not yet officially acknowledged the dGPU issue in Windows 10 v1903.
Surface team members do not reply in this forum, only support staff and other users do.
You can manually install the latest NVidia drivers from geforce.com/drivers. The 430.86 package still has the issue. The 431.36 package came out on Tuesday July 9, but I haven't had a chance to test apps that use the dGPU. I suspect it will still have the issue as I believe the problem is on Microsoft's side, not NVidia's.
Microsoft should listen to its users even more, like the excellent work done with Windows 10. There are plenty of discussions and posts on the subject, so if they don't recognize the issue we will try to speed it up.
Support staff can scale the issue to product teams, so they can read.
Thank you for share the last package of NVIDIA drivers, but I prefer to use certified and updated drivers by Microsoft. With a device like this, with this price, I would avoid doing "experiments" ;)
Microsoft has not yet officially acknowledged the dGPU issue in Windows 10 v1903.
Surface team members do not reply in this forum, only support staff and other users do.
You can manually install the latest NVidia drivers from geforce.com/drivers. The 430.86 package still has the issue. The 431.36 package came out on Tuesday July 9, but I haven't had a chance to test apps that use the dGPU. I suspect it will still have the issue as I believe the problem is on Microsoft's side, not NVidia's.