Hello, I bought a Dell 27 Plus S2725QC monitor for my MacBook Pro M1. I'm connecting it via Type-C, but there's no sound coming from the monitor. How can I fix this?
SOLVED — it was not the monitor, and not a DisplayPort/firmware issue.
Follow-up to my diagnostic report above. After further testing, the S2725QC is not defective and no RMA is needed.
The root cause is on the macOS side: coreaudiod degrades over long uptime and loses the ability to negotiate the monitor's DisplayPort audio channel.
The fix — one command:
sudo killall coreaudiod
Then select "DELL S2725QC" as the output device. Audio drops for ~2 seconds and comes back working. How I isolated it. The failure is intermittent, so I captured a full system snapshot in the working state and one in the broken state and diffed them. Every variable was identical — same 60 Hz refresh rate, same cable, same port, same firmware (M3B102), same transport — except one: the uptime of coreaudiod. Broken state: 1 day 23 hours. Working state: 5 minutes (freshly restarted). A coreaudiod that has been running for days, across many sleep/wake cycles and Bluetooth device switches, stops handshaking the DP audio endpoint correctly.
Log signature. Broken: HALS_IOContext_Legacy_Impl::StartIOThread: the IO thread failed to start, Error: 1937010544 (fourcc 'stop'). Working: IOWorkLoopInit … starting followed by stopping with error 0. In the broken state the device still enumerates and still accepts samples — it just never clocks them out, which is also why video playback freezes in every app while the Dell is the default output. That freeze is the tell-tale sign: it is not a mute, it is a stalled audio device.
What was NOT the cause (all tested and ruled out): monitor firmware (updated to M3B102 anyway), DDC/CI, DDPM permissions, OSD factory reset, sample rate, refresh rate (identical behaviour at 60 Hz and 120 Hz), HDMI vs USB-C (fails on both), the cable, and hot-plugging.
A restart of the Mac fixes it too, for the same reason — it restarts coreaudiod. But the killall is instant and does not interrupt your work.
Click the blue "Get Help Now" on the right to start a private live chat session. Share with them the private S2725QC Service Tag, issues, this thread link, and all of your troubleshooting. This will in turn generate a unique Technical Support case for your unique Service Tag.
Enter the S2725QC Menu--> Audio. Make sure it is set = Volume 50 Speaker On
Once set in the S2725QC Menu, the source computer controls the audio INTO the S2725QC. Open the Apple OS sound settings and choose the S2725QC as default audio device.
When the S2725QC is connected via USB-C (DP Alt Mode) to a MacBook Air M2, the monitor's audio device enumerates in macOS but its audio I/O thread fails to start at the CoreAudio HAL level. As a side effect, whenever macOS auto-selects the monitor as the default output device, all video playback system-wide hangs indefinitely(AVFoundation players wait on the default output device's clock: Safari, Chrome, QuickTime, local files).
The issue is fully reproducible and persists after every remediation attempted, includinga monitor firmware update to M3B102.
The monitor's audio device appears in Sound settings as "DELL S2725QC" (DisplayPort audio, 48 kHz). Its manufacturer ID in the device UID is 0x10AC (= 4268, DELL):10AC72A2-0000-0000-0723-0104B53C2278.
When any app tries to start audio I/O on it, coreaudiod logs this failure loop (repeating every ~10 s while the device is the default output):
HALS_IOContext_Legacy_Impl::StartIOThread: the IO thread failed to start,
Error: 1937010544 (FourCC 'stop')
HALS_IOContext_Legacy_Impl.cpp:2415 Initialize failed - thread hasBeenStopped: 0 and shouldExit: 1
HALS_IOContext_Legacy_Impl::IOWorkLoopDeinit: ... 10AC72A2-...: stopping with error 1937010544
Additional observation: system_profiler SPAudioDataType lists the "DELL S2725QC" device but with an empty property section — no sample rates, no channel info — suggesting the device publishes no valid stream formats to the HAL.
After restarting coreaudiod, the very first short I/O session on the device can complete cleanly (stopping with error 0), but sustained I/O immediately falls back into the 'stop' failure loop. Behavior is intermittent at the level of single sessions, but no audio is ever produced by the monitor speakers.
Hardware video decode is unaffected (all VideoToolbox/AppleAVD sessions create witherror 0); the playback hang is purely the audio-clock wait.
Dell community thread "S2725QC, MacBook Pro M1, no sound" describes the same symptom on a different Apple Silicon Mac; the suggested OSD/Sound-settings steps did not resolve it for those users either (still unresolved as of May 2026).
This looks like a DP-audio handshake/descriptor issue between the S2725QC scaler and macOS's DisplayPort audio class driver (device enumerates but exposes no usable stream formats / rejects I/O start). Please escalate to engineering — a scaler firmware fix appears required, as M3B102 does not address it.
Good post. It needs to go through Technical Support to create a case.
Click the blue "Get Help Now" on the right to start a private live chat session. Share with them the private S2725QC Service Tag, issues, this thread link, and all of your troubleshooting. This will in turn generate a unique Technical Support case for your unique Service Tag.
nemone81
1 Rookie
•
2 Posts
•
8 Points
1
0
Posted July 13th, 2026 14:13
SOLVED — it was not the monitor, and not a DisplayPort/firmware issue.
Follow-up to my diagnostic report above. After further testing, the S2725QC is not defective and no RMA is needed.
The root cause is on the macOS side: coreaudiod degrades over long uptime and loses the ability to negotiate the monitor's DisplayPort audio channel.
The fix — one command:
sudo killall coreaudiod
Then select "DELL S2725QC" as the output device. Audio drops for ~2 seconds and comes back working. How I isolated it. The failure is intermittent, so I captured a full system snapshot in the working state and one in the broken state and diffed them. Every variable was identical — same 60 Hz refresh rate, same cable, same port, same firmware (M3B102), same transport — except one: the uptime of coreaudiod. Broken state: 1 day 23 hours. Working state: 5 minutes (freshly restarted). A coreaudiod that has been running for days, across many sleep/wake cycles and Bluetooth device switches, stops handshaking the DP audio endpoint correctly.
Log signature. Broken: HALS_IOContext_Legacy_Impl::StartIOThread: the IO thread failed to start, Error: 1937010544 (fourcc 'stop'). Working: IOWorkLoopInit … starting followed by stopping with error 0. In the broken state the device still enumerates and still accepts samples — it just never clocks them out, which is also why video playback freezes in every app while the Dell is the default output. That freeze is the tell-tale sign: it is not a mute, it is a stalled audio device.
What was NOT the cause (all tested and ruled out): monitor firmware (updated to M3B102 anyway), DDC/CI, DDPM permissions, OSD factory reset, sample rate, refresh rate (identical behaviour at 60 Hz and 120 Hz), HDMI vs USB-C (fails on both), the cable, and hot-plugging.
A restart of the Mac fixes it too, for the same reason — it restarts coreaudiod. But the killall is instant and does not interrupt your work.
Hope this saves someone the two weeks it cost me.
(edited)