Acer AO1-431-C8G8 can't boot after hibernating

IsaacBrave22

Hi there. Could anyone help me on this problem: I have Acer AO1-431-C8G8 but when I hibernate and try to boot it again, it ends on displaying a Windows logo until I force restart! 

{ edited the title to add model name } 

JackE

Hibernate is buggy. Use sleep mode instead.

IsaacBrave22

Thanks Jack
I like hibernation but it seems I'll have to forego it and use sleep only 

JackE

Yeah, I use sleep only on mine even if I'm not using the thing for a day or so. Some users, not many, claim that changing fast startup mode in Control Panel's power button app fixed it for them.

 Hibernation is no longer an option in the Windows start menu   Only sleep, restart & shutdown. Same in Linux. Sleep/suspend uses such little power to maintain a session --- not much more than fast startup --- that writing a session to  a hiberfil.sys file on a disk doesn't offer much of an advantage.

This is especially so if your disk space is limited like on most cloudbooks. Hiberfil.sys might get corrupted or truncated since it can get pretty big. Then you're gonna have booting problems if it's corrupted.

Furthermore, waking a session from sleep mode that's still in RAM is a whole lot faster than loading a session back to RAM from hiberfile.sys  even on a relatively fast SSD.  

Easwar

Hi @IsaacBrave22,

Check here

https://answers.microsoft.com/en-us/windows/forum/all/windows-10-want-boot-after-hibernation/edc3bc77-4d8a-4511-8079-54c6768a9a0c

JackE

Yeah, I use sleep only on mine even if I'm not using the thing for a day or so. Some users, not many, claim that changing fast startup mode in Control Panel's power button app fixed it for them.

 Hibernation is no longer an option in the Windows start menu   Only sleep, restart & shutdown. Same in Linux. Sleep/suspend uses such little power to maintain a session --- not much more than fast startup --- that writing a session to  a hiberfil.sys file on a disk doesn't offer much of an advantage.

This is especially so if your disk space is limited like on most cloudbooks. Hiberfil.sys might get corrupted or truncated since it can get pretty big. Then you're gonna have booting problems if it's corrupted.

Furthermore, waking a session from sleep mode that's still in RAM is a whole lot faster than loading a session back to RAM from hiberfile.sys  even on a relatively fast SSD.