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

201 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. 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
  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
  3. 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
  4. Anonymous
    2016-04-19T19:39:48+00:00

    I have the same issue with the same Surface, i5 256gb dGPU. I have installed the new firmware drivers before, and there are no errors in the device manager. I have also done a full reset, the error still occurred.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-04-20T00:49:31+00:00

    Thanks Brian for your help.

    It is greatly appreciated that someone from MS is trying to help all of us having issues with our SB.

    I had already seen the link that you provided, and had verified before.

    In addition to that, I have done sfc, dism (with downloaded image), recovery-reset, etc. None of them have helped.

    But per your instructions, I checked Device Manager again and everything looks good (the driver version numbers match too):

    Was this answer helpful?

    0 comments