Hey @Ravenor,
Thanks for the update! We were able to review a fresh Roon log analsis, and can confirm what @vadim has shared above:
The log shows a burst of repeated, identical resize events:
15:46:46 render area size changed value: 2048x1080.8
15:46:47 [windowpos] saving pos=... because size changed to {Width=2062.4, Height=1118.4}
15:46:48 render area size changed value: 2048x1080.8
15:46:49 [windowpos] saving pos=... (same size)
15:47:09 render area size changed value: 2048x1080.8
15:47:13 render area size changed value: 2048x1080.8
15:47:14 [windowpos] saving pos=... (same size)
That pattern, the same window snapping back to the same size/position over and over in rapid succession, is the log fingerprint of minimize/maximize cycling, exactly what you’ve described doing to trigger the bug.
Immediately after the last resize, the very next rendered frame stalls hard:
15:47:15 Warn: frame took 1240.48ms! 63.95ms preframe, 0.00ms safe queue, 5.46ms timers, 0.00ms frame calls, 1.02ms update, 1240.48ms render
This is strong, concrete confirmation that the hang is a GPU render-call stall on the Intel Arc 130T triggered specifically by the resize event from minimizing/maximizing, not a RoonServer, network, or app-logic issue.
Given the confirmed render-stall signature, the next steps I’d try, roughly in priority order:
Disable Multi-Plane Overlay (MPO). This exact symptom cluster (GPU spike, brief hang, audio glitch on resize/minimize with Intel Arc) is a well-documented MPO/compositor bug, not just a generic “update your driver” issue, it’s the same category as the GitHub issue Vadim linked.
The fix: add a DWORD value OverlayTestMode set to 5 under HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers, then reboot. This disables MPO system-wide and is the standard workaround for exactly this Intel Arc flip-model hitch. Worth trying before anything else, since it targets the specific mechanism the logs point to.
Re-check Hardware-accelerated GPU Scheduling. You said you couldn’t find “Change default graphics settings,” but on Windows 11 the HAGS toggle lives at the top of Settings → System → Display → Graphics (a standalone switch, not under the per-app default-settings link he found). Worth confirming you’re looking at the right control and toggling it off if currently on.
Driver-level troubleshooting beyond a simple update:
- Clean-reinstall the Arc driver with DDU (Display Driver Uninstaller) rather than an in-place update, in case remnants of an older driver are conflicting.
- Check whether a newer Arc driver has shipped since 32.0.101.8860 that specifically addresses Core Ultra Series 2 compositor issues.
Isolate the monitor/resolution variable. You already noticed the glitch is worse on the 2560x1440 display than the 1920x1080 one. Worth testing with only the primary monitor connected, if it disappears or shrinks with one display, that points more specifically at multi-monitor compositor load on the Arc GPU rather than a pure driver bug, which changes the escalation angle.
Workaround in the meantime: since you already confirmed the issue doesn’t occur when the window isn’t full-size, running Roon maximized-but-not-true-fullscreen (or just avoiding minimize/restore cycles while music is playing) sidesteps it without waiting on Intel.
Let us know if any of the above help, thank you!
