Roon keeps freezing and crashing on Windows (mostly when resuming from minimized) [Solved After Roon Build 1302]

Support
217

Hi @Darren_Gee,

I hope you don’t mind, but we’ve moved your post over to this thread so we can troubleshoot the issue you’re experiencing in a dedicated topic. Your issue doesn’t appear to be connected to the memory leak regressions which were solved with Build 970, so we’ll need to gather a few more details before proceeding.

The team will pull some diagnostic reports from your account to investigate, but if you don’t mind, can you please first provide an approximate date/timestamp for when the crash recently occurred?

This will help us pinpoint the issue most efficiently.

218

Same here. Any window switching or moving = instant crash. Let me know if you need anything to help pinpoint:)

219

Please open a new Support request giving full details of your setup. Then Support will be able to pull diagnostic reports. As @connor wrote above, please also provide an approximate date/timestamp for when the crash recently occurred. Thanks.

1 Like
220

Roon Core Machine

Win 11 ryzen 5600x 16gb mem

Networking Gear & Setup Details

Wired network from my Talk talk router, to lyksys unmanaged switch to sonore opirendu roon.

Connected Audio Devices

Optiprendu to denifhips venus 2 dac . to kinky studio amp.

Number of Tracks in Library

I have less that 30 in library, I use Tidal

Description of Issue

Every time I leave roon and use another app roon crashes intermittently, when I come back to roon and click on roon screen. sometimes it recovered, but most of time crashed without any error. I have to reopen. Sometimes leave music playing and roon closes I never had this issue until a couple of week ago after update. Latest versions on roon installed. Crashed 18.30 today. I have created a log file and zipped. named zip darren_gee uplaoded to you already.

221

Are you running build 970 on your core and control devices? If not install the updates & reboot all devices including the router.
If you have installed “970” then go through the reboot of your devices & router, hopefully that will fix everything.

222

Hi @Nelson_Parker,

If you can also let us know the approximate date/time when you next encounter the issue, that will greatly augment our troubleshooting efficiency as we pull logs on the backend to investigate. We’ll follow up here to troubleshoot your issue until we can determine if it’s unrelated to what @Darren_Gee is experiencing.

223

I raised a ticket Also uploaded log. details in ticket Roon Crashing on core. windows 11 - Support - Roon Labs Community

1 Like
225

Something I noticed. The crashing for me occurs when using Microsoft Edge. I downloaded Google Chrome and it seems to have stopped…

226

Right now I have Roon 970 running, Discord, multiple windows in Chrome open including Youtube, V-Rising running and Steam going. Zero crashes and I’m trying to crash it lol.

227

Been experiencing these crashes for a few months, Crashes when Roon has been minimised for a while. I have Build 970 and still having the same issue.
I’m using Google chrome, so t’s not a browser issue, edge or chrome etc,.
I think it’s when the hard drive goes to sleep, then spins back up Roon crashes when maximising after using other programs. It’s very random.

228

The energy-saving features can be configured individually for all operating systems, and there are certainly advantageous and disadvantageous settings for the smooth operation of Roon.

This explains why primarily the remote controls are affected.

I think the Roon team comes to a recommendation after some analyzed cases, what is better not to set. Good to put in the FAQ.

Minimizing seems to be not yet without problems in Windows 10/11. But short freezing for seconds is better to handle than crashes observed with old releases. The individual settings mean for the Roon team to always take a close look under which hard- and software configurations problems occur more often.

229

It’s nothing to do with windows or energy-saving configuration. no other program has these issues.
It’s been reported by many people that Roon crashes after minimising.
I’ve been a Roon user for 8 years, I’ve had no problems previously.

1 Like
230

I also had much less problems with Windows XP and Windows 7, with enthusiasm I jumped to Windows 8 and had to limp. Now I use Windows 10/11 in dualboot and have even more problems. The Apple world has not become more stable when Steve Jobs left us.

Roon had to struggle with Mono, now dotnet is the order of the day, but not in your own hand…

Old graphics drivers fail after an update, new ones don’t work completely right either. Not everything can be dumped on the Roon team that can go wrong with the system. There are also individual settings of the user that can stand in the way. But the team should support in each individual case.

actual example:

231

This appears to be the same problem as in the pinned thread:

Roon keeps freezing and crashing on Windows (mostly when resuming from minimized)

234

Crashed today6/29/2022 around 3PM EST

235

Hi everyone,

Thank you for your patience with this issue. We appreciate the detailed reports you’ve provided so far.

Summary: Users running Build 970 are experiencing hanging, freezing, and inconsistent poor performance on Windows devices. So far, this has been reported mostly in setups with a Windows Core device, but the issue has also manifested in setups with RoonOS and Linux Cores. Minimizing/maximizing and certain scrolling patterns so far seem to trigger the behavior.

While reports of this issue overlapped with a known memory leak that we resolved with Build 970, the diagnostics so far show no indication this is a related issue.

Next steps: The team is actively tracking these reports and gathering diagnostics from reporting users to isolate variables and pin down the problem.

We will provide status updates in this topic thread. If you experience a crash, please post a general timestamp here; the more precise, the better equipped our tech support will be to investigate.

Thank you!

2 Likes
236

I have had numerous freezes over the past few days but no crashes.
In case it is not known, the freezes do not trigger a windows event whereas the crashes do (otherwise i would have reported a timestamp and event)
Additionally, in my experience roon continues to play during both freezes and crashes and both do not allow access to the app (to make changes). A freeze will eventually unfreeze and the app again becomes available to access whereas a crash, closes the app down and reopens (most of the time without interruption of the current song in playback)
Finally, the crashes occur almost all of the time while the background audio analysis is cranking away on analyizing new additions to the library (cpu and memory are much higher during this process). If no audio analysis in progress, the system just freezes

2 Likes
237

Thanks @connor, appreciate you confirming that the team is trying to isolate the problem. Suspected as much, but good to know.

Well, you asked for it! Here are my notes since 970 update, which include the last few lines from Roon logs. You’ll notice many crashes immediately after 970 update, then a few days clear after logging out of Tidal/Qobuz. I had also done this (logged out) in the week before 970 and had no crashes, so thought I might be on to something, but then started crashing regularly. Most often occurs for me on waking PC or display. You might notice in Roon logs the line “Debug: render area size changed value: 2560x1369” comes up a few times. Note that I rarely get freezes only, almost always I get a crash.

Date Time Event RAM usage Max/Min
14/06/2022 22:27 CORE CRASH: After playlist finished playing on end point – shortly afterwards Unknown Unknown
15/06/2022 13:47 CORE CRASH: After stopping playlist on end point – maybe 30mins later? igccservice information event immediately before (20secs) Unknown Unknown
15/06/2022 16:09 CORE CRASH: Not using Roon. Had just finished some admin in MS Edge ( perhaps on finishing the focus went to Roon?) Unknown Unknown
16/06/2022 1:29 CORE CRASH: Not using Roon. 2+ hours after paying album to end point. igccservice information event immediately before (30secs) Unknown Unknown
16/06/2022 11:00 Logged out of Tidal and Qobuz, closed Roon Core, rebooted wireless router, rebooted PC
17/06/2022 12:00 Updated Intel graphics driver, reboot
20/6/2022 11:33 CORE CRASH: PC already awake, turned on display, no Windows lock screen (usually is), appears to have been an immediate memory increase to about 3gb and then Roon crash. Faulting module name: System.Core.ni.dll, version: 4.8.4515.0, time stamp: 0x624cf626 From Roon logs: 06/20 11:32:18 Debug: GMS: saving nav stack 06/20 11:32:18 Debug: GMS: trying to save nav stack, but nav stack stuff was in progress 06/20 11:32:18 Debug: GMS: trying to save nav stack, but nav stack stuff was in progress Immediate jump from ~2gb to ~3gb No change, display turned on
21/6/2022 13:17 CORE CRASH: Switching to Roon, already maximised, after using MS Edge, MS PPT, MS Outlook. Had played album to system output, ended maybe 30mins prior, on album screen Faulting module name: clr.dll, version: 4.8.4515.0, time stamp: 0x624ce98e From Roon logs: 06/21 13:17:00 Debug: render area size changed value: 2560x1369 06/21 13:17:00 Debug: GMS: saving nav stack 06/21 13:17:00 Debug: unhandled selection type: ~2gb commit, slight uptick on crash Max, on giving focus
22/06/2022 11:07 CORE CRASH: PC already awake, turned on display; 3 errors in Event Viewer: Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at System.Runtime.InteropServices.Marshal.ReadInt32(IntPtr, Int32) at Roon.WindowsDriveDetector.WndProc(System.Windows.Forms.Message ByRef) at WinUtils.WindowHelper+WndProcDelegate.Invoke(System.Windows.Forms.Message ByRef) at WinUtils.WindowHelper+<>c.<_HookWindow>b__18_0(IntPtr, Int32, Int32, Int32) Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af Faulting module name: mscorlib.ni.dll, version: 4.8.4515.0, time stamp: 0x624ce856 Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af Faulting module name: KERNELBASE.dll, version: 10.0.22000.708, time stamp: 0x89f799f7 From Roon log: 06/22 11:07:25 Trace: GetImageData[Remote](id=248011 spec=256 key=xwcoaaaa) => got from cache overalltime=0ms 06/22 11:07:25 Trace: GetImageData[Remote](id=248011 spec=256 key=xwcoaaaa) => got from cache overalltime=0ms 06/22 11:07:25 Debug: [easyhttp] [2882] GET to http://127.0.0.1:9300/image/xwcoaaaa.256.jpg returned after 3 ms, status code: 200 06/22 11:07:25 Trace: [broo/images] caching http://127.0.0.1:9300/image/xwcoaaaa.256.jpg etag=b367303bb2c427d04bb8cf659e428317d808dddd expiration=23/06/2022 12:22:12 PM 06/22 11:07:29 Trace: [volumewatcher] ev_VolumeChanged DidMount: I:\ 06/22 11:07:29 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at I:\ 06/22 11:07:30 Trace: [rnet/RnetJsonClient] GOT NONFINAL {“status”: “DeviceAdded”, “device”: {“device_id”: “{0.0.0.00000000}.{396465b0-0bde-46f4-83af-1d67cabc842f}”, “type”: “wasapi”, “name”: “Intel(R) Display Audio”}} 06/22 11:07:30 Info: [raatserver] GOT DEVICE c04785ef-8076-4d9a-9d99-3f67a670d331::{0.0.0.00000000}.{396465b0-0bde-46f4-83af-1d67cabc842f} Type=wasapi Name=Intel(R) Display Audio 06/22 11:07:32 Info: [stats] 6783mb Virtual, 996mb Physical, 584mb Managed, 2446 Handles, 135 Threads ~2gb commit, slight uptick on crash Was minimised, appeared crash initiated on maximising
22/06/2022 11:16 Ran C:\WINDOWS\system32>sfc /scannow Windows Resource Protection found corrupt files and successfully repaired them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offlinerepairs, details are included in the log file provided by the /OFFLOGFILE flag.
22/06/2022 11:38 Reboot PC
22/06/2022 13:32 CORE CRASH: PC not being used, still on; maybe when display timed off after 15mins? Application: Roon.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at System.Runtime.InteropServices.Marshal.ReadInt32(IntPtr, Int32) at Roon.WindowsDriveDetector.WndProc(System.Windows.Forms.Message ByRef) at WinUtils.WindowHelper+<>c.<_HookWindow>b__18_0(IntPtr, Int32, Int32, Int32) Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af Faulting module name: mscorlib.ni.dll, version: 4.8.4515.0, time stamp: 0x624ce856 Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af Faulting module name: KERNELBASE.dll, version: 10.0.22000.708, time stamp: 0x89f799f7 From Roon log: 06/22 13:31:18 Trace: [upnp/discovery] device expired: uuid:9a7b9cb1-71eb-4104-a893-0c429a04f5de 06/22 13:31:31 Info: [stats] 6793mb Virtual, 717mb Physical, 508mb Managed, 2413 Handles, 126 Threads 06/22 13:31:46 Info: [stats] 6801mb Virtual, 718mb Physical, 505mb Managed, 2397 Handles, 128 Threads 06/22 13:32:34 Info: [stats] 6789mb Virtual, 730mb Physical, 508mb Managed, 2405 Handles, 125 Threads Unknown Minimised
22/06/2022 17:22 CORE CRASH: After general PC use, brought focus to Roon, on home screen, hang for ~10secs then crash. Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af Faulting module name: System.Core.ni.dll, version: 4.8.4515.0, time stamp: 0x624cf626 From Roon log: 06/22 17:21:53 Debug: render area size changed value: 1528x833 06/22 17:21:53 Debug: unhandled selection type: 06/22 17:21:53 Trace: GetImageData[Remote](id=35831 spec=1by1_512 key=dabcaaaa) => got from cache overalltime=1ms 06/22 17:21:53 Trace: GetImageData[Remote](id=35831 spec=1by1_512 key=dabcaaaa) => got from cache overalltime=2ms06/22 17:21:53 Debug: [easyhttp] [251] GET to http://127.0.0.1:9300/image/dabcaaaa.1by1_512.jpg returned after 44 ms, status code: 200 06/22 17:21:53 Trace: [broo/images] caching http://127.0.0.1:9300/image/dabcaaaa.1by1_512.jpg etag=592d0626388a4b4d8329fc86800768b07acb20a9 expiration=23/06/2022 4:53:18 AM ~2gb commit, slight uptick on crash
24/06/2022 16:31 CORE CRASH: PC not being used, still on, crashed when waking up display Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af Faulting module name: clr.dll, version: 4.8.4515.0, time stamp: 0x624ce98e From Roon log: 06/24 16:30:50 Info: [stats] 7795mb Virtual, 863mb Physical, 587mb Managed, 2977 Handles, 173 Threads 06/24 16:30:59 Debug: GMS: saving nav stack Minimised
26/06/2022 13:09 CORE CRASH: PC not being used, still on, crashed when waking up display/PC Application: Roon.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at System.Runtime.InteropServices.Marshal.ReadInt32(IntPtr, Int32) at Roon.WindowsDriveDetector.WndProc(System.Windows.Forms.Message ByRef) at WinUtils.WindowHelper+<>c.<_HookWindow>b__18_0(IntPtr, Int32, Int32, Int32) Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af Faulting module name: mscorlib.ni.dll, version: 4.8.4515.0, time stamp: 0x624ce856 From Roon log: 06/26 13:09:19 Info: [stats] 6930mb Virtual, 811mb Physical, 532mb Managed, 2532 Handles, 125 Threads 06/26 13:09:22 Debug: render area size changed value: 2560x1369 06/26 13:09:22 Debug: unhandled selection type: 06/26 13:09:26 Trace: [rnet/RnetJsonClient] GOT NONFINAL {“status”: “DeviceRemoved”, “device”: {“device_id”: “{0.0.0.00000000}.{396465b0-0bde-46f4-83af-1d67cabc842f}”, “type”: “wasapi”, “name”: “Intel(R) Display Audio”}} 06/26 13:09:27 Info: [transport] about to sleep; disabling transport if needed 06/26 13:09:27 Trace: [transport] disabling transport 06/26 13:09:27 Trace: [zone System Output] Suspend 06/26 13:09:27 Info: [zone System Output] Canceling Pending Sleep 06/26 13:09:27 Info: [zone System Output] Canceling Pending Sleep 06/26 13:09:27 Trace: [zone Lounge] Suspend 06/26 13:09:27 Info: [zone Lounge] Canceling Pending Sleep 06/26 13:09:27 Info: [zone Lounge] Canceling Pending Sleep 06/26 13:09:27 Trace: [raat] disposing 06/26 13:09:27 Trace: [airplay] disposing06/26 13:09:27 Trace: [devialet] disposing 06/26 13:09:27 Trace: [devicemanager/sonos] disposing06/26 13:09:27 Trace: [devicemanager/kef] disposing 06/26 13:09:27 Trace: [hqplayer] disposing06/26 13:09:27 Trace: [meridian] disposing Unknown Unknown
26/06/2022 15:47 CORE CRASH Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af Faulting module name: KERNELBASE.dll, version: 10.0.22000.708, time stamp: 0x89f799f7 From Roon log: 06/26 15:47:39 Trace: [client/roonbridges] woke from sleep, sending discovery query 06/26 15:47:39 Trace: [roonbridge] [sood] Refreshing device list 06/26 15:47:39 Info: [stats] 6909mb Virtual, 799mb Physical, 531mb Managed, 2377 Handles, 112 Threads 06/26 15:47:39 Trace: [push2] exception thrown. restarting connection (An internal WebSocket error occurred. Please see the innerException, if present, for more details. ) 06/26 15:47:39 Trace: [push2] retrying connection in 81009ms 06/26 15:47:39 Error: [cast/client] [TDAI-1120- 0c88d7c04c3a632015aacd49e583cb38._googlecast._tcp.local] Exception writing message to stream: Unknown Unknown
27/06/2022 13:33 CORE CRASH: PC not being used, still on, crashed when waking up display/PC Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af Faulting module name: clr.dll, version: 4.8.4515.0, time stamp: 0x624ce98e From Roon log: 06/27 13:33:44 Info: [stats] 7308mb Virtual, 787mb Physical, 515mb Managed, 2581 Handles, 145 Threads 06/27 13:33:47 Debug: render area size changed value: 2560x1369 06/27 13:33:47 Trace: [library] finished with 1 dirty performers 1 dirty places 0 clumping tracks, 0 clumping auxfiles 0 compute tracks, 0 deleted tracks, 0 tracks to (re)load, 0 tracks to retain, 0 auxfiles to (re)load, 0 auxfiles to retain, and 1 changed objects06/27 13:33:47 Debug: unhandled selection type: Unknown Unknown
28/06/2022 12:58 CORE CRASH: PC not being used, still on, crashed when waking up PC Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af Faulting module name: clr.dll, version: 4.8.4515.0, time stamp: 0x624ce98e From Roon log: 06/28 12:57:56 Info: [stats] 6632mb Virtual, 1043mb Physical, 500mb Managed, 2529 Handles, 119 Threads 06/28 12:58:11 Debug: render area size changed value: 2560x1369 06/28 12:58:11 Debug: GMS: saving nav stack06/28 12:58:11 Debug: unhandled selection type: Unknown Unknown
29/06/2022 11:07 CORE CRASH: PC not being used, still on, crashed when waking up PC Application: Roon.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at System.Runtime.InteropServices.Marshal.ReadInt32(IntPtr, Int32) at Roon.WindowsDriveDetector.WndProc(System.Windows.Forms.Message ByRef) at WinUtils.WindowHelper+WndProcDelegate.Invoke(System.Windows.Forms.Message ByRef) at WinUtils.WindowHelper+<>c.<_HookWindow>b__18_0(IntPtr, Int32, Int32, Int32) Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af Faulting module name: mscorlib.ni.dll, version: 4.8.4515.0, time stamp: 0x624ce856 Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af Faulting module name: KERNELBASE.dll, version: 10.0.22000.778, time stamp: 0x5f5438c2 Unknown Unknown
2 Likes
238

@connor
App just crashed, nothing playing, just open

Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af
Faulting module name: System.Core.ni.dll, version: 4.8.4515.0, time stamp: 0x624cf626
Exception code: 0xc00000fd
Fault offset: 0x00000000003444c7
Faulting process id: 0x3b88
Faulting application start time: 0x01d88c72f7760525
Faulting application path: C:\Users\chuck\AppData\Local\Roon\Application\Roon.exe
Faulting module path: C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Core\5a9aa981acfc11a81b346d71a68d228c\System.Core.ni.dll
Report Id: 92700439-e23d-4fb4-b00c-4c83b64eb4ff
Faulting package full name:
Faulting package-relative application ID:

1 Like
239

Another freeze and then crash. This time playing from a playlist.

Faulting application name: Roon.exe, version: 1.0.0.0, time stamp: 0x62a332af
Faulting module name: System.Core.ni.dll, version: 4.8.4515.0, time stamp: 0x624cf626