Help wanted - NUC running Roon drops off network

This is not strictly a Roon question, rather a question about the computer on which I am running it (set-up details below). I run Roon on a W10 NUC that is attached directly to my router (a BT Home Hub 2) by ethernet. With increasing frequency the machine drops off the network and has to be hard-restarted via the on-off switch. My problem is I don’t know where to look to identify the cause; unlike my mac the NUC does not provide a crash report (as fas as I know) that will give me a clue as to the cause. I am hoping that someone with more knowledge of hardware/software diagnostics on PCs can point me in the right direction. Hardware/software set-up details below.

• Core Machine (Operating system/System info/Roon build number)**

Roon 1.8 (build 831) on Intel i7-8559U NUC w 16GB RAM running windows 10 pro (version 20H2).

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

connection is via wifi

Intel NUC → BT Home Hub 2 via Ethernet

BT Home Hub ->Netgear Orbi

Netgear Orbi-> Roon endpoints via wifi

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

various, currently iMac running Roon 1.8 (build 831) on macOS 11.2.3 via wifi

Have you looked in Windows logs, its called Event Viewer and has logs for hardware, software, etc This might help.

Thanks. I will do that.

Hi

I checked Event Viewer the next time I noticed that the NUC had become unresponsive. I could see when the machine went down as there was nothing in the systems logs after that until I rebooted the NUC but at the same time nothing to indicate why the machine hung. Weird.

Aidan

@support I wonder if you can help with this.

I have done bit more investigation and now believe that this issue is Roon-related, even if not directly Roon-caused. The background is given in my 1st post but since then my NUC has been crashing silently (no error message) about once a day. I experimented with just leaving the NUC on without running Roon for a few days and it is completely stable, which is what leads me to think that the failure is Roon-related.

When I review the logs I see two worrying things: Roon trying to reprocess the same files over and over again; Roon using more and more VM (up to: 01/10 07:10:19 Info: [stats] 9067mb Virtual, 3658mb Physical, 1381mb Managed, 2990 Handles, 88 Threads). But again there is no obvious error, either in Roon or event viewer. Can you help? Obviously I will upload whatever logs are helpful.

Aidan

What if you removed those files from the watched storage directory?

Run MemTest86 for no less than 24 hours:

Thanks @wklie I will give that a try over the weekend, although I should add that since my last post on this topic the NUC has been running fine without Roon - it fails only when Roon is running.

@rugby you asked if I could just remove the files that get rescanned from my library. I could do that but I wonder if it might not be simpler just to recreate my library from scratch. While I have been investigating this issue I have moved my Roon install to my mac desktop (which has 64gb of memory so more than enough…) and rebuilt the library from scratch and that also has been very stable.

My plan of attack therefore is to 1 run memtest and if no errors then 2 rebuild the library from scratch on the NUC. Unless that is anyone has a better suggestion.

Hi @Aidan_Gaule ,

I’ve moved your post to the #support section, please be aware that to receive technical support, you must post to this section.

Can you please reproduce the issue and upload a set of your Roon logs (you can use these instructions to access them) to our Logs Uploader for review?

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

Please let me know once uploaded, thanks!

Thanks @noris. I have moved my Roon core to a different machine while I conducted some other testing so I will need to move it back and will send logs when/if it crashes.

@wklie Peter, I ran the memory checker you suggested for 16 hours (4 batches of 4 hours on the free version) and no errors were reported.

1 Like

@noris roon crashed about 10 minutes ago. I have uploaded the logs as requested.

Where is the Roon Core running from when it crashed? The original i7 NUC or “the different machine”?

How do you know it actually crashed, or just dropped off from the network? A few posts above you said “hung”, which is different from a crash. When a PC hangs, the screen freezes and the mouse cursor cannot move. When it crashes, it shows an error dialog or a blue screen of death if you disabled Windows reboot on crash.

A while ago it was proven Home Hub 4 could not support Roon. The solution was to change to a Smart Hub 2. However, if you Roon Core really crashed, then it’s not caused by the router.

Hello Peter

Thanks for your reply and your continued interest in my problems.

To respond to your questions…

Where is the Roon Core running from when it crashed? The original i7 NUC or “the different machine”?

the NUC

How do you know it actually crashed, or just dropped off from the network? A few posts above you said “hung”, which is different from a crash. When a PC hangs, the screen freezes and the mouse cursor cannot move. When it crashes, it shows an error dialog or a blue screen of death if you disabled Windows reboot on crash.

I run the NUC ‘headless’ so it is difficult to know if it is hanging or crashing. When this happens, the NUC becomes inaccessible from the network and the fan goes haywire. When I restart the machine, there is nothing in Event Viewer to tell me what happened, other than a message that I restarted the machine after an improper system shutdown. So probably hanging…

A while ago it was proven Home Hub 4 could not support Roon. The solution was to change to a Smart Hub 2. However, if you Roon Core really crashed, then it’s not caused by the router.

Apologies for my inaccuracy - I have a smart hub 2, not a home hub 2.