SurfaceBook Crashes/Shutdowns During Sleep

As many of you have posted the SB will consistently crash at some point during sleep. In my case it had been taking 3-4 hours in Sleep. Recently it started doing it after an hour or so in Sleep. I haven't changed anything. Yes, all updates are installed and I've tried all the potential "fixes" (sfc followed by DSIM using a clean image, disable Fast Startup, turn off WiFi connected while in Sleep, etc.). So back to the MS Store I went. They took a look at the Event log, which had dozens of Critical Errors related to the Sleep crash and hundreds of other errors and warnings. They reviewed the settings and checked the drivers and updates. They have seen this happen before on my multiple SBs. In the past they would say it had to be a hardware problem and swap out the SB.

I want to say that the staff at the MS stores deserve credit for being really great about doing what they can to support me, but it almost always results in a SB replacement that ultimately has the same issues.

This time my visit to the store was different. After confirming the latest SB exchange hadn't solved the Sleep problem they surprised me by suggesting that maybe the SB wasn't the best PC for my needs asking "might I prefer a different PC such as a Dell XPS or Lenovo?" I wasn't sure how to respond. They won't (can't?) say that there are issues with the SB, but trying to steer me away from it when they know I purchased the SB specifically for its features was unexpected and telling. I left the store saying I would think about it.

Has anyone else has had a similar experience?

For now I assume Sleep will fail. So I have turned off Sleep and I shut down the SB when I will not be using it for an extended period. Annoying that I cannot use Sleep, but it isn't a big issue as I don't use the SB for anything but browsing. I won't load my Apps or use it for work until/if the SB shows better stability. I travel frequently so Sleep is critical to my work use of a notebook PC.

Yeah I agree with you on the whole intel is probably at fault part. Ive been suspecting a hardware issue for awhile now but the skylake chip issues on other devices as well all point fingers at intel.

Yeah I've already tried EVERY solution you have tried and it still hasn't worked. Its completely stupid that Microsoft can't even fix their own products. Also the fact that they are COMPLETELY silent on this issue is really a sign that there are probably a lot more problems with surface devices that they don't want people to figure out. I'm never purchasing another surface device again. At one point when the surface phone rumors were goin crazy I decided I was gonna get it but after this gongshow, I doubt that will happen. I'm pretty sure I'm not the only one that feels like this.

You know what's funny dude I think their silence has something to do with Intel... All of a sudden Intel has ditched their Tick Tock production method and plan on adding an addition period were they further "improve" on their chipset architecture. This happened all of a sudden after the skylake APUs came about.

Every windows laptop with these later skylake-U processors are experiencing screen flickering and other power related/stability issues. The dell xps 13/15, lenovo yoga ect..... Im starting to wonder if Microsoft knows its a hardware issue and that they have to simply play it out kinda like how the xbox 360 RROD fiasco panned out. They wouldn't be able to fix a design flaw on Intel's side hence the ongoing 5+ months of unresolved issues. They haven't even fixed the sleeping issue. All they've done is removed it and replaced the sleep function for hibernation.

This reminds me of the Ford Pinto bs where Ford Motors payed out royalties to the affected family members who had the balls to sue instead of recalling all of the faulty vehicles and fixing the design flaw. One of my old college professors years back explained how it was cheaper for them to simply pay the individuals/family's off who were injured or experienced a death vs's recalling all the vehicles and fixing them.

If this indeed is a design fault on intel's side I won't be surprised is the same technique will be applied for this as after the 30 days you are basically stuck with it.

I get the same issue, but more often when I put the screen on the backwards.  The time it takes to start makes me think the computer turned off.