This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
My SB (i5, 256gb, 8gb, GeforceGPU) keeps crashing/freezing during sleep which causes it to shut down. According to the windows reliability monitor it has been happening every day multiple time.
I though I was going crazy because I clearly remember not turning it off before putting it to sleep. I recently had my original SB replaced with a new one which fixed most of the issues from blue screens to flickering that would not go away. But this new one still has the Hello Camera issue where it wont turn on during startup and this new problem that has popped up.
Is this caused by a hardware defect? I really don't want to drive 23km to the other side of my city to get another replacement at a Microsoft store if the issues aren't resolved. Here's an image on the report. As you can see, there are 17 critical events today not to mention all the other days as well. Thanks.
If anyone has a solution that isn't a complete factory reset or system reinstall (I've tried them before) that would be great.
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.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
Thank you for raising these problems, I have exactly the same situation with my SB ever since I bought the machine. I also tried many solutions but none of them helped a bit. It's ridiculous that Microsoft is not communicating with us properly. I love the machine and waiting for a firmware/driver fix that would solve this, but when Microsoft is not even acknowledging problems my hopes remain slim that these issues will be fixed in the short term. Microsoft technical support, please reply to us!
Thanks for the reply. I'll try a DSIM again enable Hibernation as per the default (2 hours) and see what happens. Last time I tried Hibernation the Hello Camera stopped working until I did a restart.
My experience is the same as yours, Duneman. I don't think there is another factor here -- the issue is with the SB and its inability to sleep and wake from sleep or hibernation 100% correctly. Yes, my SB wakes almost every time (though sometimes if it has crashed during sleep, it will be a full boot sequence), but I can replicate the sleep/hibernation issues easily. I have done a DISM fix, too. My system stability is 1000x better after that (haven't seen any BSODs since then). But, just because it "wakes" does not mean everything is working completely correctly, which is where my issues are. If it wakes at all, that's only half the battle. After that, will the Hello camera work? Will the detach sequence work correctly? The answer for me is not always.
MS store employees are probably steering you away from the SB due to your repeated issues and they don't want to keep exchanging SBs for you, knowing (likely) that the issue is firmware related.
Thanks for the reply. I'll try a DSIM again enable Hibernation as per the default (2 hours) and see what happens. Last time I tried Hibernation the Hello Camera stopped working until I did a restart.
Very strange attitude for them to take, and does not bode well.
I am having a much better sleep experience - 10 out of 10 times it will gracefully awake from sleep upon lid opening. And if it is sleeping for 2 hrs it will migrate to hibernation as specified, and 9 out of 10 times it will subsequently restart from migration as it should. I had put that down to a DSIM rebuild - but you say you've done that, so there must be another factor(s) in play here...
