Surface Pro 2 previously on Win 8.1 and now on Win 10.
The complete reboot happens for me when the Type Cover 2 is jarred against the Surface Pro, possibly resulting in a quick disconnect/re-connection.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I just noticed this recently but sometimes I get a Random reboot not even doing anything particular. I also noticed twice that when I attached my Type Cover 2 it reboots. Example I attached it and the SURFACE logo shows and it boots up.
Anyone else experiencing this.?
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.
Surface Pro 2 previously on Win 8.1 and now on Win 10.
The complete reboot happens for me when the Type Cover 2 is jarred against the Surface Pro, possibly resulting in a quick disconnect/re-connection.
This has never happened on a Surface 3 or Surface Pro 3 that I've seen.
This also stopped happening on my Surface Pro 1 after upgrading it to Windows 10.
What is more ridiculous is that this problem has been present for an entire year with absolutely no fix from M$. You quite simply don't have to put up with this kind of unreliability in other products. I am seriously considering abandoning the Surface line of products, it is a great concept but damn it is unstable. Perhaps Apple will someday make a Surface clone that is actually stable. What is the point of a detachable keyboard if the damn thing keeps crashing as soon as you touch it.
Yep I get it too, I think when browsing with Chrome mostly (sometimes FireFox). Sykpe is running too. Can't pin it down to what it is. Will be good to know what is causing this as I have live DJ performances and don't want this happening mid set!
My problem has vanished after I manually downloaded the Surface driver and firmware zip bundle and manually installed the Type Cover 2 and Touch Cover 2 drivers using the .inf files. Perhaps it was failed driver update that kept the problem reproducing.