Scrolling Lyrics cause Roon to shutdown

Roon Core Machine

Win 11 Home
Overclocked Intel i7 9700k @ 5GHz

Networking Gear & Setup Details

Asus RT-AX88U via Ethernet

Connected Audio Devices

USB to Topping D50s

Number of Tracks in Library

Approx 2000 via Qobuz

Description of Issue

After updating to build 903, I experience a crash everytime I attempt to view scrolling lyrics while streaming Qobuz. When entering the scrolling lyrics screen they will stutter almost instantly but auto scroll for a few seconds before crashing and closing down Roon. This issue was not evident in prior builds and seems to have been introduced after the 903 update.

HI @DonRom,

Is this only happening on your Windows Core. We’ve seen Windows updates cause issues with graphics drivers which results in this behavior. What is the GPU for your device?

Windows’ automatic driver updates can sometimes be a bit unreliable, and we’ve seen direct downloads from the manufacturer help in cases where Windows installations did not, so it’s worth a try if you haven’t gone that route.

Please follow these steps:

  • quit Roon
  • reboot the Windows machine
    • Turn off your Roon Core
    • Unplug your Core for a few minutes
    • Plug the Core back in
    • Turn on the Core
  • uninstall your graphics drivers
  • navigate to the manufacturer’s website for your Graphics Card (for example, a popular one is NVIDIA) and download the graphics drivers directly from there
  • install the graphics drivers
  • relaunch Roon and check your audio devices page.

Please let us know if this helps. Thanks

Been having the same issue myself, seems to be similar if not the same as the issues we are seeing in Windows 11 & Release 1.8 (903): Scrolling Issues and Random Crashing - #2 by SlyBlue

Thank you. I have an old GTX 1070 (damn crypto miners and chip shortages) and my drivers are always up to date. In any case I did as you suggested and then reinstalled the latest driver. During the process i was prompted to update Roon to build 913, which i did - and this combined with the re-installation of graphics drivers seems to have resolved the issue.


This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.