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> |
Unfortunately, there have been many replies on this thread that have been just useless noise that don't help anybody, and which create unwanted noise for those of us that are subscribed hereto with the desire to see a "fix" for the reported issues. Such is the nature of public forums. Irrespective, these are the two current issues as I understand them:
I have experienced both of these issues on my SB2, which I've had since November 2017.
I am now running the Insider build of Windows, as per Eddy's recommendation, and neither issue has plagued me since I made this change. (For those unwilling and/or unable to implement this "pre-release fix" for whatever reason, for the sake of all subscribers to this thread, please keep your irrelevant responses to yourselves, as obviously if you're in that camp then this recommendation wasn't for you, at least not yet).
For those interested, here are my current, working stats (from Start > Settings > Updates & Security > View Update History):
Humm, I see. At least, they are supposed to run a test of the beta builds for us SB2 users before offering this solution. I think they are irresponsible for its existing users.
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...