Roon keeps stopping playback and restarting Library details: Artists: 33,397 Albums: 79,654 Roon just crashed again so I can't finish getting the library details
Describe your network setup
Verizon Fios 1GB fiberoptic Verizon CR1000A router Ethernet connection to Roon server Ethernet connection to Roon ready endpoint Roon server: Windows 10 Home, 64 bit, version 22H2, OS build 19045.5011 Processor: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz 4.20 GHz RAM: 64.0 GB
This behavior started on Monday and I rebooted my Roon server. Roon did not crash again on Monday or Tuesday. However Roon started crashing and restarting again today (Wednesday).
When Roon crashes it just stops playing and restarts with no input on my part.
I am trying to determine if the crashes occur when playing local files or when playing Tidal/Qobuz files or both, however the crashes are very random and that makes it difficult to determine.
The crashes that have occurred today have been during playback from Qobuz. Also Qobuz selections take about one minute to start playing.
I have made a zip file of the last 7 log files and can send it if needed.
Things have now gotten much worse - Roon now just cycles starting->crashing->restarting->crashing->restarting…
With or without any music (local or Tidal/Qobuz) playing
Another update: after looking at the logs it appears that this behavior might be caused by an interruption in the connections to Tidal and Qobuz (remember that I’m no expert in this area) so I tried rebooting my Verizon router and restarting Roon.
So far so good - Roon has now been playing some music from Qobuz for the past 45 minutes without any issues. I will update again after another few hours of playback.
Hi @Jazzfan_NJ,
Thanks for writing in to ask us about this issue and for providing the extra details. I’ve activated diagnostics on your account and we will review those when they come in.
Definitely let us know how this went. It’s entirely possible that the router restart is exactly what was needed.
I’m pretty sure that this issue is related to the POS Verizon router but any help in narrowing down what is actually causing this odd behavior would be greatly appreciated. It would also be helpful in getting Verizon to fix their side of things.