Roon Core Crashes on Windows 10 few mins after Launch

Roon Core Machine

Windows 10 Enterprise 10.0.19045 Build 19045
CPU: AMD Ryzen 3950x 16-Core
RAM: 32 GB

Networking Gear & Setup Details

Ethernet: 10 GB Intel X550-T2
Router: Asus RX88U
Swtich; Netgear GS110

Connected Audio Devices

UltraRendu

Number of Tracks in Library

Tracks: 503,476

Description of Issue

Roon Core crashes few mins after it starts. This started happening after the recent update Ver 2.0 (Build 1277). It was working stable a month ago.
I have tried following in this order

  • Restore Database from March 2023
  • Reinstall Roon after renaming existing Roon to Roon_Old.
  • I’ve check Skipped files in Library and removed those files before doing the above setups
    None of these has worked.
    I had similar problem few years ago and the issue turned out to Roon was unable to scan metadata on one of tracks and was crashing. This took many weeks to resolve it as I had to isolate the issue.
    I’ve not added any significant tracks in the library after that.
    I don’t have time and patience to do this exercise again.

I believe this time is also something to do with Roon unable to get metadata for some file in my library.
I’m include both Event View and Roon logs to review to check if that will help resolve it.

The Files has been uploaded using Roon File Uploader

Thanks,
Arshad

1 Like

Here is the Old thread from 2020 that I was referring to that had the same issue.

In the end it turn out to be an error caused by Roon when processing certain metadata.

I took 6 months to resolve it and I hope I don’t have to wait that long to resolve this time.

Have been waiting on the issue for the past few days.
Can someone from Support at least acknowledge the issue?

1 Like

Support can you please let me know what am I missing here to get this issue looked at?

1 Like

I disabled Roon Arc by assigning Port 0 and Roon did not crash for 2 days but then crashed again
Still Crash…

Here is the Error in Event Viewer
Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x641cef7e
Faulting module name: ntdll.dll, version: 10.0.19041.3086, time stamp: 0x6349a4f2
Exception code: 0xc00000fd
Fault offset: 0x000000000002aa2c
Faulting process id: 0x368c
Faulting application start time: 0x01d9a9c6a067febd
Faulting application path: C:\Users\OfficePC\AppData\Local\Roon\Application\Roon.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 8765a0f8-3d28-4955-ad22-3c1eb2b8b259
Faulting package full name:
Faulting package-relative application ID:

This was the error from 3 days ago
Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x641cef7e
Faulting module name: RPCRT4.dll, version: 10.0.19041.2965, time stamp: 0x2261afdc
Exception code: 0xc00000fd
Fault offset: 0x000000000005c0d3
Faulting process id: 0x6498
Faulting application start time: 0x01d9a8ab9bd1afdd
Faulting application path: C:\Users\OfficePC\AppData\Local\Roon\Application\Roon.exe
Faulting module path: C:\WINDOWS\System32\RPCRT4.dll
Report Id: 7e21ea09-2d68-4a10-bbad-e125286b1f20
Faulting package full name:
Faulting package-relative application ID:

Crashed again

Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x641cef7e
Faulting module name: coreclr.dll, version: 6.0.1623.17311, time stamp: 0x641ce9c1
Exception code: 0xc00000fd
Fault offset: 0x000000000016c777
Faulting process id: 0x348c
Faulting application start time: 0x01d9ac4f58d29275
Faulting application path: C:\Users\OfficePC\AppData\Local\Roon\Application\Roon.exe
Faulting module path: C:\Users\OfficePC\AppData\Local\Roon\Application\200001277\coreclr.dll
Report Id: 8ec0bed1-3f60-4d92-adeb-db0cc75fde4c
Faulting package full name:
Faulting package-relative application ID:

1 Like

Now keeps crashing every few hours.

Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x641cef7e
Faulting module name: ntdll.dll, version: 10.0.19041.3086, time stamp: 0x6349a4f2
Exception code: 0xc00000fd
Fault offset: 0x000000000002b866
Faulting process id: 0x78d8
Faulting application start time: 0x01d9ac7ed8a694e3
Faulting application path: C:\Users\OfficePC\AppData\Local\Roon\Application\Roon.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 3f762f06-2e69-4378-9031-54af3675d3cc
Faulting package full name:
Faulting package-relative application ID:

A couple of those Event Viewer reports are referring to Windows components (RPCRT4.dll and ntdll.dll), so there may be something amiss with your Windows installation itself.

Here is the Build Info of Windows 10.
OS Name Microsoft Windows 10 Enterprise
Version 10.0.19045 Build 19045

I’ve all the Windows updates installed. Not sure what you mean by something is missing. Can you please elaborate.
Here are version of Dll’s
ntdll. versioin
image

rpcrt4dll version
image

This started happening after the installing the Roon Verison 2.0 build 1277.

As mentioned I’ve also tried reinstalling Roon after renaming Roon folder and restoring it from backup.
I’ve checked the log files and nothing stands out.
The crashes are random after restoring from backup. Sometimes it happens after after few days and sometime after a day or two.

1 Like

Sorry, English may not be your first language. What I meant by saying “something is amiss” was to say that something may be wrong with your Windows installation. Those components are Windows components, not Roon components.

I’ve the latest Windows 10 22H2 x64 and I did check windows update and everything is up to date.

Other than Roon everything else is working on my Windows PC.
So I think my windows installation is ok.

Only Roon support can tell me if something is working and they have been unresponsive.

1 Like

Crashed again
Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x641cef7e
Faulting module name: ntdll.dll, version: 10.0.19041.3086, time stamp: 0x6349a4f2
Exception code: 0xc00000fd
Fault offset: 0x000000000002b866
Faulting process id: 0x3594
Faulting application start time: 0x01d9acfbfbbb88e9
Faulting application path: C:\Users\OfficePC\AppData\Local\Roon\Application\Roon.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 4fc65866-fd64-417f-a4c1-26e7f7d1ce5e
Faulting package full name:
Faulting package-relative application ID:

1 Like

Same here (Windows 10). Roon launches, streams for less than a minute, then freezes and ultimately crashes and closes.

@Support
It has been 9 days and no one from support has responded.
Not sure what needs to be done to receive support

1 Like

I’m having the same issue. Unbelievable that it remains unaddressed. It’s difficult to believe only 2 of us are having this issue. Makes it an easy decision for me not to renew Roon next month!

I run Windows Enterprise and the size of those two files are different on your installation than mine. Try running a non Windows defender virus scanner.

Can you please check your build# from System Info
Here is mine.
Version 10.0.19045 Build 19045

I’ve ESET Internet Security so no issue with that.

Surprisingly I’ve not seen the crash for past 2 days.
I don’t recall changing anything in my setup and this baffles me.

Crashed again this morning

Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x641cef7e
Faulting module name: coreclr.dll, version: 6.0.1623.17311, time stamp: 0x641ce9c1
Exception code: 0xc00000fd
Fault offset: 0x000000000016c777
Faulting process id: 0x3370
Faulting application start time: 0x01d9ae10c5df9357
Faulting application path: C:\Users\OfficePC\AppData\Local\Roon\Application\Roon.exe
Faulting module path: C:\Users\OfficePC\AppData\Local\Roon\Application\200001277\coreclr.dll
Report Id: 9f23a9ee-3af5-4b26-b805-a6c3f54400ee
Faulting package full name:
Faulting package-relative application ID:

I guess we are running differing systems

Windows 10 Enterprise LTSC
Version 10.0.17763 Build 17763

Refers to a .NET runtime I think. You might try uninstalling/re-installing Roon. And/or updating .NET (uninstall/reinstall).

Over the years, when a crash is unusual, which this is, it points to a software interaction that is causing it. Since you might have been off for the Holidays the
Does the crash occur when you might be running something else on the PC?