Surface Pro 2017 turning off or hibernating randomly!!!

Anonymous
2017-06-17T13:19:55+00:00

For some reason my new Surface is shutting off randomly. I check the setting and a few other things but it's still randomly turns off without warning. I'm losing some of my school work because of it. Is anyone else having this problem?

Surface | Surface Pro | Power and battery

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
Answer accepted by question author
Anonymous
2017-06-29T00:49:55+00:00

Hey Everyone,

As of 7/14, the fix for this issue has completed testing and is now live, please go update your Surface Pro via Windows Update to get the latest download. You can obtain this fix by checking Settings> Update & security > Windows Update

The Surface Pro Update History page has been updated with the details of this release and the update is also available on the Surface Pro Drivers and Firmware page as part of the MSI installation package available for download.

BryanH [MSFT]

Was this answer helpful?

100+ people found this answer helpful.
0 comments

594 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2017-06-28T00:24:16+00:00

    The following was my solution:

    While plugged in did a complete system reset deleting all files and settings. So far it's been 2 days and hasn't shutoff unexpectedly. 28.06.17

    Also kept it plugged in during all updates and app install

    EDIT: Has started doing it again - so reset is a temporary fix.!!!!!!!!!!!!!!!!!!!!!!!!!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-06-28T01:29:39+00:00

    Same thing is happening to me. i5, 8, 256 SP 2017. Has happened about 4 times so far since owning the device for a week. It seems to only happen when I'm using the device in Tablet mode with touch and no other accessories. When it's plugged in, the only other device I have is the new type cover. Here are the events from the viewer from the time it happened. 

    Log Name:      System

    Source:        Microsoft-Windows-Power-Troubleshooter

    Date:          27/06/2017 21:58:35

    Event ID:      1

    Task Category: None

    Level:         Information

    Keywords:     

    User:          LOCAL SERVICE

    Computer:      Surface

    Description:

    The system has returned from a low power state.

    Sleep Time: ‎2017‎-‎06‎-‎28T00:58:10.716326900Z

    Wake Time: ‎2017‎-‎06‎-‎28T00:58:33.848669600Z

    Wake Source: Unknown

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Microsoft-Windows-Power-Troubleshooter" Guid="{CDC05E28-C449-49C6-B9D2-88CF761644DF}" />

        <EventID>1</EventID>

        <Version>2</Version>

        <Level>4</Level>

        <Task>0</Task>

        <Opcode>0</Opcode>

        <Keywords>0x8000000000000000</Keywords>

        <TimeCreated SystemTime="2017-06-28T00:58:35.767558800Z" />

        <EventRecordID>3697</EventRecordID>

        <Correlation ActivityID="{45316B03-0998-49C0-89A9-1BB1DE5E55D2}" />

        <Execution ProcessID="3352" ThreadID="10980" />

        <Channel>System</Channel>

        <Computer>Surface</Computer>

        <Security UserID="S-1-5-19" />

      </System>

      <EventData>

        <Data Name="SleepTime">2017-06-28T00:58:10.716326900Z</Data>

        <Data Name="WakeTime">2017-06-28T00:58:33.848669600Z</Data>

        <Data Name="SleepDuration">3472</Data>

        <Data Name="WakeDuration">1354</Data>

        <Data Name="DriverInitDuration">1094</Data>

        <Data Name="BiosInitDuration">0</Data>

        <Data Name="HiberWriteDuration">5264</Data>

        <Data Name="HiberReadDuration">2788</Data>

        <Data Name="HiberPagesWritten">430080</Data>

        <Data Name="Attributes">33571073</Data>

        <Data Name="TargetState">5</Data>

        <Data Name="EffectiveState">5</Data>

        <Data Name="WakeSourceType">0</Data>

        <Data Name="WakeSourceTextLength">0</Data>

        <Data Name="WakeSourceText">

        </Data>

        <Data Name="WakeTimerOwnerLength">0</Data>

        <Data Name="WakeTimerContextLength">0</Data>

        <Data Name="NoMultiStageResumeReason">0</Data>

        <Data Name="WakeTimerOwner">

        </Data>

        <Data Name="WakeTimerContext">

        </Data>

      </EventData>

    </Event>

    Log Name:      System

    Source:        BTHUSB

    Date:          27/06/2017 21:58:35

    Event ID:      34

    Task Category: None

    Level:         Warning

    Keywords:      Classic

    User:          N/A

    Computer:      Surface

    Description:

    The local adapter does not support an important Low Energy controller state to support peripheral mode.  The minimum required supported state mask is 0x491f7fffff, got 0x1fffffff.  Low Energy peripheral role functionality will not be available.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="BTHUSB" />

        <EventID Qualifiers="32773">34</EventID>

        <Level>3</Level>

        <Task>0</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2017-06-28T00:58:35.220008100Z" />

        <EventRecordID>3696</EventRecordID>

        <Channel>System</Channel>

        <Computer>Surface</Computer>

        <Security />

      </System>

      <EventData>

        <Data>

        </Data>

        <Data>0x491f7fffff</Data>

        <Data>0x1fffffff</Data>

        <Binary>00000000030028000000000022000580000000000000000000000000000000000000000000000000</Binary>

      </EventData>

    </Event>

    Log Name:      System

    Source:        Microsoft-Windows-DistributedCOM

    Date:          27/06/2017 21:58:37

    Event ID:      10016

    Task Category: None

    Level:         Error

    Keywords:      Classic

    User:          SYSTEM

    Computer:      Surface

    Description:

    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

    {D63B10C5-BB46-4990-A94F-E40B9D520160}

     and APPID

    {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}

     to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />

        <EventID Qualifiers="0">10016</EventID>

        <Version>0</Version>

        <Level>2</Level>

        <Task>0</Task>

        <Opcode>0</Opcode>

        <Keywords>0x8080000000000000</Keywords>

        <TimeCreated SystemTime="2017-06-28T00:58:37.290173100Z" />

        <EventRecordID>3698</EventRecordID>

        <Correlation />

        <Execution ProcessID="1016" ThreadID="15200" />

        <Channel>System</Channel>

        <Computer>Surface</Computer>

        <Security UserID="S-1-5-18" />

      </System>

      <EventData>

        <Data Name="param1">application-specific</Data>

        <Data Name="param2">Local</Data>

        <Data Name="param3">Activation</Data>

        <Data Name="param4">{D63B10C5-BB46-4990-A94F-E40B9D520160}</Data>

        <Data Name="param5">{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}</Data>

        <Data Name="param6">NT AUTHORITY</Data>

        <Data Name="param7">SYSTEM</Data>

        <Data Name="param8">S-1-5-18</Data>

        <Data Name="param9">LocalHost (Using LRPC)</Data>

        <Data Name="param10">Unavailable</Data>

        <Data Name="param11">Unavailable</Data>

      </EventData>

    </Event>

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-06-28T03:42:18+00:00

    Hi,

    Let's take a look into this concern. Have you tried creating a new power plan yet? If not, we suggest that your try creating a new one just to see if the same issue occurs.

    Also, make sure that all Windows and Surface updates are installed, here's a Support article that might help.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-06-28T09:32:01+00:00

    I also have this problem, SP i7 16 512, had it for 5 days, did the Windows Cumulative update last night and today at work, using Chrome, it just hibernated and I had to wake it up and wait for it to come back.

    Rubbish. Will have to send it back if this isn't fixed in the next few days.

    Back to a Mac :-(

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments