Would expect Framework to provide a response especially when they think Framework for Business is going to work. Simple issues like this will circulate fast. [@twittsgibber]
After almost one year using a framework laptop 12th gen intel i7, I did a clean install of windows 11. No restores in user profiles, only restored %appdata% and installed the Framework recommended drivers, download from this site.
On the old install neither “not so modern” standby nor hibernate works as expected (Modern standby results in crashed windows and hibernate resumes spontaneously).
Modern standby is the first now being tested and behaves as expected, modern crashed.
This just does not work, I think it is a big fail, as it removes a big part of the using pleasure. Nothing is broken, but still this is very very annoying.
Is there some action in this topic from R&D, in cooperation with (I suspect) Intel?
I hope there is, otherwise this is not business ready.
This is frustrating a lot of users now, hope this still has attention from Framework!
2 Likes
Is there any progress on this issue or even a little bit of information you could share?
A very unconfirmed thing to try: on my unit Win11 would shut off completely (presumably) when switching to hibernation from sleep.
Ever since I first disabled hibernation (in order to confirm that sleep itself was working well) and enabled it again it seems to work.
To do so I opened an admin command prompt and entered “powercfg /hibernate off”, reboot, then the same with “powercfg /hibernate on”, and reboot again.
Very unconfirmed and I didn’t do any specific testing in that regard.
Are you sure this is the same issue?
We have been having problems with the laptop shutting down during sleep and hasn’t been going into hibernation first.
Hello all,
We haven’t yet found a way to reliably reproduce this issue to be able to root cause it, and the logs provide by those affected also don’t point to a root cause. We have seen reports of other Windows-based laptops experiencing similar issues, but we have not ruled out that there could be a firmware or hardware root cause. We encourage anyone seeing this to provide details in this thread as requested and we’ll continue to investigate. When we have a way to reproduce this or are otherwise able to determine a root cause, if it’s something Framework can address, rest assured we will do so and communicate a plan to the Community. At this time, we do not have an update to share.
Also, just to set expectations, direct pinging me or Framework in threads does not guarantee a response. If and when we have meaningful/tangible updates to share, we absolutely will.
Thanks!
4 Likes
Hi @TheTwistgibber ,
Thanks for your answer but it is not giving any comfort.
A thread like this one is going on for more than a year, with lots of people having the same behavior and this can not be reproduced? Hardware has been swapped by multiple users (no result), USB-C accesoiries have been put aside with no results, so you can not rule out hardware?
I’ve had some years of experience in this business as the most buyers have (tech enthusiasts), but this is not reproducible?
To me this sounds more like a shortage of resources on your part.
Again, this is not giving any comfort and trust this will be resolved.
So please do better!
1 Like
Typically “reproducing” a behavior means to guarantee a certain behavior happens everytime, when a set of conditions are met, not just to observe the behavior once.
Reliably reproducing a behavior is hard. From the post above, people certainly cannot repoduce such behavior. And it doesn’t seem like a easily reproducible problem to me.
1 Like
I’m not convinced. I do have the idea that a lot of members in this topic have similarities and can therefore be reproduced or further investigated to understand the differences.
Either am I missing the listing in what situations Framework self has been testing or what symptoms have been collected, with what circumstances.
So when willing to fix this, more can be shown then asking to report.
I think this needs a better approach then an incidental forumpost from Framework emplyees.
Sharing a (read only) kanban board would be a better approach, following different users in troubleshooting as wel as documenting what has been tested.
If a thread like this consumes too much time, it is not going to be effective anymore, hence the missing solution.
On my machine, I can reproduce it every time it’s in sleep mode for more than a few hours as long as S0 sleep is enabled. If there is something specific that Framework support needs or wants me to try, I’d be more than happy to do so. My logs as well as some speculations are linked above.
I think what makes this hard is that it might be more than one problem as evidenced by different fixes working for different people.
2 Likes
I got my new 7840U mainboard.
It still shutsdown during sleep. How? Why ?
I pre-ordered a ryzen mainboard hoping it would fix it
It must be an OS or battery issue?
I was using a new Windows 11 install with the 7840U, and I tested my 12th gen Intel laptop with the battery disconnected, which still did not prevent the laptop from shutting down.
Wow that is very strange. I can’t imagine what else it could be.
At this point I’m thinking of cancelling my preorder and just getting another laptop.
1 Like
Two more instances of the 7840U mainboard shutting down now. Tried disabling memory core isolation to no avail.
1 Like
My Framework Laptop 13 has had this issue since day 1 when using the usb c cable connected to 2 x Dell Monitors and therefore is readily reproducible. I would be more than happy for Framework to remotely install monitoring software to capture the issue and track to the source. The conclusion that this is not readily reproducible is nonsensical given its persistence and it would be reasonable to conclude that those in this community are more advanced IT users / professionals given the nature of the product they have purchased + the community responses to date in an attempt to resolve.
1 Like
Lack of support for such a simple issue is perhaps indicative of the immaturity of the framework model unfortunately. The fact that no solution at all has been proposed or attempted to be found is evidence of the approach despite the community being willing to help with extensive logging and different hardware / software combinations.
1 Like
I have this intermittently happen on my i7-1260P. I feel like this more of a Windows 11 issue than a Framework issue personally given that it’s not consistent. Still very annoying!
Definitely not exclusive to Windows 11. I’m seeing it consistently on Windows 10. Then again, I still think there’s more than one issue.
2 Likes
Has anyone had this happen recently, it’s been about a month and a half since I last noticed it.