· None of the above quite fits
· None of these quite match
· Music stops playing mid track and no error messages displayed
· Full fibre 150 Mbps internet. Sky supplied router feeding into TP-Link Deco x55 mesh. Roon Server PC plugged into ethernet port of Deco x55 pod.
Hey @Meldrew61,
Thanks for writing in and sharing your report! From a fresh daignsitoc report, we can see the playback engine gives up.
Unexpected Failure While Opening Sound... IoFailure.
StoppedEndOfMediaUnnatural. This is why your music simply cut out instead of continuing to the next song.
0.99% GC pauses), the intense database writing (endmutation) and search indexing occurring every few seconds can cause "micro-stuttering" in how the Core handles new network requests.
If this happens frequently, try lowering the streaming quality to 16/44.1 (CD Quality) temporarily. If the problem disappears, it confirms that your local network or Core’s current processing load is struggling to maintain the “perfect” timing required for high-resolution cloud streaming.
Feel free to share a specific track name the next time this happens if the above doesn’t help. Thank you! 
This is happening all the time. The music I am playing is local files stored on Samsung M.2 NVMe drives installed on the PC running Roon Server. The PC has Intel i9-10900T CPU and 64GB DDR4 RAM. The music is being streamed to a Devialet Expert 44o Pro using Exclusive WASAPI USB. There should be no network involved in this scenario, everything is local to the Roon Server. I cannot give a specific track because it is not track based. All the music files are valid FLAC and have been verified with dbpoweramp Test Conversion. The drives have no errors and the file system has no errors/corruption. What diagnostic report are you viewing and how did you obtain it?
Hi @Meldrew61,
For context, we’re reviewing logs, which can access locally on your machine by navigating to your database location:
The vast majority of the dropouts we see in logs occurred between 04/24 and 04/27 and resulted from a content delivery failure between the Qobuz content delivery network and your RoonServer. These were Qobuz streaming failures caused by a known issue on Qobuz’s end that they have since resolved. Roon released a hotfix that prevented these failures from breaking playback entirely; the silent failure you were encountering was the expected fallback while Qobuz worked to resolve the problem. This problem has since been resolved, so if you are experiencing playback problems with streaming, please share the name of a track here.
We don’t see any overt audio transport failures with local hi-res content in the latest set of logs. We’ll really need to know an approximate timestamp of any given local playback failure (or a screenshot of the Signal Path) in order to pinpoint the events you are describing and deduce what’s occurring.
Just for due diligence, do you have the latest firmware installed for this Devialet endpoint? Do you have this problem if you play to the System Output of the Windows machine instead, using ASIO or WASAPI non-exclusive?
We’ll watch for your reply.
Hi, I experienced the Qobuz steaming issues and understood the causes. I daily read the community posts, more for entertainment than issues especially the sound quality debates (bits are just bits). This is a relatively new issue and not caused by the recent release. I cannot find any issues with the hardware. Does Roon Server log to the Windows event log? I have found various text logs in users app data but couldn’t see anything specific to a track stopping playing. When this occurs again is there anything more specific I can capture to pinpoint the cause? Regards, Andrew. PS I’m an ex Win32 C++/C# .NET software developer so know a thing or two.
Hi @Meldrew61,
Thanks for the additional information! Some additional next steps for you:
Do a full PC reboot, not just a Roon restart.
Check Windows Device Manager and Event Viewer for the storage drives. Even if chkdsk shows no errors, look in Event Viewer → Windows Logs → System for any entries around 09:29–09:36 mentioning disk errors, AHCI/NVMe controller resets, or “disk not ready” events. The drives may be entering a power-saving state that Windows briefly drops them from before Roon can access them.
Disable drive sleep/power management for your data drives. Go to Device Manager → Disk Drives → right-click each Samsung SSD → Properties → Power Management → uncheck “Allow the computer to turn off this device to save power.” Also check Power Options in Windows and set it to High Performance (or a custom plan with drive sleep disabled).
NTP / Clock: Resync Windows time - Open an admin Command Prompt and run w32tm /resync /force. Then check w32tm /query /status to confirm it’s syncing cleanly. The negative clock skew Roon logged is unusual for an NTP-synced machine.
We’ll be monitoring for your reply and results!
Hi @Meldrew61,
We don’t see obvious track dropouts logged, but the most recent diagnostics from your Roon Server show novel but generic connection errors from Qobuz server during routine background activity (library sync, login/authorization, etc).
I recommend signing out and back into your Qobuz account within Roon and then forcing a sync from the same page.
Do you rely on any consumer VPNs that might affect the network pathway? Do you have any issues with the Qobuz native app or web player?
We’re going to allow this thread to auto-close due to inactivity at this time, but please reach out here in a new tech support request if we can assist further.
Thank you!