Surface Book 2 GPU Driver disappears randomly after May 2019 update

Sorry, when I look at this thread, the top is a post from Shahin Kohan stating:

"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?"

This problem is the one directly related to the 1903 issue as stated above.  I had posted a thread directly linked to this issue that was then merged into this thread.  What we're looking at in reality is three entirely separate issues that have been exacerbated by changes within the Windows architecture between 1803, 1809, and 1903.  These issues are as follows:

1. dGPU disconnect.  I've had the Surface Book 2 since release (and had a SB1 w/ Performance Base before that) and use it exclusively for CAD drafting using the dGPU.  I never had a problem with the dGPU disconnecting or graphics related BSODs until my system updated to 1903 (it was on 1803 before then, it never received the 1809 update).  From what I can ascertain from other people with this issue and going through the logs from my own experience, this issue is caused by changes in the way that Windows manages power.  Once the dGPU kicks in, the system does give the dGPU enough power to maintain under load, so the dGPU shuts off causing the system to lose connection to it, also likely crashing the software that's using it or causing a BSOD.  This is why a hardware rescan temporarily resolves the issue, the card reset and was only truly disconnected momentarily.  This is also why setting the machine to be in permanent "high performance" mode prevents the disconnect since the graphics card is always getting max power (at the expense of having the fans constantly running at full tilt).  I was lucky enough to catch it within the 10 days to roll back to 1803, so this issue has been more or less resolved for me at the moment.  The other issues however...
2. Black screens / external displays disconnecting.  As far as I can tell, this is mostly a problem with the dock accessory.  I've had issues relating to this since day one but only seem to have the problem when connected to the dock.  If I connect an external display directly to the USB-C port (or the mini-display port on the SB1), I never saw this behavior.  I think this could be either a power issue or a heating issue, as it only happens to me when the dGPU is running and the dock itself gets really warm.  One of the problems with the Surface Book line since its inception has been that the power supply and dock power supply doesn't provide enough power for the system (under really extreme operation, the system doesn't get enough power to operate and charge the battery at the same time, resulting in the batteries draining even though it's plugged in).  The dock has several other problem as well, I've had problems with USB components disconnecting as well as the audio jack randomly disconnecting.  I've gone through the process of updating the firmware on the dock, but all of those issues persist.
3. CPU throttling.  This is a problem that I haven't encountered too often but that I found many others suffered from on Reddit.  This is more or less a cooling issue of the CPU located in the "clipboard" half of the machine, and is especially prevalent in the 13" fan-less models.  According to Reddit, this is a problem that got worse in 1809 (probably why I haven't really seen the issue) and can be solved by having a fan point at the center of the clipboard when under heavy load.  The tell-tale symptom of this problem is having the CPU use never go above 0.4 Ghz in the Task Manager, as that is where the machine throttles back to until it's been cooled.

Overall, these issues are pretty terrible and frustrating.  I love the machine and strongly believe in what the Surface team are trying to do in terms of design, but I can no longer recommend the machine in good conscience even though mine no longer has the crippling bug.  Microsoft's response has also not been stellar and I do see a class-action lawsuit happening over lost work/time.

Add #4: Hibernation recovery black screen and Hibernation BSOD issues likely related to GPU

Regarding #1,  I know folks with SB1 that had issue #1 with frequent dgpu and base disconnects but it may be a different issue just same appearance on the surface

Regarding #2, Black screens have nothing to do with the dock. I get black screens without the dock. The issue I have with the dock is the fan on the SB2 no longer seems to kick on when the SB2 gets hot so I cannot use it with the lid shut

Regarding #3, that is the latest issue. I never had it happen until maybe February / March time frame. It started with 1809 when I received windows updates. It carried over into 1903.

Sorry, when I look at this thread, the top is a post from Shahin Kohan stating:

"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?"

This problem is the one directly related to the 1903 issue as stated above.  I had posted a thread directly linked to this issue that was then merged into this thread.  What we're looking at in reality is three entirely separate issues that have been exacerbated by changes within the Windows architecture between 1803, 1809, and 1903.  These issues are as follows:

1. dGPU disconnect.  I've had the Surface Book 2 since release (and had a SB1 w/ Performance Base before that) and use it exclusively for CAD drafting using the dGPU.  I never had a problem with the dGPU disconnecting or graphics related BSODs until my system updated to 1903 (it was on 1803 before then, it never received the 1809 update).  From what I can ascertain from other people with this issue and going through the logs from my own experience, this issue is caused by changes in the way that Windows manages power.  Once the dGPU kicks in, the system does give the dGPU enough power to maintain under load, so the dGPU shuts off causing the system to lose connection to it, also likely crashing the software that's using it or causing a BSOD.  This is why a hardware rescan temporarily resolves the issue, the card reset and was only truly disconnected momentarily.  This is also why setting the machine to be in permanent "high performance" mode prevents the disconnect since the graphics card is always getting max power (at the expense of having the fans constantly running at full tilt).  I was lucky enough to catch it within the 10 days to roll back to 1803, so this issue has been more or less resolved for me at the moment.  The other issues however...
2. Black screens / external displays disconnecting.  As far as I can tell, this is mostly a problem with the dock accessory.  I've had issues relating to this since day one but only seem to have the problem when connected to the dock.  If I connect an external display directly to the USB-C port (or the mini-display port on the SB1), I never saw this behavior.  I think this could be either a power issue or a heating issue, as it only happens to me when the dGPU is running and the dock itself gets really warm.  One of the problems with the Surface Book line since its inception has been that the power supply and dock power supply doesn't provide enough power for the system (under really extreme operation, the system doesn't get enough power to operate and charge the battery at the same time, resulting in the batteries draining even though it's plugged in).  The dock has several other problem as well, I've had problems with USB components disconnecting as well as the audio jack randomly disconnecting.  I've gone through the process of updating the firmware on the dock, but all of those issues persist.
3. CPU throttling.  This is a problem that I haven't encountered too often but that I found many others suffered from on Reddit.  This is more or less a cooling issue of the CPU located in the "clipboard" half of the machine, and is especially prevalent in the 13" fan-less models.  According to Reddit, this is a problem that got worse in 1809 (probably why I haven't really seen the issue) and can be solved by having a fan point at the center of the clipboard when under heavy load.  The tell-tale symptom of this problem is having the CPU use never go above 0.4 Ghz in the Task Manager, as that is where the machine throttles back to until it's been cooled.

Overall, these issues are pretty terrible and frustrating.  I love the machine and strongly believe in what the Surface team are trying to do in terms of design, but I can no longer recommend the machine in good conscience even though mine no longer has the crippling bug.  Microsoft's response has also not been stellar and I do see a class-action lawsuit happening over lost work/time.

For me, the BSOD screens when using the dGPU started after updating to 1903 version of Windows, as for the dGPU disconnections.

Before updating to 1903 release, I never experienced a BSOD screen for a GPU driver issue and never experienced dGPU disconnections.

I don't know if it's strictly connected to dGPU issues, but the CPU throttling is for sure another severe issue of this device, it might be related to the usage of the iGPU and from 3 months till now I have it quite every day (here is summer and temperatures are always > 28°C). You can find more details on the throttling bug here:

https://www.reddit.com/r/Surface/comments/94uac9/lets_talk_about_the_sb2_infamous_04ghz_throttling/

The sad thing is that with these two bugs, not yet solved after many months, any Surface Book 2 really becomes unusable.

For those of you who are saying it started with 1903, were you on the absolute latest build with all updates on 1809? I ask because I am pretty sure much of the issues were introduced in 1809 or with a cumulative update / windows update that also applied to 1809. Many folks may think it started with 1903 because 1903 brought them up-to-date on previous updates to 1809. I have no new issues in 1903 that I didnt have already in 1809.