Surface Pro 2017 turning off or hibernating randomly!!!

I am experiencing the same problem as well. Instead of hibernation, I believe it actually turned off because the Microsoft logo will pop up and that happens when you turn on your Surface right?

I have the i7/8GB RAM/512GB Model

Power Mode doesn't matter as it happened under all mode.

When it happens, only type cover (SP4 version) is attached, and it is on battery (not plugged in)

I have inspected the event viewer, the following warnings can be found every time after the sudden "death" of the SP2017:

1. 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.
2. 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.
3. The system has returned from a low power state. Sleep Time: ‎2017‎-‎06‎-‎19T16:28:27.177108900Z Wake Time: ‎2017‎-‎06‎-‎19T16:28:48.378997100Z Wake Source: Unknown [I personally think this is the most crucial one?]

Kinda frustrated, as I just got the new machine for 2 days :(

Nice to see that it's not only my computer.

My Surface is the i5/8g/256g. I only have the keyboard accessory. I'm using it in a laptop mode (it's in a regular standing position on a table). It mainly goes into hibernation mode (randomly) but I did notice that it turned completely off twice. I have notice it happening plugged or unplugged. I did go into the setting and change all the timing to none and I did check for overheat and any other warnings and there isn't. With everything that I have done its still having that problem.

I'm will be contacting Microsoft about this problem if they haven't seen this post yet.

Yep, I have the same exact issue with my surface pro 256/8/i5 with the keyboard cover. It is annoying me with how it is putting itself to sleep all the time. Even when I am in the middle of typing sometimes! Seems like it is more likely to happen after a real reboot, and then it seems less likely to happen a subsequent time. (I think. There doesn't seem to be much rhyme or reason for why it is happening. It probably has happened 8 or 10 times to me so far since I got it last week.) I have set all my power options to turn off/sleep to "NEVER" and I disabled the checkbox to "save me power when my device knows I am away." Doesn't seem to make any difference. I see 2 different scenarios in my event log for this. One is when it puts it to sleep, and another time is when it puts itself into "connected standby". Here are the two kinds of "Events" and "Reasons" that I am getting:

Information 6/18/2017 11:08:46 AM Microsoft-Windows-Kernel-Power 506 (157) "The system is entering connected standby Reason: Idle Timeout."

Information 6/19/2017 8:35:41 PM Microsoft-Windows-Kernel-Power 42 (64) "The system is entering sleep. Sleep Reason: Application API"

Note #1: The reason the display brightness is changing by itself (even if you have it set not to) is because of some intel thing called "DPST" and you can turn it off with a registry setting (although it may not be straight forward, since the setting for it is just one bit in a DWORD so if your settings aren't the same as on this link, you might need to do a little bit of bitmask math.)https://mikebattistablog.wordpress.com/2016/05/27/disable-intel-dpst-on-sp4/

Note #2: There is a registry setting to turn off "Connected Standby" which may help the situation (but probably wont

help the "sleep" scenarios.) The directions for that are here: http://windowsitpro.com/windows-client/disabling-windows-connected-standby

Note #3: When I contacted Microsoft support about this, their suggestion was to give me a link to reinstall all my drivers. I did that, but it had no effect on the situation. 

The registry tweaks in the links above make the situation a little less bad, but there is still a problem. I hope Microsoft can issue a Hotfix for this quickly! Or else I might consider having to return my new Surface Pro while I'm still in my 30 day return-window.

Any plans on Microsoft fixing this ? looks like I will need to return the device