Surface Pro 1 on Windows 8.1 reboots when Type Cover 2 is removed

Thanks, Mark. This might have worked for me. I haven't had a reboot since I tried it this afternoon. I checked my event log, and I haven't had one of the kernel-power events since then, either. I did notice one of them this morning at about the time I first turned it on, but it didn't do anything

Makes you wonder why Microsoft doesn't submit help to this thread?  :)  Its easy to tell how much a company cares after they take your money I suppose.

Thanks, Mark. This might have worked for me. I haven't had a reboot since I tried it this afternoon. I checked my event log, and I haven't had one of the kernel-power events since then, either. I did notice one of them this morning at about the time I first turned it on, but it didn't do anything

I too am having this problem but it has only started happening recently.

I notice it happens when I've got my touch cover connected.... it'll just go black and display the Surface logo and then logon screen.

I've checked the system logs and I find this:

Log Name:      SystemSource:        SchannelDate:          26/12/2013 20:51:04Event ID:      36887Task Category: NoneLevel:         ErrorKeywords:      User:          SYSTEMComputer:      surfaceDescription:A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 40.Event Xml:<Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">  <System>    <Provider Name="Schannel" Guid="{1F678132-5938-4686-9FDC-C8FF68F15C85}" />    <EventID>36887</EventID>    <Version>0</Version>    <Level>2</Level>    <Task>0</Task>    <Opcode>0</Opcode>    <Keywords>0x8000000000000000</Keywords>    <TimeCreated SystemTime="2013-12-26T20:51:04.899899700Z" />    <EventRecordID>10363</EventRecordID>    <Correlation />    <Execution ProcessID="568" ThreadID="4452" />    <Channel>System</Channel>    <Computer>surface</Computer>    <Security UserID="S-1-5-18" />  </System>  <EventData>    <Data Name="AlertDesc">40</Data>  </EventData>

</Event>

The reboot happened twice in quick succession, the Surface logo appeared and just as the logon screen appeared it done it again.... the logs are identical to the one above.

Of course I tried clicking the web link in the log but apparently Microsoft cannot find the page!

Trying to get a replacement Pro Pen a few weeks back was like pulling teeth considering it was only a few months old so I'll need the patience of a saint for a replacement touch cover!!

Hi guys

I think I've found a fix!  It seems to have stopped my Surface Pro rebooting randomly.  I was speaking to Louise from the online support and she suggested I do the following:

Louise: 1. Fully power off Surface by holding power button down or select "shutdown"

Louise: 2. Once shut down press and hold the volume button up, and the power button for 15 seconds. Without letting go of the volume up button press the power button again for 5 seconds.

Louise: 3. Once a different screen appears select to Install Default Secure Boot keys

Louise: 4. Select to Exit then Save Configuration and Reset

Louise: Once you do that, just reboot the Surface and try to reproduce the keyboard issue.

I have done the above and I've not had any reboots since and I could guarantee that it would do it at least once when I was using the device.

I did have one issue when doing the above, once I clicked exit and save configuration it kept going into the UEFI screen (step 3) and in order for me to get it to boot correctly I had to have it shut down completely (holding the power button to fully shut down).  Then instead of pressing power button and volume up together as in step 2, I pressed the power button and volume down and it seemed to then boot into Windows i.e. when the surface screen appeared the circle progress appeared below it.

Let me know if this helps.  I think it will do the trick.

Merry Christmas and have a good New Year!

Thanks

Mark

My surface pro has rebooted twice today with the kernel-power error in the event log. First time it happens the keyboard wasn't attached. Second time the keyboard was attached and folded back. Its happened a few times before