February 23, 2016 at 7:25 am #2077
Surfacebook i5,256,8, dGPU here. the last couple of days ive noticed that my computer has turned off on its own. ive walked away and after coming back to it the screen is dark as it usually is when it goes to sleep however it wouldnt wake up and so i hit the power button only to find it booting. i looked in the windows log – system for errors and i have found the following
Log Name: System
Date: 2/21/2016 4:04:16 PM
Event ID: 6008
Task Category: None
The previous system shutdown at 3:00:53 PM on 2/21/2016 was unexpected.
as well as this:
Log Name: System
Date: 2/21/2016 7:55:46 AM
Event ID: 41
Task Category: (63)
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
on several occasions. I hope you guys can halp me with this as i’m using the SB for classes.
February 23, 2016 at 12:11 pm #2096
OK, there’s probably something causing your system to restart, it might be an app or other program. Here’s a MS KB on the subject…
Here’s a quick workaround that might help keep it from restarting so you can see what’s going wrong:
– Search for Advanced system settings (the Control Panel version).
– Select the Startup and Recovery section, then Settings.
– Click to clear the Automatically restart check box.
I’d also run a SFC and chkdsk just on case it’s some corruption…
You may want to consider restoring to a system restore point and/or removing any software/updates you installed just before the problems started.
If that doesn’t help, run a battery report to make sure it’s not simply running out of power (weirder things have happened).
Unfortunately, it is possible that you’re having a hardware issue. If so, you might need to talk to Microsoft.
March 2, 2016 at 9:39 pm #2147
i really really want to love the surface book but it is giving me so many issues. i realize its a gen 1 device running a brand new version of windows but really they should have kept win 10 as a beta until they got the majority of the kinks worked out of it (like 99.5+% of the bugs). i did run SFC as per your suggestion and lo and behold it did find corrupt files some of which it claims to have repaired and there were others that it said it couldn’t fix ( so i guess im going to have to wipe the device and do a clean install… it mentioned cbs.log for more information which i looked at and that was pointless since it’s chock full of technical information that IT specialists and software engineers only would understand. i sincerely hope that all of this is a software issue and not a hardware issue. Because for the amount of money that i invested in this device i should get more than 2 Mo of hassle free operation out of it.
March 4, 2016 at 10:42 am #2151
Frankly, I agree with you that there have been problems that should not have happened with the Surface Book and SP4.
I hope a reset works for you.
March 4, 2016 at 6:00 pm #2156
Heh. I backed up the small number of files on it (thankfully an easy task) and I did do a reset and had it remove everything. A couple of hours later after it was all finished and back up and running the same event occurred. Looking at the system log I saw the same type of errors I saw before the reset. After that I got on the phone with MS support and they had me do another reset although different than the one I did. That’s where I am right now. Hopefully the issue is resolved because I don’t know whats left to do other than nuking the device and starting from scratch with a clean install of win 10 and downloading the recovery image… maybe it’s the image that was corrupt? I really don’t know and time will tell. Luckily I can do classwork on an ancient Sony Vaio in the interim.
- This reply was modified 1 year, 8 months ago by Jonathan S.
March 8, 2016 at 9:51 am #2165
Sorry for the gap in responses, had a lot of visitors here.
Anyway, did the second reset from a different source work?
March 8, 2016 at 11:29 pm #2166
Unfortunately it did not. In fact that same problem still occurs with a myriad of new problems. I thought that it might be the recovery partition that has corrupt files on it because I ran sfc a couple hours after the reset and it found corrupt files. On my other PC I downloaded the recovery image for the surface book using my serial so it would get me the right one. While that downloaded I nuked the surface in preparations for loading the new image. after that and everything looked back to normal the computer was fine for a day and then shut down unexpectedly. I don’t have the time or resources to fully pick this thing apart since I have school, an internship and a job so I think i’m going to ask for an RMA and try and get a new one. I’m kind of bummed because when this thing worked it worked great. I knew what I was getting into with a Gen 1 device on a brand new OS glitches were inevitably going to happen… Drivers and minor updates I can wait for but I think this is quite a bit more serious since the Microsoft tech support guy I spent the better part of a day with said that this was a pretty uncommon issue. I’m not giving up on the SB yet just the one on my desk I’m typing at right now.
March 10, 2016 at 9:27 am #2191
Yeah, I think an exchange is the way to go at this point.
March 20, 2016 at 1:25 am #2224
So i got an RMA from MS tech support and i requested that i exchange it at a local MS store which i did. i unboxed the new device at the store so i could verify that the replacement was brand new, which it was. i took it home and 8 hours after the initial power on the very same error happened again. what are the odds of getting two defective units suffering from the same exact issue? i never got a chance to test it out before updating the system so i wonder if it is the updates that are causing this problem.. is there anyway i can send you the windows logs to you to take a look at because all MS tech support is going to do is tell me to reset the device which will do nothing since 3x on the last device did absolutely nothing. the SB was plugged in all day, i stepped away from it and returned later today (hours later) the screen was dark and i figured it was sleeping. it wouldn’t wake up so i powered it on and checked the windows log where it stated that it hadn’t shutdown cleanly… The computer has never restarted or shutdown on me while i’ve been working on it. only when i go away for some extended period of time.
- This reply was modified 1 year, 8 months ago by Jonathan S. Reason: add some addl information
March 29, 2016 at 10:24 am #2254
Well I got the replacement device at a MS store in Palo Alto and everything is up to date now. I have found that after disabling sleep (preventing it from ever going to sleep) has resulted in the issue not reoccurring. Is anyone else experiencing this issue or is it even a known issue? I have not used a hibernate feature just sleep. I fear that now some windows files are corrupted after the unexpected shutdowns about a week ago. I suppose I can learn to deal with not letting the device sleep and instead just shutting it down however I really would like this problem to get fixed as it’s somewhat inconvenient and MS really should tackle this particular problem over some of the lesser issues that have been reported.
May 13, 2016 at 11:26 am #2323
I’ve noticed a similar issue with my SP4 which would lead me to believe this is a Windows 10 issue and not a Surface Book issue, especially considering that you’ve experienced this on multiple Books. For me I’m not too inconvenienced by it because the SP4 starts up so very quickly, but it shouldn’t be happening at all.
You must be logged in to reply to this topic.