Catalina constantly crashing when Sleep

Update on my end. I really believe this may be related to cheap docks/hubs people are using. When I first posted I noted that the kernel panics and sleep issue I was having would only occur if I was using the USB-3 hub/adaptor I purchased from amazon called VAVA. The apple thunderbolt to hdmi adaptor did not cause any sort of issue.

So I picked up a hp thunderbolt dock g2 and two USB-3 monitors. Since I started docking the system this way, I have not had the issue since. And I'm down to only one cable for power and peripherals. The only issue I have is with the dock. HP doesn't publish mac drivers for the onboard audio output and ethernet. Thats not a mac issue though, and is a known deficiency with the product. May be swapping this out for a different dock.

Not that this is a solution. It definitely wasn't cheap.

Start a case with Apple Support and keep after it. Let them collect data (eventually) and they may discover a defect on the logic board. This was my circumstance. Physical repair or replacement may be necessary.

I'm having the same problem when my 16" Macbook goes to sleep.

Configuration

2,3 GHz 8-Core Intel Core i9​

64 GB 2667 MHz DDR4​

AMD Radeon Pro 5500M 4 GB​

Intel UHD Graphics 630 1536 MB​

external LG 34UM94 Monitor​

external Keyboard​

external Mouse​

USBC->HDMI Adaptor for the monitor. USBC->HDMI Adaptor​

After updating to 10.15.5 (19F101) each time I want to wake it up it was crashed with kernel panic.

It seems as if I could solve it: 

I removed the Monitor from the HDMI-Adaptor and plugged it to an USBC to Thunderbolt adaptor from Apple.

Now the LG is connected to Thunderbolt not HDMI, with a nice side effect: I can adjust the volume from the Keyboard now.

Maybe this helps someone.

P.S.

Disabling PowerNap, HDD Sleep did not make any difference on my system.

Anyway: It is a shame that Apple makes no effort to fix this! This high price machines MUST work perfectly!

another UPDATE

In case it's useful for anyone finding this thread.

I had updated to 10.15.4 and experienced endless crashing, updated to 10.15.5 and nothing changed.

I then backed everything up and and formatted my Macbook 16" and installed 10.15.3 and have had zero issues.

Note I didn't use time machine to restore or migration manager. I manually copied over my documents and photos etc and reinstalled everything from fresh downloads. Everything is working great.

I just bought a new 2tb SSD to clone my Macbook and figured, with this clone backup, I'll try updating to 10.15.6. I instantly had issues again. One crash, and upon leaving it for a while returned to open it up and have a red screen! Restarted it, similar issues.

I've restored it using the cloned 10.15.3 and no issues again.

I have no idea what it is. It's really disappointing, especially because I can't access my Photos library for the time being because it's from a newer version of Photos.

Remove Paragon, it fix my crashes

After some experiments, I think I have narrowed down the cause of my nightly crashes. I have two NASes (network attached storage). I made sure to disconnect them before I go to sleep. The crashes seem to not be happening.

So until Apple fixes this problem, you can try to disconnect external/network drives before you go to sleep. Leaving them connected during the daytime doesn't cause crashes for me.

Good luck.

FWIW — I updated to the latest version of Catalina, downloaded the newest OWC RAID software and installed it, and turned on the "Prevent computer from sleeping automatically when the display is off" checkbox in the Energy Saver preferences. My OWC Thunderdrive is back up and running (and backing up), and my computer is o longer crashing when it sleeps. I don't exactly which of these three actions helped the most, but I'm happy that I'm not crashing every 15 minutes now. I'll probably try unticking that checkbox and see if the problem returns, but for now I'm good.

I had a similar issue. Waking the computer up in the morning I would be greeted with a "Slack has crash" dialog. From there things just wouldn't work, couldn't open up other apps ext until I quit something else. Things looked fine but a full restart was needed to get fully working.

Updating to 10.15.2 and updating everything else didn't do anything either.

The last time I decided to check the Activity Monitor before restarting and noticed a bunch of "cron" processes running. I at one point also had terminal say something like "Too many processes running".

I ran down the culprit of a custom cron I setup to check the mouse battery level every so often. The cron never worked but I guess it was still running and with Catalina not liking "cron" processes anymore they will filling up and not clearing properly. Eventually this would not allow other things to open ext.

This might not be the same issue but check the Activity Monitor after waking your computer and if there is a ton of "cron" processes running this could be the issue. Track down whatever is creating these cron jobs and fix or remove it.

Final update.

New iMac 2019

10.15.2 update has sorted my problem. Sleep now works fine and the system still seems stable after a couple of weeks.

This fix came only after my many phone calls to Apple’s help line giving them the info they needed to develop the fix.

I recommend that anyone with this problem takes the time to call Apple and slog through it with them as in my case that worked.

Been having this kernel panic about 3-4 times a day, which has seriously killed productivity. I think I came up with a temporary fix, potentially. It's only been 24 hours, but disabling Powernap on battery power + AC power seemed to have stopped the crashing. I figured this might be the case because I noticed that I was only getting the panics while connected to AC, and Powernap was only turned on when connected to AC.

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.

Update 7: Apple Engineering has informed me, via Apple Support Sr. Technical Advisor, that they have concluded there is a COMPONENT FAILURE on THE LOGIC BOARD of my 2019 MacBook Pro 16 inch. (!!)

Apple pulled data on two occasions to make their determination. They did not tell me which component they identified as having failed.

They sent me a return shipping box after we discussed and rejected the option of a possible in-store repair. Since my MBP 16" was special order (max configuration with 4T storage), we concluded that the store would not be able to fix it and would need to ship it to Apple Repair specialists anyway.

So this concludes my story – for now. I expect my problem is not shared with too many others here on this thread, but I hope it proves helpful to someone at some point.

If the anticipated repair does not remove the crashing-while-sleeping problem for me I will return and update this thread.

Good luck to all. ~k

I disabled "deep sleep" and this fixed my problem.

https://apple.stackexchange.com/questions/300823/compatibility-of-nvme-and-deep-sleep-in-macbook-pro

I was using the exact same hardware (hard drive, etc.) in Mojave without issue.

I am not using any external drives or docks.

One user suggested that using low-end attached devices may be a cause. The low-end/high-end issue doesn't seem to apply to my 2018 15" MBP (Catalina 10.15.3). I have two Lacie 2B Docks (20TB/16TB) daisy chained via Thunderbolt 3 with an attached (to the last Lacie) 2TB SSD for Time Machine via Thunderbolt 3. All of them use one Thunderbolt 3 port on the MBP. I also have a 32" 4K Acer monitor via Thunderbolt 3, and a Yubikey always attached via TB3. I've isolated the attached drives to be a reason since when they are not attached, I don't have this issue.

A suboptimal work around that has worked for the last two days is to check the box in Energy Saver settings, "Prevent computer from sleeping automatically when the display is off." The following two boxes are also checked: "Wake for Wi-Fi network access", and "Enable Power Nap while plugged..." (which should be moot given the first check box). "Put hard disks to sleep when possible" is not checked. "Automatic graphics switching" is checked.

Before changing to these settings it would self restart when asleep 100% of the time when the drives were attached. I'll cross my fingers and experiment with other settings to further isolate issues.

I hope a fix comes at some point, although I am not sure the real root issue so far, but this problem surfaced when I upgraded to Catalina.

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!