Hi. Ive been a Roon user for 5 or 6 years and never had an issue until last night.
I have a fanless NUC box running windows 11 hosting Roon Server which i use for a few Hi-Res Albums but mostly using Qobuz.
All was great until last night when Roon advised me there was an Update. I went ahead as usual and then ‘Boom’ … my Roon client lost connection to the Server.
Went to look at the Server and i was constantly getting an error pop up ‘a new guard page for the stack cannot be created’.
I googled and saw most people saying this is a out of memory issue - however, i have 16Gb and i was using 5Gb.
I tried the usual, renaming the RoonServer folder and setup fresh, uninstalling Roon and reinstalling… all to no avail.
I decided i would look at it another day (and possibly wipe the box and do a fresh install) - so in the meanwhile, i thought ‘i’ll install in on my Laptop to keep me going’.
However, this is also causing issues. im getting the exact same symptoms on the laptop as i get on the NUC box - just not the popup.
The symptoms are that the server keep trying to start then dies… then attempts again… one really odd side effect is this is also somehow killing my Router - so even after i kill the Roon processes i have no internet connection and have to reboot the Router.
Looking at the Eventlog i have two Application Crashing Events being raised :-
Hi. Ive been a Roon user for 5 or 6 years and never had an issue until last night.
I have a fanless NUC box running windows 11 hosting Roon Server which i use for a few Hi-Res Albums but mostly using Qobuz.
All was great until last night when Roon advised me there was an Update. I went ahead as usual and then ‘Boom’ … my Roon client lost connection to the Server.
Went to look at the Server and i was constantly getting an error pop up ‘a new guard page for the stack cannot be created’.
I googled and saw most people saying this is a out of memory issue - however, i have 16Gb and i was using 5Gb.
I tried the usual, renaming the RoonServer folder and setup fresh, uninstalling Roon and reinstalling… all to no avail.
I decided i would look at it another day (and possibly wipe the box and do a fresh install) - so in the meanwhile, i thought ‘i’ll install in on my Laptop to keep me going’.
However, this is also causing issues. im getting the exact same symptoms on the laptop as i get on the NUC box - just not the popup.
The symptoms are that the server keep trying to start then dies… then attempts again… one really odd side effect is this is also somehow killing my Router - so even after i kill the Roon processes i have no internet connection and have to reboot the Router.
Looking at the Eventlog i have two Application Crashing Events being raised :-
Update - I decided to wipe my windows 11 install on the NUC (the one complaining about ‘A new Guard page…’ and do a virgin install of Windows 10. I then installed Roon again - and im now getting the exact same issue as i was getting on my laptop.
I have zipped the logs and uploaded them via your portal.
Many thanks in advance for any help you can provide.
Thank you for sending over the logs — I’ve reviewed them, but I don’t see the crash report file included. Could you please re-upload the following so we can get a clearer picture of the error?
The Report.wer file generated at the time of the crash.
A screenshot (or export) from Windows Event Viewer → Windows Logs → Application showing the RoonAppliance crash entry.
This will help us confirm exactly what’s failing inside the runtime.
In parallel, please also reinstall the Microsoft .NET Desktop Runtime, since Roon relies on this and a corrupted install can cause the coreclr.dll crash you’re seeing:
Go to Microsoft’s official site:
Under .NET 6.0 Desktop Runtime, choose Download x64.
Once downloaded, run the installer.
Restart your machine.
Launch RoonServer again.
This step is important, as it will replace any corrupted runtime files that may not have been cleared by reinstalling Roon itself.
Please let us know once you’ve uploaded the Report.wer file and Event Viewer screenshot, and confirm if reinstalling .NET changes the behavior.
Thanks. i have just uploaded a fresh set of logs, events and report files.
Here is the setup i have:-
Windows 10 NUC box (fresh install from freshly formatted drive- then updated via Windows update with the latest updates)
This is connected to my Virgin Media Router via a tp-link TL-SG108 switch.
After your message this morning, i installed the .Net 6 Desktop runtime, rebooted and then installed Roon.
It initially started ok… allowed me to connect to the server and setup the Qobuz account.
However, i then got a message saying it was trying to connect to the Server (im paraphrasing).
Finally, my wired network died - Oddly, the wifi still works - (ive seen this previously in my day job around multicasting issues - im assuming thats what Roon uses).
The only solution is to kill the Roon processes and restart my Router (thinking about it i may have only needed to restart the switch).
Ok, so i did as you suggested - i started roon server and then on the same box ran roon.
This seemed to work ok, i then tried to connect off my android app. The roon server immediately died and lilled my network.
So I left the roon server running and restarted the router.
This then seemed to work. I could play both via roon on the server and on my phone.
I then wanted to see if this state would persist, so i then rebooted my Nuc server and started the roon server. Again, as soon as i connected via my phone app it killed the roonserver and caused the wired network to die.
So there is clearly an issue that happens every time i run roon server on a rebooted box and then try to connect via another device.
Also, strange side effect - is even when i get the Server and app working, its not happy logging me in to Qobuz… i have checked and can login just fine via their webpage
Can you please pass on the following to the team:-
To eliminate possible issues i removed the Switch from the equation. The issue still occurs when the Server is directly connected to the Router and the switch is disconnected.
I cannot get it to work at all now. Roon remote cannot see the Roon server - even when ran on the same machine (looking at 127.0.0.1).
Do you have any idea when a resolution will be available please? ive just subscribed to another year of Roon so i am keen to get this resolved asap.
Is there no way i can get the previous release? this has only happened since i upgraded to build 1554. It literally crashed the moment i updated the server with the new release.
Seems you are facing the issue with the code changes introduced earlier. We have reverted the changes to your account. Please restart the Roons Server multiple times and let us know if it fixes the issue.
Can you please explain what this issue was so im aware for future releases??? And if you need me to change something to fix the issue my end as you said you have reverted my account specifically…
Ok. Well, i tried it earlier and it seemed to work again. All was well for 5 hours or so…
Then about 10 mins ago it went down again.
Im hoping its something your end that.is being switched back qnd forth… as my environment is exactly as it has been for the last 4.or 5 years and hasnt changed.
Can someone please come back to me as to what is happening with my Setup.
It is still down and the fact that yesterday when it was like this you told me you had reverted changed to my account meant it immediately started working suggests it was something on your side which has now for some reason reverted.
Ive raised a new topic as the previous one from yesterday was marked as solved and i have not had any feedback from the team since then so wasnt sure it was still being monitored.
The issue i have was deemed by @vadim to be an issue at the roon end and upon an update reverting my settings (see here Roon Server crashes after recent update causing connection issues and affecting network (ref#UTJI9I) - #11 by vadim) it worked perfectly for 5 or so hours. It then stopped working and is still unusable.
Can someone please look into this as according to his initial reply (which was later edited) it stated it was due to ipv6 changes.
We are sorry to hear that you are still facing the issue.
We’ve discussed this with our senior QA and development teams. The team is investigating some possibilities here and, as soon as that investigation is complete, we’ll be sure to follow up ASAP.
In the meantime please follow the guide below
Open Network Connections
Press Win + R on your keyboard, type ncpa.cpl, and press Enter.
This will open the list of network adapters.
Find your active network adapter
Look for the network you are currently using (for example, “Ethernet” if you are wired, or “Wi-Fi” if you are on wireless).
Right-click it and select Properties.
Disable IPv6
In the list under “This connection uses the following items”, find Internet Protocol Version 6 (TCP/IPv6).
