SurfaceBook Crashes/Shutdowns During Sleep

Thanks for your post. Given your experience it is unlikely that plugged in or not has any effect with the Sleep Crash issue. I haven't done that much testing of Sleep with the SB unplugged (on battery) for extended periods like I have with the SB plugged in, so it is likely I just haven't encountered it yet. I was struggling to understand the difference between Sleep with the SB plugged in or on battery. It appears there isn't any.

I had a crash during sleep last night, while not plugged in. (All new updates installed) 

Also still overheats/does not sleep properly while plugged into my Dock. Looks like it's back to all hibernate settings for another 2 months...

Another issue, overnight I left the SB plugged in sleep mode and today in the morning I noticed that the SB had rebooted from a cold start, that means instead of staying in sleep mode or go into hibernation mode overnight, the SB unexpectedly shutdown, I confirmed this by checking the logs at the Event Viewer, is this another know issue?

Thank you for sharing your observations webdev90201.

I have completed the DISM repair process and verified no Device Driver issues. I can confirm my SB still crashes during Sleep.

What is peculiar (to me) is that my SB seems to sleep and resume properly when not plugged in to the charger (hibernate is disabled) but consistently crashes when plugged in during sleep.

The 4/19 updates did not solve the crashing while in sleep for me either. I too, am on my second Surface Book. I have the i5/256/dGPU model. After applying the updates, I reset my power settings back to defaults with the hope that connected standby and hibernation would all work in harmony. I shut the lid with Chrome and Outlook open when I left work this evening and a couple of hours later turned it on to find it had once again crashed during sleep. I just ran sfc /scannow and am back to having corrupt files since the 4/19 update (all of which had been previously fixed - see my history below).

For a brief *not so brief* history, I originally pre-ordered my Surface Book, so I got my machine on day one. After a month, I returned it due to many reliability issues (hinge stuck on one side, black screen during resume, hot bag, camera issues). After the first big set of updates I decided to give it another go and I instead went to Best Buy to purchase another i5/256/dGPU model in late December. Most of the initial issues were indeed resolved and I thought things were going pretty well. I still had a few issues with the black screen where the keyboard would light up, but no screen. Sometimes shutting the lid, or detaching would solve it. Sometimes I would have to reset it. I gave up on the Windows Hello Camera in order to focus on narrowing the chance of failure.

When the February updates came, I applied them and that's when things got way worse for me. I had constant crashing during sleep. I posted about it on Thurrott's blog. Many others were also saying the 2/17 update was creating new problems for them. I ended up spending the following weekend doing a full reset and re-installing all of my apps so that I could be sure I had a fresh system. During that process, I noticed a few things. After a full factory reset and installing all of the updates (no 3rd party software installed), the sfc /scannow and DISM found problems. Unusual for a new build, I thought. Others have stated that the builds on some Surface Books were corrupt. I'm not sure if it was the initial build or one of the updates, but that's not a good way to start off. Following instructions here, I was successful with the DISM reset, but that had already put a dark cloud over the whole install. I decided to start over yet again, only this time create my own Windows 10 flash drive and download the ISO from Microsoft. I once again did a full reset with this build. Unfortunately, the results were the same. I ran the updates and then had to do a DISM reset and fix corruption.

After my seemingly working fresh install with all the updates, including 2/17 and default sleep settings, it did seem that things were working well (granted I had no software installed). I then started adding programs, one by one and trying sleep / hibernate. I couldn't get it to fail. Then, I installed iTunes. I know (my kids have iPod Touches). That's when the first crash during sleep happened. Researching the DCOM error found that iTunes was definitely the first issue. Since then, however, its been whackamole with DCOM errors as I've added software. I have done the DCOM permissions fix and stopped them from reoccurring, but its been hit or miss. Probably one in ten times, I find it's crashed again. Usually, I will only have Chrome and a couple of apps open. I use Visual Studio all day long, but I always close it when I know I will be away for a while, because I can't trust this machine.

From my own experiences and from reading what other's are saying, here is my take. I think there is a fundamental flaw with the way Windows legacy apps behave with the hand-off between connected standby and hibernation that was possibly introduced or intensified by the changes made in the 2/17 update. The DCOM errors are not new, you can find similar reports of even the same app ids back in Windows 8 and 8.1, but they weren't causing a system crashes until they started happening during the connected standby mode on a Skylake machine. The reason it is not consistent may be related to which apps were running, or services (e.g. video in a browser (even if not playing) which inadvertently causes a DCOM error on the Intel 520 driver, but only after the hand-off from sleep to hibernate occurs. Most of the attention has been on the more obvious errors, such as the hot bagging and the black screen, but I think there is a much bigger underlying problem here that is complicated and sporadic enough that it's not getting a lot of attention.