Kernel panic crash with 2 external LG displays - Monterey 12.0.1 MacBook Pro (16-inch, 2019)

After installing Monterey 12.0.1, my MacBook Pro crashes if I have the laptop retina display open and both LG monitors connected. Worked fine on Big Sur, no other changes.

I can run the retina and one LG display, or run both LG displays with the laptop lid closed, but it kernel panics after about 60 seconds if all three displays are on.

  • MacBook Pro (16-inch, 2019)
  • 2.3 GHz 8-Core Intel Core i9
  • 32 GB 2667 MHz DDR4
  • AMD Radeon Pro 5500M 4 GB
  • 1 TB SSD (APPLE SSD AP1024N)

Monitors:

  • LG 27UD68-P
  • Each connected through a separate USB-C hub via HDMI
  • Both plugged in on the right-hand side of the MacBook

I also have this issue. Kernel maxes out often when using my 1 wide curved external monitor and I have Zoom on or a video playing on either screen. Quick fix is to unplug the external monitor, but that's no fun.

Same tired insanely annoying and monotonous problem with Radeon RX550 16" 2019 on 2 x Samsung LU28R55

Does anyone at apple actually listen and fix these problems? It's 2022, and Apple STILL to this DAY, cannot properly handle dual screen monitors while docked. Monterrey shouldn't ship if there were issues with dual screen monitors. Stop using your customer base as free QA. This has costs to our productivity.

Apple. For the love of anything you find dear. The amount of pain that people are forced to go through on account of your poor window management is beyond disruptive to work. It goes out during meetings, and suddenly BOOM kernel panic. It goes out during pair programming. Boom Kernel panic. We send the updates to you "TeeHee we had a problem". It goes on for months and months and months and months and never sees resolution. If you are dropping KernelPanic on basic usability, what are you doing besides creating ANGRY people, who will eventually take their money back to another platform?

panic(cpu 0 caller 0xffffff800ecd41a8): Wake transition timed out after 180 seconds while calling power state change callbacks. Panicked task 0xffffff99ef4d5670: 6275 threads: pid 0: kernel_task Backtrace (CPU 0), panicked thread: 0xffffff9049b32aa0, Frame : Return Address

Go find an AMD rep. Work with them to solve this ridiculous problem.

Investigate and fix this. What planet do you have to live on to get BASIC dual monitors to work properly? Linux handles this more elegantly than MacOS.

I have the exact same issue and it's beyond frustrating.

I had been using one external monitor (27" Dell P2720D) with the Macbook in clamshell configuration for almost 2 years, without a single issue with performance or any kind of crashing. I recently updated to macOS Monterey 12.2.1 and added a second monitor at the same time (BenQ GW2280). I wish I never made the decision to update to Monterey as I now cannot connect my external monitors with the Macbook without it going into a complete meltdown after a couple of minutes of use, resulting in a force restart.

The only workaround I have managed to find is that it works perfectly if the Macbook lid is open. Meaning I now have 3 displays instead of 2. I really can't get my head around how the Macbook crashes running just 2 displays but can handle 3 without an issue!

This problem has to be resolved as I suspect lots of users are having the same issue and just resorting to using 1 monitor thinking it's their Macbooks performance, not a software glitch. I also suspect some users aren't having this issue and it's going unreported as they have their Macbook lids open and their performance hasn't taken a hit.

Apple, please, please, please fix this issue it's driving me insane!

Macbook specs:

  • MacBook Pro (16-inch, 2019)
  • 2.3 GHz 8-Core Intel Core i9
  • 16 GB 2667 MHz DDR4
  • AMD Radeon Pro 5500M 4 GB Intel UHD Graphics 630 1536 MB

Same problem. MacBook Pro, 13-inch, 2020, 2.3 GHz Quad-Core Intel Core i7. Really frustrating.

Same here, different monitors though! I did reset SMC, reset the computer PR... no difference. So annoying to spend 4k on laptop that can not handle simple two monitor config...

I am having the same issue with my Mac Studio Ultra. My current setup is 2 x LG 27UL850-W 4K monitors and 1 x Wacom Cintiq Pro 24. I have had two LG monitors plugged into OWC Thunderbolt 4 Hub, and Cintiq Pro connected directly to the Studio. To isolate the issue, I plugged in one of the LG monitors directly to the Studio and disconnected everything, and I was still having the problem. 2nd day I connected the Wacom monitor, and I did not have the same issue.

Everybody still has this same problem for so long now ! I paid US$6500 for this POS that cannot work with external monitors.

My MBP crashes when connected to the external monitor too. It started with a macOS update and has been happening for a long time now. There were multiple macOS updates since this issue first appeared, but this wasn't fixed yet. This is the crappiest computer I've ever touched in my life.

  • MacBook Pro (15-inch, 2016)

  • Processor 2.9 ghz Quad-Core Intel Core i7

  • Memory 16Gb 2133. MHz LPDDR3

  • Graphics Radeon Pro 460 4GB

  • macOS Monterey version 12.4

2 x LG UltraFine Displays 5K 27” (5120 x 2880)

I’m having to shut my laptop lid to stop my machine locking up / shutting down and it seems to be playing up quite a bit for the last week. I was previously having issues with cirrus and the MAC being Busy doing nothing for ages then after a wait for a few mins if I was lucky it went back to being responsive.

  • MacBook Pro 15-inch, 2018

  • CPU 2,9GHz 6core Intel Core i9

  • RAM 32GB 2400MHz DDR4

  • GPU Radeon Pro Vega 20 4 GB + Intel UHD Graphics 630 1536 MB

  • macOS Monterey 12.4

Crashing as described. Fore sure it will crash during MS teams window sharing od google meet.


panic(cpu 6 caller 0xffffff800956799f): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds
service: logd, total successful checkins since wake (17350 seconds ago): 1736, last successful checkin: 0 seconds ago
service: WindowServer, total successful checkins since wake (17350 seconds ago): 1724, last successful checkin: 120 seconds ago
service: remoted, total successful checkins since wake (17350 seconds ago): 1736, last successful checkin: 0 seconds ago
service: opendirectoryd, total successful checkins since wake (17350 seconds ago): 1736, last successful checkin: 0 seconds ago

Panicked task 0xffffff9ac4ea0d40: 3 threads: pid 113: watchdogd
Backtrace (CPU 6), panicked thread: 0xffffff912d0e9000, Frame : Return Address
0xffffffcb2ba4b690 : 0xffffff8006081c8d 
0xffffffcb2ba4b6e0 : 0xffffff80061e1596 
0xffffffcb2ba4b720 : 0xffffff80061d0963 
0xffffffcb2ba4b770 : 0xffffff8006021a70 
0xffffffcb2ba4b790 : 0xffffff800608205d 
0xffffffcb2ba4b8b0 : 0xffffff8006081816 
0xffffffcb2ba4b910 : 0xffffff8006915223 
0xffffffcb2ba4ba00 : 0xffffff800956799f 
0xffffffcb2ba4ba10 : 0xffffff80095675f2 
0xffffffcb2ba4ba30 : 0xffffff8009566971 
0xffffffcb2ba4bb60 : 0xffffff8006883a8c 
0xffffffcb2ba4bcc0 : 0xffffff80061872e6 
0xffffffcb2ba4bdd0 : 0xffffff800605c9ab 
0xffffffcb2ba4be60 : 0xffffff80060731f9 
0xffffffcb2ba4bef0 : 0xffffff80061b35aa 
0xffffffcb2ba4bfa0 : 0xffffff8006022256 
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[D6F8B92D-3418-34BA-B42B-F553E0C44C29]@0xffffff8009565000->0xffffff8009567fff

Process name corresponding to current thread (0xffffff912d0e9000): watchdogd
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21F79

Kernel version:
Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:22 PDT 2022; root:xnu-8020.121.3~4/RELEASE_X86_64
Kernel UUID: 3C587984-4004-3C76-8ADF-997822977184

...

I installed the macOS Monterey update today (12.5 - 21G72). And my MBP still crashes when connected to my BenQ EW3270U.

I use the same monitor with another laptop running Windows 7 and one another laptop running Linux. Both runs perfectly, although the MBP seems to get kernel panics very often. Its funny an years old OS and a free OS can do things while an overpriced one is constantly struggling to do the same.

Same issues as everyone else with a max spec 16-inch 2019 MBP running 12.4. Everything worked great before upgrading to Monterey. I have two Dell monitors connected with usb-c -> displayport cables, but when I plug in a 3rd screen via usb-c -> HDMI, the screen often freezes and then reboots after 120s. I have tried all different combinations of monitors plugged in directly to the macbook and two different docks. I was able to stop it instantly freezing when plugging in the 3rd screen by changing the Macbook's display refresh rate from 60hz to 59hz, even though I'm using the macbook with the lid closed, but I still get freezes when doing things like moving a window from one monitor to the 3rd screen.

How do we actually get Apple's attention on this?

Same exact issue here. Can't believe they have not resolved yet. Unacceptable.

on similar reason maybe. I had kernel panic when I used to connect my 5k lg display with mac m1 air. then after getting fraustated for quite long I did NVRAM reset. that fixed the issue.

SAME HERE. iMac 2019, using Monterey 12.5.1 now...and crashes. Two 4K monitors plugged in. (LG HDR 4K and a BenQ LCD both at 60 Hertz Refresh) YES, I have done NVRAM reset. Still happens. If I leave my Mac for a while, I come back to it having restarted cause of a crash. When I use it, mainly InDesign, my mouse will move but not to the other monitors, and the programs will freeze up, a minute later the mouse will freeze and I have to hard reboot. I crashed about 8 or 9 times today now. Its cramping my magazine deadlines! Is this what yours is doing?

I had this issue with my 2017 iMac Pro when I upgraded to Big Sur. I have two external monitors (Dell and LG). After upgrading, my computer would crash overnight. It seems like the computer has to be idle and/or sleeping for the problem to arise. It was almost daily crashes with a kernel panic. Eventually, the problem just... went away.

Friday, I upgraded to Monterey and guess what? I'm back to daily crashes overnight. Sometimes it reboots itself, but this morning it was powered off and I had to manually turn it back on.

I asked about this two years ago when it first happened and got zero response, so I don't expect anything now, but it's (still) completely unacceptable, especially after years of reports.

I have the same issue. I receive a new mac pro 2019 (i9, 32gb, radeon 5500M) and as soon as I connect an external monitor the mac freezees completely and reboot after a few minutes. Cannot work like this. The report first page I get is below. This issue is not present in my mac pro 2018 (i7,32g, radeon 555)

Process: WindowServer [-1] Path: ??? Identifier: WindowServer Version: ??? Code Type: 00000000 (Native) Parent Process: ??? [Unknown] User ID:

Date/Time: 2022-08-29 13:56:01.9179 -0300 OS Version: macOS 12.5.1 (21G83) Report Version: 12 Anonymous UUID: 3DD382A7-F75E-0EA9-EF93-4C3BEC62685C

System Integrity Protection:

Notes: This is a watchdog-triggered termination event, and not expected to be well-represented in the legacy crash format

Crashed Thread: Unknown

Exception Type:

Termination Reason: Namespace WATCHDOG, Code 1 monitoring timed out for service (1 monitored services unresponsive): checkin with service: WindowServer failed to send ping message, WindowServer watchdog request handling code likely hung 80 seconds since last successful checkin, 657 total successsful checkins since load, 39 seconds since last crashed by watchdogd, (1 induced crashes)

Error Formulating Crash Report: This is a watchdog-triggered termination event, and not expected to be well-represented in the legacy crash format

Backtrace not available

No thread state (register information) available

Binary Images: Binary images description not available


Full Report

{"bundleID":"WindowServer","timestamp":"2022-08-29 13:56:01.00 -0300","os_version":"macOS 12.5.1 (21G83)","incident_id":"022F09A4-2686-451C-BCA9-4484CD9F2580","share_with_app_devs":0,"bug_type":"309","app_name":"WindowServer","name":"WindowServer"} { "deployVersion" : 210, "variant" : "stackshot", "incident" : "022F09A4-2686-451C-BCA9-4484CD9F2580", "crashReporterKey" : "3DD382A7-F75E-0EA9-EF93-4C3BEC62685C", "modelCode" : "MacBookPro16,1", "cpuType" : "00000000", "osVersion" : { "train" : "macOS 12.5.1", "build" : "21G83", "releaseType" : "User" }, "variantVersion" : 2, "captureTime" : "2022-08-29 13:56:01.9179 -0300", "pid" : -1, "procName" : "WindowServer", "bundleInfo" : {"CFBundleIdentifier":"WindowServer"}, "termination" : {"flags":0,"indicator":"monitoring timed out for service","code":1,"namespace":"WATCHDOG","details":["(1 monitored services unresponsive): checkin with service: WindowServer failed to send ping message, WindowServer watchdog request handling code likely hung 80 seconds since last successful checkin, 657 total successsful checkins since load, 39 seconds since last crashed by watchdogd, (1 induced crashes)"]}, "stackshot" : { "processByPid" : { "0" : {"timesThrottled":0,"turnstileInfo":["thread 109: blocked on 2298, hops: 1, priority: 92","thread 2297: blocked on 86015, hops: 1, priority: 92","thread 2298: blocked on 2297, hops: 1, priority: 92","thread 86962: blocked on 2298, hops: 1, priority: 92"],"pageIns":246,"waitInfo":["thread 109: kernel mutex 0xbe616c96f1e9f711 owned by thread 2298","thread 2297: kernel mutex 0xbe616ca087bf3821 owned by thread 86015","thread 2298: kernel mutex 0xbe616ca087bf0681 owned by thread 2297","thread 86962: kernel mutex 0xbe616c96f1e9f711 owned by thread 2298"],"timesDidThrottle":0,"procname":"kernel_task","copyOnWriteFaults":8244,"threadById":{"112":{"continuation":[0,1338336],"userTime":0,"systemTime":1.468e-06,"id":112,"basePriority":31,"name":"VM_pageout_garbage_collect","user_usec":0,"schedPriority":31,"system_usec":1,"state":["TH_WAIT","TH_UNINT"],"waitEvent":[0,1338336]},"113":{"continuation":[0,568288],"userTime":0,"systemTime":9.8414999999999999e-05,"id":113,"basePriority":63,"name":"daemon.core-analytics-events","user_usec":0,"schedPriority":63,"system_usec":98,"state":["TH_WAIT","TH_UNINT"],"waitEvent":[0,17495864]},"174":{"userTime":0,"systemTime":6321.3300071809999,"system_usec":6321330007,"id":174,"basePriority":0,"user_usec":0,"kernelFrames":[[0,1846048],[0,653418],[0,653929],[0,61854]],"schedPriority":0,"name":"idle #10","state":["TH_RUN","TH_IDLE"]},"240":{"continuation":[0,8596736],"userTime":0,"systemTime":2.5390000000000002e-06,"id":240,"basePriority":81,"name":"AppleACPIButton","user_usec":0,"schedPriority":81,"system_usec":2,"state":["TH_WAIT","TH_UNINT"],"waitEvent":[1,13718365294252224889]},"75374":{"id":75374,"schedPriority":81,"system_usec":450763,"state":["TH_WAIT"],"schedFlags":["TH_SFLAG_EAGERPREEMPT"],"user_usec":0,"basePriority":81,"userTime":0,"waitEvent":[0,1523

following up on my post to this thread - I found a thread out there in the inter webs that was similar to this one. There was an answer posted that recommended adjusting the main display (native) to 50 Hz (down from 60 Hz) to see if it helped. Indeed it worked for me. I do not have the link to the article, but this change in the main laptop Mac display setting allowed the 2 external LG monitors to be recognized and display without crashing my system. I hope this helps others.

I am also facing same issue. My Intel based bacbook pro 13" is connected to two displays using a dell docking station. Both the displays are connected through single thunderbolt cable.

Yes this is still an issue. 2 27 inch monitors via USB-C.

For my macbook pro (16-inch 2019) this issue first happened first time after Monterey release. It happens each time I start my computer, then connect display without waiting for a while or when monitor suddenly disconnected and than connected again. Only hard shutdown helps.

I had an identical case on a MacBook Pro 16 (the most powerful configuration from 2019, i9, 64GB ram). Connection with TWO external monitors (Samsung, 27 inch, 4k) by original Samsung cable (USB-C -> HDMI) After setting the configuration to (2560 x 1440) there is a crash, black screen and computer shutdown.

The only solution that allowed me to set this configuration is the program BetterDisplay: https://github.com/waydabber/BetterDisplay

I'm not affiliated with the author, I don't make any money from it, it's not an advertisement - it just works!

After setting the configuration, of course, there is also a crash, black screen and restart. But after reboot, the "configuration" (something/somewhere) is saved and it works forever. So when you reconnect this set of monitors, there is no problem anymore. Tested on several Macbooks.

I have the same issue, panic crash. MacBook Pro 16 intel 2019. Connected to one Acer 27 inch, 4K. Original Belkin Display port cable from Apple.

The issue happens every time the MBP: hibernates, enters screen saver, turn off monitors on savings or unplug the second monitor. Bug still persists, do we still have updates on intel system?

Can confirm on MBP 2019 w/ Ventura 13.2.1 the kernel panic crash still exists. I was able to get back to my desired resolution with BetterDisplay trick.

Macbook Air 2020 - crashing during sleep with two external monitors (Viewsonic and Philips). Escalated to senior Apple tech support which ultimately, after lots of software maneuvers, concluded that it was a hardware problem and replaced motherboard. No improvement. Oddly, I recently had problems with Apple Mail indexing and replaced it with Outlook and have been several weeks without crash. Could Apple Mail have been the culprit? No other changes to configuration. Big Sur 11.7.1

Kernel panic crash with 2 external LG displays - Monterey 12.0.1 MacBook Pro (16-inch, 2019)
 
 
Q