Catalina constantly crashing when Sleep

I am having roughly the same issue here.

MacBook Pro (15-inch, 2018)

macOS Catalina 10.15.2

Radeon Pro 560X 4 GB

Intel UHD Graphics 630 1536 MB

I am connecting my mac to an external monitor via a usb-c adapter and HDMI (various combinations seem to change the behavior):

1. Vava USB-C hub: https://www.amazon.com/gp/product/B079GSMZ7G/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
2. Stouchi: https://www.amazon.com/gp/product/B075S4LQ76/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

I am doing PD directly from the apple power cord.

I am looking at getting a hub like the caltech TS3 Plus as that will do PD. But I'm worried that wont solve the issue here. I have two different behaviors.

1. If I keep my laptop connected to once hub and power, eventually the machine will sleep and crash. I have sent numerous reports to apple on this
2. Once in a while, if I am working else where and then try to come back to my desk and plug in the hub and power, I get a kernel panic and an instant reboot a few seconds after I plug in the hub.

Looking at the CalTech, it seems like this is related to hardware as they recently pushed a firmware update that is supposed to solve the sleep issue.

Any advice here?

EVERYONE, PLEASE TRY THIS AND REPORT YOUR RESULTS:

Using this method I was able to cause my laptop to kernel panic with this error within 30 seconds of playing the video. I repeated the process 6 times just to be sure, and each time my computer kernel paniced with this error within 30 seconds every time.

1. (If you have a laptop) Open System Preferences, then go to Energy Saver, then deselect "Automatic Graphics Switching" at the top. This will make it so that your dedicated GPU is always in use.
2. Go to this link and download the 4K video: https://www.videezy.com/urban/2820-aerial-footage-of-new-york-city-4k
3. Open the video in Quicktime.
4. In the menu bar, click "View" and then "Loop" so the video plays repeatedly.
5. Play the video and wait.

This was the same problem here from November to early February with my 16" MBP.

Some items that may have fixed it - since I no longer have this issue:

• Updated firmware on my OWC Thunderbay 43 to current version;
• Upgraded to 10.15.4;
• Replaced USB-Type C hub;
• Have both external monitors using USB-C (one monitor uses USB-C to USB-C, and the other uses a USB-C to HDMI cable)

It's been several months of trouble-free computing, but it was really irritating while the wake from sleep crashes were going on. My sense is that these all work together, but the one peripheral that might have been the culprit was the "Totu" USB-Type C hub. I say that because I had to replace it when it stopped communicating with another peripheral via USB 3. However, the wake from sleep crashes had already ceased to be a problem before the hub failed. Nevertheless, if there was some degradation of signal over time, that hub could've easily been the culprit from the start even though I tested the system with and without it back in December, and the problem remained before and after removal.

Hope others can get their problem solved, I'm glad it's gone here! (at least 2 months now) Hopefully it's gone for good.

Good luck!

I've had this problem since the 10.15.4 update (back in Feb?). I thought for half a day that the 10.15.5 update fixed it but no.

It could crash waking from sleep, and often using Photoshop 2020 and Illustrator 2020. The recent Adobe updates didn't help either.

This week I cloned my hard drive, spent hours finding a installer for 10.15.3, made a usb installer, wiped my machine and I was finally able to go back to 10.15.3 and move my files over.

Everything has been fine since.

Configuration

• MacBook Pro 16" 2019
• 2.6ghz i7
• 32gb ram
• 2tb SSD
• AMD Radeon Pro 5500M 8 GB - Intel UHD Graphics 630 1536 MB
• LG 34UM95 Monitor
• Belkin Thunderbolt 3 Express Dock HD
• Apple thunderbolt cable and Thunderbolt 3 adapter
• Apple Magic Keyboard 2 and Trackpad
• Wacom intuos tablet

I've lost loads of time and it's been a real pain in the behind, but I'm feeling hopeful now.

Same issue with a 2019 16" MacBook Pro. The laptop will immediate have a blank display (keyboard lights stay on) when I try to go to sleep AND have my Dell P2720DC external monitor plugged in. Laptop goes to sleep fine if the monitor is not plugged in.

Tried the following and no luck:

1. Reset SMC
2. Tried connecting USB-C on monitor to Thunderbolt: Does not work.
3. Tried connecting HDMI to USB-C hub --> Thunderbolt: Does not work.
4. Tried connecting HDMI to HDMI-->USB-C adapter --> Thunderbolt: Does not work.

I am on Catalina 10.15.5

I have a brand new imac 27” with ssd and Catalina. Finder just stops responding after each sleep and spinning ball appears. I have tried all of the above several times and removed peripherals and start up programmes like Dashlane and it still happens. Driving me nuts £2k down with a c..p Apple update. Old mac mini with Mojave and ext ssd much better.

My late 2017 21” Mac is doing the same thing. I put it to sleep, and every time I return after an hour or so it has done an Emergency Reboot and wants to send an Error Report. I believe it may have something to do with detection of/external storage as sometimes on reboot it doesn’t detect all my external storage on Lightning 3 connections.

Just to add another data point to this. I also experience nightly crashes on my 2017 27" iMac with Catalina (10.15.1).

I have sent a lot of crash logs to Apple. Hopefully it gets fixed in the coming OS update.

I just updated my late 2015 iMac to Catalina and now I'm facing this irritating problem; sometimes it freezes when I work on it and I can never wake it from sleep without having to emergency reboot it. COME ON Apple, this can't be true! You have to give us a solution now! Bad, bad work by the developers. I'm seriously considering a Windows computer as I feel like Apple are being more and more sloppy......

Note; Nothing was wrong before updating. Another irritating issue was that I couldn't use iPhoto anymore, I hate the layout and the way it's presented in Photo...

OK, This is absolutely crazy. We just as well start calling this CRASHALINA. Apple has released an OS update on the public that is bricking thousands of 2016 and older systems, and causing untold problems on newer Apple systems (like my iMac 18.2 2017 21" system). I tried the route of reseting my SMC. Needless to say that was a bust. Here's what I'm getting on the error report when I wake it up (after the emergency reboot):

panic(cpu 0 caller 0xffffff7f8b416238): "IOAHCIBlockStorageDriver::CommandTimeout! reallocated sectors = 0x0, pending sectors = 0x0, power on hours = 0x455, fBuiltIn = 0, LBA = 0x0, Block Count = 0x0, Tag = 0x14, Operation Type = 0x6 fis[0]=0x10EF8027, fis[1]=0x0, fis[2]=0x0, fis[3]=0x2, fis[4]=0x0"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOAHCIBlockStorage/IOAHCIBlockStorage-316.40.3/IOAHCIBlockStorageDriver.cpp:6311

Backtrace (CPU 0), Frame : Return Address

0xffffff920bfbba70 : 0xffffff8007f39a3b

0xffffff920bfbbac0 : 0xffffff8008070fe5

0xffffff920bfbbb00 : 0xffffff8008062a5e

0xffffff920bfbbb50 : 0xffffff8007ee0a40

0xffffff920bfbbb70 : 0xffffff8007f39127

0xffffff920bfbbc70 : 0xffffff8007f3950b

0xffffff920bfbbcc0 : 0xffffff80086d17f9

0xffffff920bfbbd30 : 0xffffff7f8b416238

0xffffff920bfbbde0 : 0xffffff7f8b40d213

0xffffff920bfbbe20 : 0xffffff8008644f79

0xffffff920bfbbe90 : 0xffffff8008644e99

0xffffff920bfbbec0 : 0xffffff8007f7b625

0xffffff920bfbbf40 : 0xffffff8007f7b151

0xffffff920bfbbfa0 : 0xffffff8007ee013e

Kernel Extensions in backtrace:

com.apple.iokit.IOAHCIBlockStorage(316.40.3)[D16B857E-1AFB-3E06-A190-6F0944BB81AF]@0xffffff7f8b405000->0xffffff7f8b42cfff

dependency: com.apple.iokit.IOAHCIFamily(290.0.1)[0456322C-3677-3442-8F74-3171483F3886]@0xffffff7f8b3da000

dependency: com.apple.driver.AppleEFINVRAM(2.1)[A86937B2-6177-3699-BE65-6762DDC120C6]@0xffffff7f89870000

dependency: com.apple.iokit.IOStorageFamily(2.1)[A9967DFD-FCB3-3536-B071-F8B46494895B]@0xffffff7f8931f000

It goes without saying, Catalina is a disaster - the only question now - Is Apple going to own up to it, fix or replace the equipment they break, and FIX CATALINA!!

I have this same issue on my Mid 2015 iMac 5k. It happened after I updated to Catalina. I sent crash logs... and have since downgraded back to Mojave and I am not experiencing the sleep/wake crashes anymore.

I'm experiencing the exact same thing on my iMac Pro 2017. This is really ridiculous and infuriating. I swear, every since Steve Jobs passed the quality of Apple products has been in steady decline. I've been using Macs since 1988, and I can't ever remember a time when I regretted an update and really wished I could revert.

I would like to report a similar issue. I am on imac late 2015. I just noticed it when I had upgraded to Catalina(i had some other issues so i thought it could be something else) . I called Apple and worked with a senior advisor who helped me run a bunch of tests and we noticed that the problem only happened when I have my OWC hard drive docking station attached via thunderbolt. In the docking station I have a couple of SSD's. He said they were drawing to much power and causing the crash. That did make sense to me. I have never had this happen with them(although I did start using a large SSD recently) I think it should worked based on the specs of the stations. My next step was to call OWC and find out if they had reports of a similar problem. It appears there's an underlying OS problem if everyone else is having the same problem since Catalina. I never had this problem before that I recall so it appears it is yes perhaps only triggered in this way but clearly something is happening with Catalina.

Ok, I have both an OWC 4-drive external Thunderbolt 2 and a 2-drive Thunderbolt 2 enclosure. Both are full with 2 Tb 7200 rpm hard drives. I have never had a problem with them until I installed Catalina. But my big question is - how can they be drawing to much power when they both have their own power chords with in-line bricks? They are not drawing any power from the system, just data.

YES! This is a wonderful question you ask. It makes no sense this is why I looked it up today. Something is not quite right. I'm going to call tomorrow and see what they have to say. I will report back!