2020. 2. 8. 18:43ㆍ카테고리 없음
- Crashes: Column Width After Sleep/wake Reset Morehead
- Crashes: Column Width After Sleep/wake Reset More Than
Photo by groenmen. Who wouldn’t want more sleep? We live in a 24/7 world where the work of the day doesn’t have to end when it gets dark, work can start long before the sun comes up, and even. Acer Aspire R3-131T. Whenever laptop goes to sleep, it crashes when I wake it up. Happens regardless of method used to put it to sleep or to wake it up. I have tried NUMEROUS things to fix. I have spent COUNTLESS hours searching the internet. I have updated drivers, uninstalled drivers, reinstalled drivers, and even REINSTALLED WINDOWS 10.
Does anyone else have a Mac that crashes often when in sleep mode? My iMac crashes about 2 times per day while in sleep mode, now. My iMac is updated to macOS 10.13.4, but the problem has existed for at least 1 previous version of macOS. The crash report lists this - Event: Sleep Wake Failure. I talked to Apple phone support - no help unfortunately. Apple told me to try disabling the 'Put hard disk to sleep when possible' feature, but that did not fix the issue. I report every crash to Apple; seems to fall on deaf ears in Cupertino.
I can post the crash logs if they do not contain any sensitive data. Does anyone have a solution? Click to expand.I also have the same problem. It started after updating my MacBook Pro 17' (mid 2010) to 10.13.4. I does not matter if my second screen is connected or not.
I does not matter if the power cord is connected or not. My mac is always connected to the power so the battery is always full.
FileVault is not enabled (I saw some reply's saying that disabling this option solved this issue). Resetting SMC and PRAM also has not a positive result.
Since the update to 10.13.4 my Magic Trackpad 2 started stuttering when using it wireless. When my trackpad is wired, it works fine. But that's not why I spend a lot of money on that device:-( I was planning to reinstall my OS but I have read that other users have done that without succes. For now I have configured my mac Computer Sleep time to 'Never' in the Energy Saver settings. That means that I have to shut down my mac every time I'm not using it. I hope Apple fixes this issue soon.
Click to expand.When I re-encrypted the drive, the same error started to occur. So the only 'workaround' at the moment is to completely disable FileVault, which I am not happy about. I am not convinced Apple will fix it in the next update so I won't get my hopes up. For something as simple as this they should be able to issue a patch.
I guess it needs more of us to make a noise. Maybe MacRumors could pick this issue up and put it on their front page to get some coverage? The only thing I haven't tried is to do a clean-install of macOS on my iMac but I just don't have the time available to do that. When I re-encrypted the drive, the same error started to occur. So the only 'workaround' at the moment is to completely disable FileVault, which I am not happy about. I am not convinced Apple will fix it in the next update so I won't get my hopes up.
For something as simple as this they should be able to issue a patch. I guess it needs more of us to make a noise. Maybe MacRumors could pick this issue up and put it on their front page to get some coverage? The only thing I haven't tried is to do a clean-install of macOS on my iMac but I just don't have the time available to do that. When I re-encrypted the drive, the same error started to occur. So the only 'workaround' at the moment is to completely disable FileVault, which I am not happy about. I am not convinced Apple will fix it in the next update so I won't get my hopes up.
For something as simple as this they should be able to issue a patch. I guess it needs more of us to make a noise. Maybe MacRumors could pick this issue up and put it on their front page to get some coverage? The only thing I haven't tried is to do a clean-install of macOS on my iMac but I just don't have the time available to do that. Click to expand.The 10.13.5 beta appears to fix this problem.
I haven't had a chance to try myself but reports from the Apple support thread linked on the first page has some responses indicating as such. I simply reverted to 10.13.3 and am waiting until 10.13.5 is released because disabling File Vault is an unacceptable workaround in my books. There are three stages of Mac sleep: sleep, standby/auto-off, and hibernate. They're a little muddy to explain, but on Mac notebooks, standby kicks in after 3 hours by default and auto-off after 6 hours. The default on Mac notebooks is also to have 'safe sleep' enabled.
This is basically hibernation mode=3 in pmset. RAM remains powered for 3-6 hours but backs up the RAM to the disk just in case the power dies in those 3/6 hours, then goes into the lower power state and relies on the hibernate image to resume. Basic sleep still works in 10.13.4 and File Vault. Disabling standby and auto-off (they're basically the same thing) prevents the writing of the hibernation image to the disk, which is there in case the power to the RAM gets cut for some reason.
With the default behavior for sleep, the Mac will cut power to the RAM after 3/6 hours to save battery and rely on the saved hibernation image to resume. This behavior is broken in 10.13.4 with File Vault enabled. So, you can still do basic sleep with 10.13.4 + File Vault, but after three or six hours your Mac will crash unless you disable standby and auto-off. On Mac desktops, the default sleep behavior is to not save a hibernation image at all since there is no battery (hibernation mode =0 I think), so I have no issues with waking from sleep on my iMac on 10.13.4 + File Vault. The 10.13.5 beta appears to fix this problem. I haven't had a chance to try myself but reports from the Apple support thread linked on the first page has some responses indicating as such.
I simply reverted to 10.13.3 and am waiting until 10.13.5 is released because disabling File Vault is an unacceptable workaround in my books. There are three stages of Mac sleep: sleep, standby/auto-off, and hibernate. They're a little muddy to explain, but on Mac notebooks, standby kicks in after 3 hours by default and auto-off after 6 hours. The default on Mac notebooks is also to have 'safe sleep' enabled. This is basically hibernation mode=3 in pmset. RAM remains powered for 3-6 hours but backs up the RAM to the disk just in case the power dies in those 3/6 hours, then goes into the lower power state and relies on the hibernate image to resume. Basic sleep still works in 10.13.4 and File Vault.
Disabling standby and auto-off (they're basically the same thing) prevents the writing of the hibernation image to the disk, which is there in case the power to the RAM gets cut for some reason. With the default behavior for sleep, the Mac will cut power to the RAM after 3/6 hours to save battery and rely on the saved hibernation image to resume. This behavior is broken in 10.13.4 with File Vault enabled. So, you can still do basic sleep with 10.13.4 + File Vault, but after three or six hours your Mac will crash unless you disable standby and auto-off. On Mac desktops, the default sleep behavior is to not save a hibernation image at all since there is no battery (hibernation mode =0 I think), so I have no issues with waking from sleep on my iMac on 10.13.4 + File Vault. Click to expand.I can confirm this. I've re-enabled FileVault on my iMac with fusion drive and set both sleep and autoshutdown values to 0, it no longer crashes after sleeping for a few hours.
I note you said you never had a problem with your iMac as it's default hibernation mode is 0, I'm wondering if the fact mine is an EU sourced one is the difference here. According to the man page for pmset, EU law mandates more severe default power saving measures - sleep and autoshutdown both did default to 1 on mine even with hibernate set to 0. I'm getting this on my MacBook Pro (Retina, 15-inch, Mid 2015) and I've never used FileVault, so it's not that. It happened after the update to 10.13.4 - I think. I can't remember this happening before then. I've tried every combination of which-way-what (Energy Saver settings, etc) but nothing cures it. Even tried clean install, but the problem persists.
Close the lid, odds on, later on in the day or next morning, it's rebooted with the 'send to Apple' guff. It's like there seems absolutely nothing I can do.
Crashes: Column Width After Sleep/wake Reset Morehead
Just hoping that 10.13.5 might do something, but my iMac has same OS version and never shows it. How can that be? I'm getting this on my MacBook Pro (Retina, 15-inch, Mid 2015) and I've never used FileVault, so it's not that. It happened after the update to 10.13.4 - I think.
I can't remember this happening before then. I've tried every combination of which-way-what (Energy Saver settings, etc) but nothing cures it. Even tried clean install, but the problem persists. Close the lid, odds on, later on in the day or next morning, it's rebooted with the 'send to Apple' guff. It's like there seems absolutely nothing I can do. Just hoping that 10.13.5 might do something, but my iMac has same OS version and never shows it. How can that be?
Ok, so it seems I am not alone here. I used to have this issue maybe once every few 4, 5 months. This has now happened twice in 5 days. I'm running 10.11.6, El Capitan on a 2012 iMac. I did a Apple Security update maybe a few weeks ago when it came out (I forgot the darn date). The restart for that took an awful long time, I almost thought the update messed up things up.
Crashes: Column Width After Sleep/wake Reset More Than
The only thing that changed on the Mac before this latest 'Sleep Wake Fail' last might was I installed some software, drivers install for my new Canon printer.