Surface Pro 2017 turning off or hibernating randomly!!!

Try this as a workaround that should (hopefully) stop the random hibernation / shutdown.  The following will disable hibernation through the command line interface:

• Start an elevated command prompt (in the search bar on the task bar type "cmd" and right click "command prompt" and select "run as administrator")
• At the prompt type "powercfg /h /type reduced" (exactly that text without the quotes) - this command actually reduces the size of the hiberfile so that traditional hibernation doesn't happen and it is used only for hiberboot.  Alternately you can turn off hibernation entirely by typing "powercfg /h off"
• If you used the first command to change to the reduced hiberfile size, you'll get a response showing the new size of the hiberfile.  If you instead turned it off, you won't get any confirmation
• Close the command prompt window

This has worked for me for about a day, which is admittedly not enough time to confirm this is a valid workaround, but I figured I'd post this so others can try the same and report back.

One thing to note - this essentially disables hibernation, so you'll lose some of the power saving benefits you get while hibernating, but standard sleep mode works pretty well on the Surface Pro.  I'm thinking this is better than the Surface Pro randomly shutting down in the middle of what you are doing until Microsoft comes up with a real solution.

I've included a screen clip of a sleepstudy report over the last 5 days.  You'll notice that over the last 24 hours or so there are no breaks in the line, which indicates my Surface Pro has not shut down or hibernated since I first ran the command.  Over the previous 4 days you'll see a lot of shutdown/hibernation periods (indicated by the line breaks), some of those are random some normal.

I am experiencing the exact same conditions as Frog675.  I am using the Model SP i5/8Gb RAM/256Gb drive. I too have had the random hibernation issue occur several times and the "light screen light bleed" along the bottom of the screen.  

In my case, I have returned several of these with the same exact problems -- light bleed and hibernation issues.  However, I am not willing to pay a premium for this device and tolerate the light bleed issue or hibernation issue.  The hibernation issue is probably a difficult issue for the engineers to fix, however, I am willing to believe MS will likely fix it via a firmware or software update.  

I, like Frog675, may simply get a refund, wait for a month or more for newer batches of devices to come out, and then repurchase; I want this amazing device.  Whoever is manufacturing these devices for MS somehow messed up.  

In defense of MS, I will say this.  I have bought over 50+ Surfaces over the last couple of years and have found the quality of the Surface line unquestionable outstanding.  Apart from these problems, I have had the lowest problem/failure rate with the Surface line than I have had when compared against any other manufacturer (for devices I've purchase for my organization).  Also, MS's customer service in both the physical MS Stores and the online store has been unquestionably outstanding.  

I, too, hope MS fixes this soon.  This latest new Surface Pro is an amazing machine and is quite an engineering feat.  They just need to get these technical issues addressed and this machine -- the New Surface Pro -- can be considered the best in its class, period.

I have been suspecting Arc Touch and Bluetooth, either or both, as the cause of random hibernation.  I have taken out ArcTouch from Bluetooth in device manager.  For now I am using a USB mouse.  So far I have not had the random hibernation problem since last night.  It has been several hours since taking out Arc Touch Bluetooth from Device Manager.  I will continue to observe and report back with updates.

Just to follow up on my previous post:

A little over a week ago, my new Surface Pro i7 256GB hibernated twice within a short space of time while on battery power. Since then I have used it for several hours every day (for a week) with no hibernation issue. I then switched to battery power, and within an hour experienced the sudden unexpected hibernation again. I was using Outlook 2010 at the time, with only the Type Cover connected. I have never connected any Bluetooth device to this machine (I am still waiting to receive my new pen). Event viewer shows the same error messages as for previous occurrences, so I have given these with some more detail below:

Error: Event 17 BTUSB

The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.

Followed 2 seconds later by:

Warning: Event 34 BTUSB

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.

Followed 2 seconds later by:

Error: Event 10016 DirtributedCOM

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

{D63B10C5-BB46-4990-A94F-

and APPID

{9CA88EE3-ACB7-47C8-AFC4-

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.

Looking through previous messages, others have experienced the same error messages while on battery power, which I hope will help Microsoft to identify the problem.