SurfaceBook Crashes/Shutdowns During Sleep

Anonymous
2016-03-31T05:22:05+00:00

My SB (i5, 256gb, 8gb, GeforceGPU) keeps crashing/freezing during sleep which causes it to shut down. According to the windows reliability monitor it has been happening every day multiple time.

I though I was going crazy because I clearly remember not turning it off before putting it to sleep. I recently had my original SB replaced with a new one which fixed most of the issues from blue screens to flickering that would not go away. But this new one still has the Hello Camera issue where it wont turn on during startup and this new problem that has popped up.

Is this caused by a hardware defect? I really don't want to drive 23km to the other side of my city to get another replacement at a Microsoft store if the issues aren't resolved. Here's an image on the report. As you can see, there are 17 critical events today not to mention all the other days as well. Thanks.

If anyone has a solution that isn't a complete factory reset or system reinstall (I've tried them before) that would be great.

Surface | Surface Book | Display and screen

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.

0 comments No comments

201 answers

Sort by: Most helpful
  1. Anonymous
    2016-04-19T18:24:40+00:00

    Hello orman62,

    Please verify that after your 2/17/2016 updates on your Surface Book that there are not any devices in Device Manager showing an yellow exclamation icon next to the device. Even if you do not see any it may be beneficial to try manually installing available firmware and drivers for your Surface Book by following the instruction provided here.

    Please try these troubleshooting steps and post your results in your reply.

    Best Regards

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-04-19T17:35:55+00:00

    Here is a summary of the four major issues that many many SB owners are experiencing since the 2/17 update (well-documented in these forums):

    1. sleep-crash (crashing while in sleep for a longer period of time)
    2. hibernate-hello (windows hello not working after coming out of hibernate)
    3. hibernate-attach/detach (tablet attach/detach not working correctly after coming out of hibernate)
    4. hibernate-autorotate (tablet screen auto rotate, once tablet detached, not working after coming out of hibernate)

    I think item 1 above is the most pressing issue that needs to be addressed by MS, urgently.

    Thanks

    Microsoft, please solve the problem. It has been 2 month since 2.17 updates. 

    BTW, 2.3.4 always happen together.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-04-19T04:02:53+00:00

    Here is a summary of the four major issues that many many SB owners are experiencing since the 2/17 update (well-documented in these forums):

    1. sleep-crash (crashing while in sleep for a longer period of time)
    2. hibernate-hello (windows hello not working after coming out of hibernate)
    3. hibernate-attach/detach (tablet attach/detach not working correctly after coming out of hibernate)
    4. hibernate-autorotate (tablet screen auto rotate, once tablet detached, not working after coming out of hibernate)

    I think item 1 above is the most pressing issue that needs to be addressed by MS, urgently.

    Thanks

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-04-19T02:37:02+00:00

    Hi Brian,

    Sleep crashing is a well documented and often observed fault for many SB users. A review of this forum will find dozens if not hundreds of posts about this issue. I have observed this problem on every one of the several, exchanged SBs I have owned. The problem can be easily replicated. Leave the Power/Sleep settings to default. Then open a few browser windows and/or applications and leave them open. Close the clipboard or put the SB to sleep using the Power menu. Allow it to stay in the Sleep state overnight. Instead of the SB exiting Sleep as expected with the desktop intact (browser windows and apps where you left them) you will find that the SB has crashed and will restart after you push the power button. All of your open windows and apps are gone. The Event Viewer will log this as a Critical Error "Kernel-Power" with the description "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." I have all updates installed, SB is plugged in during Sleep. I can reproduce this every time I let the SB Sleep for at least a few hours.

    Perhaps not all SBs suffer from this issue but many do. I have had at least 5 different lot numbers up to and including my current SB (lot #1602) exhibit this problem. I have tried all the suggested "fixes" others on this forum and MS Support have suggested (reloaded drivers, DISM from a clean image, completely wipe and reinstall the image, disable Fast Start, disable connected standby, etc.). Exchanging SBs has not solved the issue.

    My temporary workaround has been to disable the sleep state when the SB is plugged in to power and to shut down otherwise. This is contrary to my normal workflow where I would prefer the SB to Sleep properly when I am away from it and exit Sleep with my desktop intact on demand. Forcing the SB to bypass Sleep and go directly into Hibernate results in the Hello Camera stalling every time it exits Hibernate. This is also a well documented fault on this forum.

    It would be helpful to know if Microsoft can reproduce the Sleep Crash and Hello Camera problems and what is being done to remedy them, if anything. If you would like to contact me offline I would be happy to do what I can to help.

    Thanks,

    Gary

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-04-19T01:05:05+00:00

    All updates are installed.

    On 3/30/2016, per MS support, I did a Recovery|ResetThisPC (did not keep any data or programs). And then ran Windows Update. See Update History below.

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=6ef30b01-087c-4f8f-a95d-21293a036b93)

    Was this answer helpful?

    0 comments No comments