LENOVO_MFF_ThinkCentre M900
Windows 10 Pro (10.0.19041)
Intel® Core™ i7-6700T CPU / 16GB RAM
Foobar2000 (No problems)
Roon Version 1.7 (Build 667) stable (64 bit)
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
ASUS RT-AC68U (Connected with WiFi)
QNAP NAS HS-251+ (Music Storage)
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Chord Async USB 44.1kHz-384kHz
Description Of Issue
Hello. First time on the support forum here. Please pardon any amateur mistakes.
I have had this setup running just fine many months now. Then the Roon app* started crashing on Startup around October 20, 2020. It is Crashing after a few minutes of Storage Scanning which is on my Qnap NAS. The PC itself works fine and I can re-open Roon but it will crash again in a few seconds to minutes.
I have done a lot of trial and error with no resolutions. This I have tried are as follows:
(mostly in this order)
NAS: Initially I thought it was my NAS. SO I rebooted it, upgraded F/W and app updates. No change in crashing
Music Files: Looking at the Roon log I found a couple of files which Roon was finding corrupt. I have since removed said files but still no change in condition. Even started with a Fresh DB Rebuild every time.
Lenovo System Updates: I noticed on other articles that it might be the Video Driver needing update. So I proceeded with Lenovo System update to get the driver updates taken care of. There were quite e few to my surprise. Including BIOS. So I did all that. Still no change on Roon crashing.
Display Adapter Settings: I changed the Display > Graphics Settings and set the Roon.exe to use High Performance (GPU Intel® HD Graphics 530. Rebooted. Still No change.
Windows Update (2004). I saw articles where the Windows 10, 2004 update was causing problems with Roon. Unfortunately I was not able to rollback with system restore but I Uninstalled all the recent updates in October 2020 and disabled Windows updates for the time being.
.Net Errors in Event Viewer: Went away after I removed the latest .net update from MS. Still crashing though.
Application: Roon.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 745F98CE (742E0000) with exit code 80131506.
Roon: Needless to say, I have uninstalled and re-installed Roon multiple times in-between. I have even tried the 32 bit version with a fresh database every time. still no change.
Interestingly, if I DISABLE the Storage Scan then Roon stays up no problem. Although that is certainly not the solution. Other apps like Foobar2000 have no problems playing the same audio files and such.
What are the arrangements for cooling on that machine?
Is your music folder split into sub-folders? If it is can you point Roon at those sub folders in turn?
I tried to add the sub-folders one at a time as you had suggested .
Worked good for 7 Folders straight which was encouraging.
Then I added folder #7. It stated syncing a few songs … and then it crashed.
Now Roon crashes within 10 seconds of starting up. After a few tries I was able to speed up to the part where I can Disable the last folder added. Assuming that it might be the cause for this particular “crash loop”. After 8 tries I was able to Disable it. But it still crashes after 10 seconds or so.
I guess I can work thru it again to remove the folders one at a time or simply uninstall and start with new DB. Interestingly no crash reports on Event viewer.
It does look potentially like something in that 7th folder is causing Roon to crash unless it is pure coincidence. Hopefully support will be able to identify the offending file(s).
Thanks for sending those logs over @Robert_Horowitz, I believe I found the file with the issue: M:\MUSIC FILES\BLUES\Chess Blues\100 Sitting Here Alone.m4a
Can you please move this file out of your watched storage locations, restart the Roon app and see if that resolves the issue? If it does, please do not delete the file as it would be useful for QA purposes.
The Forum software spam controls have stopped Robert as a new user repeatedly linking to Google Drive. I have upped Robert to basic user, which may solve the issue.
Noris will let us know if he needs the logs or can see them by enabling diagnostics. If the logs are needed and Robert is still unable to link then it may be possible to PM a link rather than make a public post.
Admins might also consider adding Google Drive as an allowed link for new users.