Roon software reboots unexpectedly while playing music (ref#X0SD8M)

What best describes your playback issue?

· Music stops playing mid-track

Is there a specific error message you see? If so, please select from the following options:

· Other

Please try to reboot your Roon Server and check to see if this helps.

· Rebooting my Server had no effect, the issue remains

Please try to reboot and unplug/replug in your affected audio device and check to see if this helps.

· Rebooting and unplugging/replugging my audio device, the issue remains

Please open your Roon Remote and select the "System Output" Zone and try to play to it. Do you encounter any playback errors with this Zone?

· Playback *errors for both* my other zone and when I play to System Output as well

Please try fully rebooting your network equipment

· No, I'm still having trouble

An issue with playback on System Output and another zone often indicates a network security problem. *Check your firewall(s)* to ensure that *Roon*, *RoonServer *and *RAATServer* are allowed to properly communicate

· I'm still having problems / This isn't relevant to me

Does the issue happen with local library music, streaming service music, or both?

· Both local and streaming content are affected

Please try playing content of a lower sample rate (44.1kHz or 48kHz). Do you still have the same issue?

· No, lower sample rates are still affected

What is the model/manufacturer of the affected audio device(s) and the connection type?

· TDAI-1120

Describe the issue

Roon reboots in the middle of playing any track

Describe your network setup

Wired netwrok. Fiber router

What device (PC, Mac, Nucleus, NAS, etc.) is your Roon Server running on? Thanks.

My Roon server is a window 10 home server.
Latest system update is installed

If that’s the case, the Windows Event Viewer should be able to give more information on what is happening when the Roon Server reboots. What does it say?

I’m wondering whether in fact this is not a “rebooting” issue, but a network issue that is causing communication to be lost between your Roon Server and your playback device? I’ve not come across an instance of Roon Server running on Windows “rebooting” - crashing yes, but rebooting, no…

How do I activate the windows event viewer?
I sent the screenshots it mentions rebooting.
All my devices are connected via wired network.
What is the next step ?

Click Start and type “Event Viewer” (without the quotes) into the search field to bring up the Windows Event Viewer, which you can then click to start.

You want to look at the Application log, click “Filter Current Log…” and check the “Error” box followed by “OK” to show just the error events. See the following screenshot to see how to set this up:

Is the Roon Server in this list?

The only screenshot I see in your first post does not mention rebooting - only waiting for your Roon Server?

below is the event viewer output -

Log Name: Application
Source: Application Error
Date: 16/05/2024 18:07:38
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-30CE8GS
Description:
‏‏שם יישום שחלות בו תקלות: RoonAppliance.exe, גירסה: 1.0.0.0, חותמת זמן: 0x65fc7138
שם מודול שחלות בו תקלות: coreclr.dll, גירסה: 6.0.2924.17105, חותמת זמן: 0x65fc6ae4
קוד חריגה: 0xc0000005
היסט תקלה: 0x00000000001d3c89
מזהה תהליך שחלות בו תקלות: 0x37f0
שעת ההפעלה של היישום שחלות בו תקלות: 0x01daa7a2b8bf0439
נתיב היישום שחלות בו תקלות: C:\Users\חיים שפר\AppData\Local\RoonServer\Application\RoonAppliance.exe
נתיב המודול שחלות בו תקלות: C:\Users\חיים שפר\AppData\Local\RoonServer\Application\200001413\coreclr.dll
מזהה דוח: 9be4fc06-4e70-4ed1-8347-b909fd0bc753
שם מלא של החבילה שחלות בה תקלות:
מזהה יישום יחסי לחבילה שחלות בה תקלות:
Event Xml:



1000
0
2
100
0
0x80000000000000

4052323


Application
DESKTOP-30CE8GS



RoonAppliance.exe
1.0.0.0
65fc7138
coreclr.dll
6.0.2924.17105
65fc6ae4
c0000005
00000000001d3c89
37f0
01daa7a2b8bf0439
C:\Users\חיים שפר\AppData\Local\RoonServer\Application\RoonAppliance.exe
C:\Users\חיים שפר\AppData\Local\RoonServer\Application\200001413\coreclr.dll
9be4fc06-4e70-4ed1-8347-b909fd0bc753





The event viewer is enclosed

Hi @Haim_Sheffer1,

Feel free to upload the full event viewer log here:

https://workdrive.zohoexternal.com/collection/8i5239cc05950ac07456889838d9319545a82/external

Thanks!

I have uploaded it. thanks

Thanks @Haim_Sheffer1! Our team will review it and I should have more information to share after that.

In the meantime, could you please refresh your database on the windows and see if your issues persist? The steps are below:

  • Make a Backup of your current RoonServer Database
  • Exit out of RoonServer
  • Navigate to your RoonServer’s Database Location
  • Find the folder that says “RoonServer”
  • Rename the “RoonServer” folder to “RoonServer_old”
  • Reinstall the RoonServer App from our Downloads Page to generate a new RoonServer folder
  • On the Roon Remotes, press “Use another Roon Server” and connect to the new database

I sent another instance of the event - event 1000 application error. It happened today.
I will follow your steps and report.

I lso have sent the roonserver log file

Hi @Haim_Sheffer1,

As a quick side test as well, can you reproduce the issue without the eversolo USB device active? What happens if you play to the system output of one of your remote devices?

I do not use eversolo but Lyngdorf.
It happens occasionally not always. It happened also with system output.

Hey @Haim_Sheffer1,

Thanks for the update - we’re seeing a lot of activity with an eversolo device, I’d triple check that you don’t have any extra device attempting to connect with Roon.

As a next step, let’s fully remove Roon from the windows and do a fresh install - do you have a recently saved backup?

After you uninstalled Roon, navigate to C:\Users\[*Your username*]\AppData\Local and delete all Roon folders:

RAATServer
Roon
RoonGoer
RoonServer

After a fresh install (download here), restore your recently saved backup to load your prior library settings.

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