Roon crashing ntdll.dll

Support
1

Core Machine (Operating system/System info/Roon build number)
Windows 10/x570 aorus I WiFi, 16gb ram, amd 3700x, m.2 SSD system, mirrored raid data disk

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Ubiquity USG pro 4 firewall/router, ubiquity 24 port Poe gigabit switch. Core software on windows 10, clients are blue sound power mode & pi/Allo Digi hat to arcam amp

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Pi with Allo Digi hat connected to arcam amp

Description of issue
Roon crashes, typically when not in use. I normally realise when I can’t connect some time later and connect to win 10 machine to restart roon. Error in Windows application log. Previously completely stable - problems only started on new pc, install of Windows 10 with new processor/motherboard. However all other software (Plex, heaven benchmark/stress test, etc working fine without issues).

Log Name:      Application
Source:        Application Error
Date:          18/08/2019 02:58:00
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DAIRY
Description:
Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x5cc12f39
Faulting module name: ntdll.dll, version: 10.0.18362.267, time stamp: 0xc00f8a30
Exception code: 0xc0000374
Fault offset: 0x00000000000f9269
Faulting process ID: 0x3084
Faulting application start time: 0x01d5550bffc1c177
Faulting application path: C:\Users\piranadmin\AppData\Local\Roon\Application\Roon.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report ID: 01d17542-f9bd-47e6-b4a4-aeb76bb97305
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>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-08-18T01:58:00.417370500Z" />
    <EventRecordID>4936</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DAIRY</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Roon.exe</Data>
    <Data>1.0.0.0</Data>
    <Data>5cc12f39</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.18362.267</Data>
    <Data>c00f8a30</Data>
    <Data>c0000374</Data>
    <Data>00000000000f9269</Data>
    <Data>3084</Data>
    <Data>01d5550bffc1c177</Data>
    <Data>C:\Users\piranadmin\AppData\Local\Roon\Application\Roon.exe</Data>
    <Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
    <Data>01d17542-f9bd-47e6-b4a4-aeb76bb97305</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>
1 Like
2

Hi @danielpugh,

How often does this type of behavior occur? Are you seeing this once a day, every few hours, more frequently than that?

Is there any patterns you’ve noticed in when this happens? Is the same screen always left up in Roon prior to a crash or anything like that?

4

Hi,

It crashes roughly every two days at a guess.
Roon launches on the pc (launched via TeamViewer and left) and i don’t touch it (I use android to control from my phone)…

Hope that helps - bit of a mystery

5

Hi @danielpugh,

The next time this happens can you make a note of the time the crash occurs (or at least the time you notice it)? We’d like to enable some diagnostics on your out, and having a timestamp to refer to will help the team better understand what’s occurring.

Thanks!

6

Of course - will post here when it crashes again

1 Like
7

ProcDump is helpful in creating dump files of crashed applications. Once an application crashes ProcDump creates a .dmp file in the configured directory. A crash dump is very helpful during analysis. You should send it to support. From the above link, in order to configure it, open a command prompt as administrator and enter:

Register as the Just-in-Time (AeDebug) debugger. Makes full dumps in c:\dumps.
C:>procdump -ma -i c:\dumps

8

Hi,

Not forgotten, but have been too busy to sort out procdump. Suspect upcoming Radeon x570 firmware update may help, so waiting to see if that helps first.

Dan

9

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