Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iMac doesn't wake up from deep sleep after Ventura update

chonkvandelay

chonkvandelay

macrumors newbie
Original poster
Oct 13, 2020
19
93
Turkey
Hello,
I updated my MacOS to Ventura 2 days ago. My iMac can go sleep and wake up without any issues for shorter periods. But if computer sleeps more than 3 or 4 hours it doesn't wake up at all. I have to force shutdown and turn on again.

It started just after new update. I tried to unplug power cable and wait for a while to reset something. But it did not work. What could be the problem? Is it just me or anyone else having same trouble too?
 
  • Sad
  • Like
Reactions: itsice and sorgo †
Experiencing the same issue. Tried unplugging to reset SMC and also resetting the NVRAM and nothing seems to fix it. Ive had to force shut it down and boot it back up to use my machine.
 
I am having the exact same issue and its driving me mad. I have a 27" iMac 2015 5K (4GHz Quad core i7) - using the Open Core Legacy patcher.

I have reset the NVRAM, SMC, and I also reset the Ventura power configuration using the Terminal sudo command to no avail.
 
Last edited:
Hi! I'm having same problem: installed Ventura 13.0 last week and wake up times after "sleep" mode are getting longer and longer. Now it stays a black screen without sign of life for full two minutes. It does still wake up. Have done a clean up with ONYX app, ran mac Disk Utilities repair, have moved and deleted files in order to free up space - but to no avail. iMac Retina 5k, 27 inch 2017
 
…As no clue is provided, and we keep trying the usual procedure (smc, pram, onyx, etc.) I would suggest the only thing that fixed a problem with FaceTime in my iMac (Monterey still):
boot in safe mode & restart again in normal mode. I believe some disk repair (deeper than Disk Utility’s) is done in the process.
It’s no harm, not too long, easy, … and must be added to the list of first-aid measures we all are used to. I don’t have the problem, but I keep finding this fix here & there for odd behaviors like that. Another usual thing to try.

(I’m still waiting to upgrade to Ventura, reading these posts to know what’s happening. I don’t usually find the “safe boot” thing, so I bring my personal experience about this step, which I think has to enter the “normal repairing” things to try).
 
Same problem here with an M1 Mini and a Pro XDR. It was a heart stopping moment when my monitor wouldn't come on after a night of sleep. And a boot. And another and another... But connecting it to another Mac gave that the display was ok. After I came off my defibrillator, I relaxed and started troubleshooting. I can boot the M1, THEN plug in the monitor and it usually comes up. Unfortunately, that fix is not going to work for your iMac.

It also doesn't fix the myriad of other problems, the worst is that "Finder is no longer responding." That problem gets worse when you force quit finder, then have a desktop with no icons at all to restart it - at least in the GUI.

Barfo to the QC people in the big ring.

Edit 12/29/22
Some more edification to the above. Turns out the trigger for the blank display was two 3.0 hubs plugged into the XDR. It still must be a Ventura problem since that configuration was used for about a year prior to MacOS 13. With both unplugged the system acts normally. I have one hub plugged into the spare TB port on the M1 and with no problem. Haven't taken the troubleshooting any further yet since I don't need the spare hub to be active at the moment.

The other issues have mostly disappeared with the last update. Fortunately, the the "Finder is no longer responding." problem hasn't come back. That was a gen-u-wine PITA.
 
Last edited:
Hi everyone,

I have some good news, installing the latest MacOS Ventura 13.1 public beta seems to have resolved the issue for me. My iMac has been running stable for 4 days now and wakes from sleep every time as normal.
 
I thought I was the only one suffering from this issues with my iMac 2017 Retina 5K 27'' 3.8. I did install the latest Ventura Beta 13.1, but it didn't fix the issue of the waking up from a sleep after 30mins. I also noticed a issue with Notification Center looping messages of apps under "Allow in the Background" displaying multiple times. This only started after I loaded the 13.1 Beta, it didn't happen with the 13.1 regular update. I reported that as well using the Feedback Assistance to Apple. Defintely, the bigger issues is the sleep wake issue.
 
Same as above (the sleep no wake issue and the app notifications) for my M1, 2021 iMac 24" on Ventura 13...and 13.1 Beta. Just deployed 13.1 Beat 2....we'll see.
 
fisherking said:
what happens? you're following the correct steps for a silicon mac?
Click to expand...
When i get to step 4 of this...I don't see the option for "continue in safe mode"....I just see continue (even when holding down shift)....https://www.macrumors.com/how-to/start-up-safe-mode-apple-silicon-mac/
 
itsice said:
When i get to step 4 of this...I don't see the option for "continue in safe mode"....I just see continue (even when holding down shift)....https://www.macrumors.com/how-to/start-up-safe-mode-apple-silicon-mac/
Click to expand...
Some banter on reddit that this may be linked to users running backblaze...I'm one of those.
 
itsice said:
When i get to step 4 of this...I don't see the option for "continue in safe mode"....I just see continue (even when holding down shift)....https://www.macrumors.com/how-to/start-up-safe-mode-apple-silicon-mac/
Click to expand...
huh, haven't tried it on my M2 air yet. meanwhile... what happens if you disable backblaze?...
 
fisherking said:
huh, haven't tried it on my M2 air yet. meanwhile... what happens if you disable backblaze?...
Click to expand...
Got safe mode to work. After starting in safe mode and setting backblaze to run only when I initiate a backup vs continuously....my mac is now waking from sleep as expected (at least overnight, last night). Should note that backblaze is not functioning correctly in Ventura and this is a known issue. I'm not sure if my issue was "solved" with safe mode...or by disabling backblaze...
 
  • Like
Reactions: fisherking
Unless you are running a laptop, like to close the lid to sleep, and really need deep sleep to maintain battery life while moving around, consider turning off hibernation mode altogether.

My OCLP Ventura install on a Mid 2012 MacBook Pro wasn't waking up, so I set hibernation mode to 0. I've seen the same behaviour through multiple installs of patcher installations in the past, but it is not just an issue with patched systems. I've seen the same problem with different installs over various previous versions of Mac OS on my 2012 Mac Mini and 2008 MacBook Pro's.

In Terminal check your current hibernation setting with pmset -g and use man pmset to read over all the settings you can change.

Give the time to boot with M1 systems and SSD system drives, I submit that hibernation mode is not very useful today.

Just my opinion.
 
I just signed up to macrumors to chime in. I recently installed Ventura via OpenCore Patcher on my iMac 17,1. The first few days everything went smoothly, only yesterday, after installing a couple of tools I always install (i. e. LittleSnitch and a few audio production related software) the Mac won't return from a longer sleep period. Resetting NVRAM and SMC didn't help. Hibernation is on "0" according to pmset -g which means "off", right?
 
Same issue here (tried solving solo but unsuccessful) for a 2017 iMac. Now pulling the power cable each morning to re-start (the power button won't do anything), which is frustrating of course. Watching this discussion now.
 
I have a similar issue on my MacBook Pro 13" 2017 with Ventura. It won't wake up from suspend sometimes and I have to reboot. Seems to occur when uptime is near about a month.
 
I have the same issue on my M1 Max Macbook Pro. I did some testing in order to find the source of the issue. Disabled the Hibernation, restarted the system every time (but re-opened all the apps) before putting into sleep, tried closing all apps before closing the lid and more.

And in my case, I found out that quitting Figma Desktop App before putting my Macbook to sleep completely fixes the problem.

I use Figma Desktop App and usually have 4 to 5 really big projects opened at the same time. This issue probably has nothing to do with Figma itself but there is definitely something that causing it. I haven't done any specific testing and I don't really have a lot of knowledge about the internals of the OS itself but I have two ideas;

1. High memory usage. I use the 64GB version and have lots of IDEs, Figma projects and Chrome windows opened across couple workspaces at all times. It's hard to fill all that memory space but it happens throughout the day. If I quit Figma, after an all day use, it frees up 15 to 20GB of memory which maybe preventing the issue from happening. I suspect if I put my computer to sleep while having a high memory usage, something crashes and I get the issue.

2. Background activity. Since Figma stores all files in cloud and has collaboration features, I suspect maybe the background activity crashes something while the computer sleeps. Again, I have very limited knowledge on the OS internals so I'm not even sure if a background activity can cause something to crash this badly but you never know.
 
For me, unable to wake began after the update to macOS 13.1 — although, it seems as if it’s getting worse.

• Typically shut down my Mac for overnight hours.
• I do have an external (USB 3.1) HDD for Time Machine.
• No Backblaze

At first, I thought, maybe a BT issue, so I connected my Magic Keyboard via USB. The Mac still refused to show video. I can recall once also unplugging and replugging the monitor (HDMI).

The Mac seems like it’s still doing things (i.e., not frozen) but no video.

For now, I guess, I’ll shut it down every instance that may have it asleep for more than an hour. ¯\_(ツ)_/¯ I’m not going to continue improper shutdowns and risk corruptions/drive failures.

srcn88 said:
2. Background activity. Since Figma stores all files in cloud and has collaboration features, I suspect maybe the background activity crashes something while the computer sleeps. Again, I have very limited knowledge on the OS internals so I'm not even sure if a background activity can cause something to crash this badly but you never know.
Click to expand...
I had a similar thought, but I don’t leave a lot running:

• Messages
• Mail

Often my HDD is connected thus TM does its hourly thing. Of course, whatever routine iCloud syncs Apple apps (e.g., Calendar) do.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back