06-15-2017 04:32 PM - edited 06-15-2017 07:13 PM
Over the past several years there are many posts of users experiencing variations on this problem with X1 Carbon and X1 Yoga of various generations, including the latest ones (I provide a list below). That is, the systems often cannot come out of sleep mode in some way, shape, or form.
I had this problem on my own brand-new X1 Carbon 5th Generation, right out of the box. In my instance, I noticed this issue in the following two scenarios:
Under both conditions:
With my machine, this was happening about 25% of the time when it would go into sleep mode -- this completely defeats the purpose of having a "portable" laptop if you can't depend on it waking up. On the freezing during boot, I would say that it was much less common, maybe 10% of the time.
After a couple of tech support calls, tech support surmised it was a faulty motherboard that needed to be replaced. To have a brand-new laptop needing a motherboard replacement was disappointing, and it was also clear that it wasn't even certain that that would solve the issue. When I offered to send my system's event logs, they weren't interested. Given the raft of similar issues I have found on this forum (see list below), is it really plausible that the production process at Lenovo is so bad that faulty motherboards are created often? Seems unlikely, and nevertheless, several of the past posts say that replacing the motherboard didn't even solve the problem. So it seems the problem lays somewhere else.
I'm writing to ask Lenovo staff -- are you even aware that this is a multi-generational crashing issue?
I have to ask the question because it keeps on coming up even to the present day, so it seems as if the root of the problem has not yet been addressed -- here's my compilation of topics related to this issue, some of which date back over 3 years:
Many thanks in advance!
06-15-2017 07:36 PM
The automatic forum SPAM filter moved your post aside, because it had so many links in it I think. With some help I was able to get it back. The other multiple posts on the same subject have been moved aside - it's just too hard to follow a discussion when it's splintered across threads.
I have had and still have several X1 Carbon's and X1 Yoga's and have not seen any of these problems. Do you have any thoughts on how to reproduce it?
06-15-2017 08:15 PM - edited 06-15-2017 08:30 PM
Thanks for rescuing the post. In my research for this, I had responded to a few of those posts I listed, and it seems I guess that they were all caught in the filter.
Now regarding reproducing the problem, it really felt random as to when it would occur. It could happen both when I would "manually" put the machine to sleep (i.e. close the lid), as well as when the machine would automatically go to sleep after being unattended. In all cases, I also note that I was not really doing anything particularly taxing beforehand (just either maybe MS Office or web browsing). It was impossible to predict when the next wake up would fail, or to do a sequence of steps to ensure it to not wake up (or at least I didn't try hard enough!).
Just to add further colour, the specific details of my X1 Carbon 5th gen were:
Are any of those machines configured with some of the elements I listed above?
As I alluded to in my first post, I actually had saved the Windows Event logs around the times of the crash. Some things I had noted before/after the crash in there:
I'm happy to hear that you have several X1s that are not behaving in this way -- it gives me confidence to order a new one at some point. I'm on a Yoga 3 Pro from 2014 and it is really time for a new and fast machine!
06-15-2017 09:12 PM - edited 06-16-2017 05:41 AM
Please stop making multiple posts across the community on the same subject. It makes any discussion impossible to follow. Thank you.
Let's continue the discussioin here!
06-16-2017 06:29 AM
06-16-2017 06:58 AM - edited 06-16-2017 07:37 AM
In my Event logs, I didn't see anything regarding the LockApp, but I will note that in my case right before the "The previous system shutdown at HH: MM: SS on DD/MM/YYY was unexpected.", it also had an error from AppModel-Runtime: "App Container profile failed with error 0x800700B7 because it was unable to register the AppContainer SID." Not sure how relevant that is.
06-16-2017 07:38 AM
I don't see any errors in the AppModel-Runtime log.
Just to clarify in case you want to look (and we aren't 100% sure these things are even related), we'll see 3 errors in the Apps | Microsoft-Windows-TWinUI/Operational log related to Microsoft.Lockapp_cw5n1h2txyewy!WindowsDefaultLockScreen usually refering to "remote procedure call failed.."
06-16-2017 08:35 AM
Do your machines have NVMe SSDs?
I also found this thread with something similar seemingly being caused by the SSD it seems (and a BIOS update fixed it):
06-16-2017 09:10 AM
06-21-2017 04:07 PM
Anyone at Lenovo read this/aware of this as a mutli-generational issue?
A Lenovo staff had replied to a recent post with a similar issue, but that is also not resolved (X1G5 fails to wake up).