Windows 8.1 Surface Shuts Down instead of sleep

Anonymous
2013-10-19T07:38:25+00:00

Since upgrading to 8.1 my Surface Pro will reboot when it should have gone into Sleep mode.... not every time, but if the machine has not been used for a while (e.g. over an hour or so). Prior to the upgrade it was very reliable.

For example, this morning the following messages were in my Event Viewer

The previous system shutdown at 20:18:39 on ‎18/‎10/‎2013 was unexpected.

Windows failed to resume from hibernate with error status 0xC0000411.

The message previous to this was...

The system has returned from a low power state.

Sleep Time: ‎2013‎-‎10‎-‎18T18:00:59.127876100Z

Wake Time: ‎2013‎-‎10‎-‎18T19:08:25.476268900Z

Wake Source: Power Button

Sleep mode was entered at 19:01, not mains connected, but battery fully charged (and still charged in the morning).

Any ideas?

Windows for home | Previous Windows versions | Install and upgrade

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

48 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2014-01-31T07:43:44+00:00

    Hi,

    Glad to know that you have fixed the issue by yourself. Let us know if you face any issues with Windows in future.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-01-31T12:00:19+00:00

    Interesting.... I ran the Troubleshooter and found the same issues, and it said it had fixed them. Then I ran the Troubleshooter again, same result......and again,same result.......and again,same result! So, when it says there was a problem, was there? Or when it says it was fixed,was it?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-02-01T00:30:36+00:00

    For me the problem seems to have been my network card, in addition to static. Yes, static from my hands, as somehow my  Payless sneakers on a wood floor pick  up a charge, and touching something near the PC, or the case, wakes it. It can also shut it down, as when i touched  a USB stick that has a metal cover. On older mobos you can kill the mobo by such (always touch the outside of the case to discharge before touching anything inside.

    In any case, this and perhaps what follows were mentioned already, but you may first  want to get a report on what is waking the PC. Using the Run command (faster) type or copy and paste,

    cmd

    and hit Enter on you keyboard. Then write

    powercfg lastwake

    just like it says, and hit Enter and see what it says. Mine now says  USB\ROOT_HUB\4&39a9d847&0 as what is waking it. 

    To deal with the network card. Using the Run command type/paste

    ncpa.cpl

    and hit Enter.  Then R. clk. on the ethernet card (or what is shown) and choose Properties>Configure>Power Management and make sure the first option is checked, and the second is not. You can also go under Advanced and deselect Wakeon Lan and do the same for Magic packet. You do not need the  Energy efficient or Green... checked either, but should be  unrelated to this.

    To configure your power options, using the Run command paste

    powercfg.cpl

    and hit Enter. Hit Change Plan>Advanced settings. I have hybrid sleep on but allow wake timers off.  I also have USB  selective .... off .  And it sleeps after 10 min.

    Also, you can check if  any scheduled tasks are waking it: Using the Run command paste

    Taskschd.msc 

    and hit OK  Look under Task Status to see what may be scheduled, and if it corresponds to your wakeups.

    Hope this does good.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-02-01T06:11:18+00:00

    Hi,

    Thank you for sharing the resolution with us which will help others facing the same problems to fix it.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-02-17T17:20:26+00:00

    I am sad to report the issue has returned...  My Surface is crashing again with the same 0xC0000411 code, and it started after I applied this latest round of patches...  Now I am back to square one..

    I have seen this issue reported on numerous news groups, so I was wondering if MSFT is working on a fix for this issue...  Any news about an update to fix this issue once and for all would be great...  At this point, I would settle for an explanation as to why so many devices are affected, and what is the root cause... Anything...

    Thanks

    Shane

    Was this answer helpful?

    0 comments