.Net-related Roon app crash

Robert_Lowe · January 17, 2021, 10:30pm

Core Machine (Operating system/System info/Roon build number)
CyberPowerPC Ryzen Threadripper Windows 10 Pro 20H2, 64 G

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Intel I211 GB Ethernet adapter, 2 ports teamed with wireline connection to Asus RT-AX88U router

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

Description Of Issue
The Roon app is crashing (while idle) because of a .NET-related error; this has happened twice in the past four days:

Log Name:      Application
Source:        Application Error
Date:          1/17/2021 13:44:56
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EvolvX
Description:
Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x5fd7dd5f
Faulting module name: clr.dll, version: 4.8.4300.0, time stamp: 0x5f7e616e
Exception code: 0xc0000005
Fault offset: 0x00000000001e772a
Faulting process id: 0x35f0
Faulting application start time: 0x01d6e9edb22e663a
Faulting application path: C:\Users\RLowe\AppData\Local\Roon\Application\Roon.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 00060e28-a84f-41b6-822d-53fc29ec95b5
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-01-17T21:44:56.3822888Z" />
    <EventRecordID>13852</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>EvolvX</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Roon.exe</Data>
    <Data>1.0.0.0</Data>
    <Data>5fd7dd5f</Data>
    <Data>clr.dll</Data>
    <Data>4.8.4300.0</Data>
    <Data>5f7e616e</Data>
    <Data>c0000005</Data>
    <Data>00000000001e772a</Data>
    <Data>35f0</Data>
    <Data>01d6e9edb22e663a</Data>
    <Data>C:\Users\RLowe\AppData\Local\Roon\Application\Roon.exe</Data>
    <Data>C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll</Data>
    <Data>00060e28-a84f-41b6-822d-53fc29ec95b5</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>
Log Name:      Application
Source:        .NET Runtime
Date:          1/17/2021 13:44:55
Event ID:      1023
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EvolvX
Description:
Application: Roon.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFABF50772A (00007FFABF320000) with exit code 80131506.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1023</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-01-17T21:44:55.4712572Z" />
    <EventRecordID>13851</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>EvolvX</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Application: Roon.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFABF50772A (00007FFABF320000) with exit code 80131506.
</Data>
  </EventData>
</Event>
Log Name:      Application
Source:        Application Error
Date:          1/13/2021 10:00:19
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EvolvX
Description:
Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x5fd7dd5f
Faulting module name: clr.dll, version: 4.8.4300.0, time stamp: 0x5f7e616e
Exception code: 0xc0000005
Fault offset: 0x000000000006f054
Faulting process id: 0x1cbc
Faulting application start time: 0x01d6e79e0e48cafa
Faulting application path: C:\Users\RLowe\AppData\Local\Roon\Application\Roon.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 95f56432-1ab2-4634-81b5-1014775cd4f9
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-01-13T18:00:19.7679722Z" />
    <EventRecordID>13453</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>EvolvX</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Roon.exe</Data>
    <Data>1.0.0.0</Data>
    <Data>5fd7dd5f</Data>
    <Data>clr.dll</Data>
    <Data>4.8.4300.0</Data>
    <Data>5f7e616e</Data>
    <Data>c0000005</Data>
    <Data>000000000006f054</Data>
    <Data>1cbc</Data>
    <Data>01d6e79e0e48cafa</Data>
    <Data>C:\Users\RLowe\AppData\Local\Roon\Application\Roon.exe</Data>
    <Data>C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll</Data>
    <Data>95f56432-1ab2-4634-81b5-1014775cd4f9</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>
Log Name:      Application
Source:        .NET Runtime
Date:          1/13/2021 10:00:19
Event ID:      1023
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EvolvX
Description:
Application: Roon.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFABF38F054 (00007FFABF320000) with exit code 80131506.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1023</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-01-13T18:00:19.1245928Z" />
    <EventRecordID>13452</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>EvolvX</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Application: Roon.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFABF38F054 (00007FFABF320000) with exit code 80131506.
</Data>
  </EventData>
</Event>

Any suggestions? I found a nearly identical error report posted here in 2016, but there appeared to be no resolution or definitive diagnosis offered and earlier versions of the .NET framework were implicated.

Mike_O_Neill · January 18, 2021, 6:00am

Are your device drivers up to date ?

This often causes issues after a Win 10 update

I use intel integrated graphics and sound and updated without issues

Also, std advice have you rebooted Everything , network gear included

I’ll flag @support they can help …

Robert_Lowe · January 18, 2021, 6:14am

Hi @Mike_O_Neill Yes, the PC has been rebooted. The app has since crashed again, this time implicating another part of the OS (ntdll.dll):

Log Name: Application
Source: Application Error
Date: 1/17/2021 21:51:32
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: EvolvX
Description:
Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x5fd7dd5f
Faulting module name: ntdll.dll, version: 10.0.19041.662, time stamp: 0x27bfa5f0
Exception code: 0xc0000374
Fault offset: 0x00000000000ff0f9
Faulting process id: 0x2588
Faulting application start time: 0x01d6ed3810037378
Faulting application path: C:\Users\RLowe\AppData\Local\Roon\Application\Roon.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 14d1862b-f6cc-4c6e-ab6d-a7e01f544a4f
Faulting package full name:
Faulting package-relative application ID:
Event Xml:

1000
0
2
100
0
0x80000000000000

13963

Application
EvolvX

Roon.exe
1.0.0.0
5fd7dd5f
ntdll.dll
10.0.19041.662
27bfa5f0
c0000374
00000000000ff0f9
2588
01d6ed3810037378
C:\Users\RLowe\AppData\Local\Roon\Application\Roon.exe
C:\Windows\SYSTEM32\ntdll.dll
14d1862b-f6cc-4c6e-ab6d-a7e01f544a4f

This follows the application earlier today of this month’s Windows 10 20H2 cumulative update. Everything else on the machine is as current as it can be.

Robert_Lowe · January 18, 2021, 9:20am

Robert_Lowe · January 18, 2021, 9:30am

A restart seems to have helped for the moment, but some @support input would be welcome.

wizardofoz · January 18, 2021, 10:30am

Im not 100% sure a “teamed” assume that’s a bonded pair of ethernet ports is perhaps something to remove while troubleshooting this.

That said, when did this start?

Mike_O_Neill · January 18, 2021, 12:24pm

My friend Google came up with this …

Maybe an uninstall of Roon leaving the db in place then reboot , download a fresh copy of Roon

That Ntdll seems pretty fundamental to Windows.

I am not that expert alas

Robert_Lowe · January 18, 2021, 10:05pm

Hi @wizardofoz, the Intel ethernet adapter has two 1GB ports. You can team these through the OS to act as a “single” port with greater potential throughput. This has been configured for some time, is a function integrated into the OS, and it’s difficult to see how it would have any impact on Roon’s stability or affect failures in .NET or other OS code. The issue became manifest initially on January 13 when the Roon application first failed as reported in the logging I initially posted. There were no corresponding software or hardware configuration changes that were contemporary with that event. @Mike_O_Neill, I did some Googling as well around ntdll and at this point am reluctant to start ripping things out until I hear from Support on this. The Roon installation itself is barely a month old because I had to completely remove the application and database as a result of an unrecoverable Roon database failure in early December. So it seems odd to me that a relatively fresh install and database would suddenly need yet another do-over.

wizardofoz · January 19, 2021, 3:28am

I recall having issues with something when bound ports used on my Synology - Im a network installer I know how its supposed to work Just trying to suggest removing something that is rather a niche environment for 99.9% of normal use case.

Mike_O_Neill · January 19, 2021, 4:07am

The early Jan Windows update caused me some issues, my wife’s PC lost sound. That’s Realtek integration in the MB , had to reload drivers

Some funnies maybe ?

noris · January 19, 2021, 4:26pm

Hi @Robert_Lowe,

Can you please use these instructions to send me a set of your Roon logs for review?

Robert_Lowe · January 19, 2021, 8:25pm

Hi @noris Please see the logs here: https://www.dropbox.com/s/ym5jczlvl8yrxbq/Robert_Lowe_Roon_logs.zip?dl=0 let me know if there’s an access problem. Thanks.

noris · February 3, 2021, 1:06am

Hi @Robert_Lowe,

Thanks again for sending logs and for your patience here. I spoke to the team regarding the logs, but they were not able to pinpoint why the issue occurred. Can you please confirm, if you try to set up a fresh Roon database, does the issue still occur? I have provided instructions on how to setup a fresh database below:

Make a Backup of your current Roon Database
Exit out of Roon
Navigate to your Roon’s Database Location
Find the folder that says “Roon”
Rename the “Roon” folder to “Roon_old”
Reinstall the Roon App from our Downloads Page to generate a new Roon folder

Robert_Lowe · February 3, 2021, 4:08am

Hi @noris Thanks. It’s a little disappointing that your developers don’t have more insight to offer than “well, try ripping it out and starting over.” Fortunately, I haven’t had a recurrence of the issue since I initially reported it, for which fact I now guess I’m luckier than I knew since there seem to be limited troubleshooting options available for this situation. I hope that the next release of Roon, which your team is actively promoting, has as much to offer in the way of improved performance, stability and reliability as it does in more trendy fonts and layouts of metadata.

noris · February 5, 2021, 7:14pm

Hi @Robert_Lowe,

Thanks for letting me know the issue went away! The test with the fresh database would have allowed us to confirm if this issue was database-related of if a fresh database also reproduced the issue and if it was hardware-related instead. Since the issue hasn’t occurred, I will go ahead and close out this case, but if the behavior returns please just let us know and we can pick this back up, thanks!

system · February 7, 2021, 7:14am

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