SurfaceBook Crashes/Shutdowns During Sleep

If my SB is in Sleep for over a couple hours and it is plugged in to the charger it will crash with the same error reported as you are getting. If it is in Sleep on the battery (not plugged in to the charger) it will not crash and will exit sleep normally with the desktop preserved. If I enable Hibernate (default setting - SB enters Hibernate after two hours) and the SB is not connected to the charger it will come out of Hibernate normally, with the desktop preserved. If the SB is plugged in to the charger and it Hibernates it usually doesn't crash but the Hello camera will fail to operate when it comes out of Hibernate until I restart the SB.

Check your settings. If your SB is set to Sleep only and you are leaving it plugged in to the charger, then you are likely experiencing the same issue that I am having. My temporary workaround is to set the Sleep settings to "Never" when Plugged In. All other settings are left to the default. Therefore my SB does not enter Sleep (or Hibernate) when plugged in. So far (five days now) it has not crashed when plugged in or on battery.

This is a widely reported issue and I remain hopeful that Microsoft will release an update that addresses this issue.

Almost every night, my Surface Book improperly shuts itself down. The only clues I can find in the event viewer are a string of "The server {7006698D-2974-4091-A424-85DD0B909E23} did not register with DCOM within the required timeout." as the last events of the day. This starts around 1:30am.

The next morning I see an event "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

If I left any programs open, they're all closed, and I have to start completely over. Clearly this is a shutdown, not a sleep. My power management settings allow my computer to sleep after 2 hours when plugged in.

There appear to be many others who are experiencing very similar things.

Yeah now that you mention it, I have to say that my observations confirm your statements. I just didn't connect the dots earlier. It was definitely the Feb 17 update that messed things up. My original was pretty much flawless after the January updates and once the Feb 17 update hit, I got all those problems. So hopefully this can be fixed with another firmware update and we can all move on with our lives.

Few observation that might shed some light on the issue of crash-while-in-sleep-mode:

1. I received my SB (i5, 256GB, dGPU) in late Nov, and I did NOT experience a single case of sleep-crash until Feb 17. I used only sleep setting, and no hibernate.
2. The day after Feb 17 updates, the sleep-crashes started, initially once a day at late night hours while in sleep mode for a long period, or multiple times during the day and night, if in sleep mode for a long period.
3. Before the Feb 17 update, never had attach/detach issue, after the Feb 17 update, many many times.
4. After the sleep-crash problems started, I started using Hibernate (removed all sleep settings). There has NOT been a single case of crash while in Hibernate.
5. After Feb 17 update, the error logs show many many critical errors while in Sleep mode, but none while in Hibernate mode. Before Feb 17 update, the error logs did not show errors.

I may be totally off, but I think MS made a change with the Feb 17 update to make the Sleep mode go into deeper sleep (but not as deep as hibernate) compared to the Sleep mode before the Feb 17 update which was a lighter sleep (standby).

This was done because many initial owners were complaining (before the Feb 17 update) that while in Sleep mode (standby) the background process kept running and draining the battery and getting hot.

But after the Feb 17 update, the deeper sleep causes those background process to fail, and maybe crash the SB.

Again, before Feb 17 update, I did not have a single sleep-crash; it all started after Feb 17 update.

Yeah I agree with you on the whole intel is probably at fault part. Ive been suspecting a hardware issue for awhile now but the skylake chip issues on other devices as well all point fingers at intel.

This has been my suspicion almost from the beginning with the SP4 and SB. The issue is most likely intel's problem and they have yet to figure out how to fix it. Power management issues are rampant with just about every laptop, tablet, or hybrid that uses a skylake. I had hoped that they would have sorted it out by now, but I guess 6 months is too much to ask.

That said, my skylake desktop chip is fine, but of course, I disabled the integrated graphics in favor of a separate video card.