Macbook Pro 16inch & CalDigit TS3 Plus Dock cSleep Crash

@proam500 I've been able to reproduce crashes without the dock too. I'm not saying the dock isn't playing a part, but I'd certainly say that you should check what software you're running too. Mine is now crashing about once a week, whereas before it was crashing everytime it slept. I _think_ that this may have improved after I manually removed some services that the Karabiner uninstall software does not remove.

Did you do the NVRAM clear and SMC reset after upgrading the dock firmware too?

I'm with you though, I'm very dissapointed. My 2012 MacBook Pro that is still going strong never does anything like this.

I haven’t had a crash since I set my monitor to never sleep. I have friends with other docks same problem. Apple should fix this if they only give us usbc to work with.

I just get the dock from apple store and arrived 2 days ago. I have been experiencing the same problem , I contacted CALDIGIT and they are aware of the problem but no solution so far, they recommend resting NVRAM and SMC . I did both and still the same. Then I contacted Apple technical support, to my surprise, their were not helpful at all claiming that they are not responsible of 3rd party devices sold in apple store !! they recommended reinstalling the macOS 10.15.4 , and I did ..still the same problem. I started isolating the problem by disconnecting devices, starting by my LaCie 8TB USB3 backup time machine, I thought it worked and that was the case for almost a day and then it crashed in the middle of the day. I tried every possible Energey saving setting , from don't put hard desk to sleep to unchecked automatic graphic .. nothing worked. I am already request a return and send back tomorrow for refund. As you mentioned good reviews that made to buy this dock ...was hoping it would work..but it is not. Let me know if you solved the problem.

I have the same problem. It only crashes if the external monitor is plugged in to the CalDigit's Display Port. I just bought a Thunderbolt to HDMI cable. It arrives in 2 days. Maybe that will fix the problem: connecting the monitor directly to the Mac and using the Caldigit for everything else.

I have this same problem to mbp 16 + caldigit ts3 plus dock. It is definite kernel panic with what appears to be the osx usb driver listed in the stack trace. Definite software issue in osx that apple should fix, especially if they sell this dock through their store claiming it is compatible.

I have reinstalled osx - no luck. nvram + smc reset works for a week maybe then it starts again.

I have been experimenting with different configurations. Between testing each configuration, I clear nvram and reset SMC (and of course reboot). I have found that my Mac will crash regardless of whether the external monitor is connected via the TS3 OR directly to its own USBC port on the Mac. Therefore, it might suggest that this is to do with external monitors full stop, rather than the TS3 itself. All of these crashes happen when I return to the Mac and at least the monitor is in sleep.

What monitors are people using? I have the ASUS VG27AQ.

With the monitor directly connected to the Mac AND the TS3 connected, I got this:

panic(cpu 0 caller 0xffffff800189167c): Sleep transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x5f41.
Backtracing specified thread

With the monitor directly connected and NO TS3, I got this:

panic(cpu 8 caller 0xffffff7f98ba1ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (7170 seconds ago): 718, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since load (7140 seconds ago): 702, last successful checkin: 120 seconds ago

I have a case open with Apple and will be reporting this back to them too.

I have also experienced the issue.

If you remember to disconnect the TS3 before stepping away for the night, everything is good in the morning. However, if you leave the dock connected, it's about 75/25% that it will have kernel panic'd overnight.

I initially thought it was a storage issue as one of my USB-C SSDs was connected via the dock, but even with that directly connected to another USB-C port on the MBP, the issue still happens.

I was having these problems when connected to doc and screen went to sleep. So far I'm 3 weeks without a crash and all I did was just not let the screen sleep :) just turns on screen saver. It's not a great solution but it's better than a kernel panic.

From the Apple Store web site, emboldening is mine:

Note: Products sold through this website that do not bear the Apple brand name are serviced and supported exclusively by their manufacturers in accordance with terms and conditions packaged with the products. Apple’s Limited Warranty does not apply to products that are not Apple branded, even if packaged or sold with Apple products. Please contact the manufacturer directly for technical support and customer service.

https://www.apple.com/shop/product/HMX12ZM/A/caldigit-ts3-plus-dock

That having been said, kernel panics should never occur, so Apple should address that issue in macOS X.

Can you post the text of one of the panic logs?

This exactly what I did " resting NVRAM and SMC" ... and It worked for few hours and then crashed again. I decided today morning to send it back and I did. Hopefully it would work for you. let me know.

That one is a known software issue; hopefully Apple will have it fixed soon, but I certainly understand if you are not willing to wait.

Note it also isn’t universal; for some reason my MBP 16 does not experience this issue.

Out of interest, are any of you using any of the following software?

• Karabiner (even if you installed and then uninstalled).
• Citrix Workspace
• Harverst Timer App

I have the most recent firmware for the TS3. And my OS is updated. I’m going to try to disconnect my peripherals like suggested above.

Well known among senior contributors here and at least some people at Apple.

I have no insight as to a root cause or when a fix may be coming, and as always it never, ever hurts to raise the issue with Apple Support yourself:

Official Apple Support