![]() |
|
|||||||
![]() |
|
|
Thread Tools | Search this Thread | Display Modes |
|
|
#1 |
|
Junior Member
Join Date: Sep 2026
Posts: 1
|
My previously working two-monitor DisplayLink setup stopped working during the morning of 24 September 2026. I am looking for help identifying the cause, and whether there is a known macOS 27 issue, a diagnostic build, or a fix.
Setup - MacBook Pro, Apple M5 Max, model identifier Mac17,7, 64 GB RAM. - macOS 27.0 Golden Gate, build 26A428, installed on 20 September. - DisplayLink Manager 17.0.24; also tested 16.2.39 as a rollback. - USB device identifies as "Quad Video Dock", VID 0x17e9 / PID 0x4307. I have not confirmed the retail dock model. - Two external monitors: Dell P2417H and iiyama PL3270Q (ProLite XB3270QS family; exact suffix unconfirmed). What happens The dock repeatedly disappears from the USB device tree and reappears with a new registry ID, approximately every 2.5 seconds. Its associated USB hubs disappear too. The displays fail to stay connected. Both monitors were working at approximately 09:00 on 24 September. The first retained burst of DisplayLink display-reconfiguration messages was around 09:54, but this does not establish the exact physical-disconnection onset. The failure began before DisplayLink 17.0.24 was installed at 10:15. All these times are CEST (UTC+2). Diagnostic findings - DisplayLink 17.0.24 crashed at 11:05:04 on 24 September with a null-address access on the DeviceNotifier_ thread. - After rolling back, 16.2.39 crashed at 11:33:43 with the same exception/thread pattern. This was a troubleshooting comparison, not an assumption that 16.2 officially supports macOS 27. - Kernel USB messages recorded 0xe0005000 (pipe stalled) for the Quad Video Dock. The same logs also contain 0xe00002ed (transaction error) for the RODE USB microphone; those microphone errors should not be attributed to the dock. - Repeated sampling confirmed complete dock/hub disappearance and re-enumeration, including a measured median interval of about 2.48 seconds in one test. Tests already tried - Restarting the Mac, power-cycling/reconnecting the dock and trying other Mac USB-C ports. - Removing DisplayLink with the vendor cleaner and reinstalling it. - Testing both DisplayLink versions above. - Using only one external monitor. - Testing with Chrome and ChatGPT closed and the RODE peripheral disconnected. - Stopping/removing a separate local window-management utility that initially looked suspicious because of its launch timing. The USB reconnect loop continued while it was absent or verified suspended, so its ongoing execution was not required for the failure. The same cable and dock had worked earlier that morning. I have not established whether the cause is software, the dock, power, a cable, or the monitor. As of 25 September, Synaptics still lists DisplayLink 17.0 (17.0.24), and macOS Software Update offers no newer update for this Mac. Could DisplayLink support advise whether this whole-dock reconnect loop together with DeviceNotifier_ crashes is a known issue on macOS 27 / Apple M5 Max? Is there a newer diagnostic build or a recommended test to distinguish a USB/power problem from a software regression? A DisplayLink Support Tool bundle and the crash reports have been retained locally. Please advise on the appropriate private support channel for any diagnostics you need. |
|
|
|
![]() |
|
|