Windows Server 2022 BSOD - Emby crashing

[oldschool 16]

I believe I'm having problems with Emby - I've had repeated BSOD issues for the last month. I've been troubleshooting hard drives, OS, etc, but when I turn off Emby for a while, I don't get the BSOD. Therefore, I'm guessing the BSOD's are being caused by Emby. Logs attached.

logs.zip

[Happy2Play 9780]

Not much in log except Mark failure for Duck Dynasty - S01E10 - Plan Bee.mkv and some image failures.

Anything in the Event Viewer Emby related?

Might want to look at these potential path issues.  But these are after shutdown request.

2024-06-13 21:27:45.640 Error BaseItem: Error validating children for git 93526 D:\Home\public\Video\Extras\Special Interest\Computers\Beginner Programming and Interview Techniques\Master Lua Programming And Create Amazing Games With Love!\~Get Your Files Here !\7 - Mobile Game Development\libraries\lume\git
	*** Error Report ***
	Version: 4.8.8.0
	Command line: C:\Users\Administrator\AppData\Roaming\Emby-Server\system\EmbyServer.dll
	Operating system: Microsoft Windows 10.0.20348
	Framework: .NET 6.0.30
	OS/Process: x64/x64
	Runtime: C:/Users/Administrator/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll
	Processor count: 8
	Data path: C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata
	Application path: C:\Users\Administrator\AppData\Roaming\Emby-Server\system
	System.ObjectDisposedException: System.ObjectDisposedException: Cannot access a disposed object.
	Object name: 'SqliteItemRepository'.
	   at Emby.Sqlite.BaseSqliteRepository.CheckDisposed()
	   at Emby.Server.Implementations.Data.SqliteItemRepository.GetItemList(InternalItemsQuery query)
	   at Emby.Server.Implementations.Library.LibraryManager.GetItemsResult(InternalItemsQuery query)
	   at MediaBrowser.Controller.Entities.Folder.GetItems(InternalItemsQuery query)
	   at MediaBrowser.Controller.Entities.Folder.GetChildren(InternalItemsQuery query)
	   at MediaBrowser.Controller.Entities.BaseItem.LoadChildren()
	   at MediaBrowser.Controller.Entities.BaseItem.ValidateChildrenInternal(IProgress`1 progress, CancellationToken cancellationToken, Boolean recursive, Boolean refreshChildMetadata, BaseItem[] collectionFolders, LibraryOptions libraryOptions, Dictionary`2 newItemIds, MetadataRefreshOptions refreshOptions, IDirectoryService directoryService)
	   at MediaBrowser.Controller.Entities.BaseItem.ValidateSubFolders(BaseItem[] children, BaseItem[] collectionFolders, LibraryOptions libraryOptions, Dictionary`2 newItemIds, IDirectoryService directoryService, IProgress`1 progress, CancellationToken cancellationToken)
	Source: Emby.Sqlite
	TargetSite: Void CheckDisposed()
	
2024-06-13 21:27:45.641 Error BaseItem: Error validating children for test 93527 D:\Home\public\Video\Extras\Special Interest\Computers\Beginner Programming and Interview Techniques\Master Lua Programming And Create Amazing Games With Love!\~Get Your Files Here !\7 - Mobile Game Development\libraries\lume\test
	*** Error Report ***
	Version: 4.8.8.0
	Command line: C:\Users\Administrator\AppData\Roaming\Emby-Server\system\EmbyServer.dll
	Operating system: Microsoft Windows 10.0.20348
	Framework: .NET 6.0.30
	OS/Process: x64/x64
	Runtime: C:/Users/Administrator/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll
	Processor count: 8
	Data path: C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata
	Application path: C:\Users\Administrator\AppData\Roaming\Emby-Server\system
	System.ObjectDisposedException: System.ObjectDisposedException: Cannot access a disposed object.
	Object name: 'SqliteItemRepository'.
	   at Emby.Sqlite.BaseSqliteRepository.CheckDisposed()
	   at Emby.Server.Implementations.Data.SqliteItemRepository.GetItemList(InternalItemsQuery query)
	   at Emby.Server.Implementations.Library.LibraryManager.GetItemsResult(InternalItemsQuery query)
	   at MediaBrowser.Controller.Entities.Folder.GetItems(InternalItemsQuery query)
	   at MediaBrowser.Controller.Entities.Folder.GetChildren(InternalItemsQuery query)
	   at MediaBrowser.Controller.Entities.BaseItem.LoadChildren()
	   at MediaBrowser.Controller.Entities.BaseItem.ValidateChildrenInternal(IProgress`1 progress, CancellationToken cancellationToken, Boolean recursive, Boolean refreshChildMetadata, BaseItem[] collectionFolders, LibraryOptions libraryOptions, Dictionary`2 newItemIds, MetadataRefreshOptions refreshOptions, IDirectoryService directoryService)
	   at MediaBrowser.Controller.Entities.BaseItem.ValidateSubFolders(BaseItem[] children, BaseItem[] collectionFolders, LibraryOptions libraryOptions, Dictionary`2 newItemIds, IDirectoryService directoryService, IProgress`1 progress, CancellationToken cancellationToken)
	Source: Emby.Sqlite
	TargetSite: Void CheckDisposed()
	
2024-06-13 21:27:45.668 Info SqliteItemRepository: Closing sqlite connection

 

[oldschool 16]

I don't see anything in the event viewer that is Emby-related. I have a ton of Errors with event ID 131 (Metadata staging failed, result=0x80070490 for container '{33BB960C-7B30-4695-8F0F-0C432CCCB849}') and a few warnings (Event ID 1076, 360, and 10016). I don't see anything labeled "Emby" in the event viewer. Is there a folder in there that I can navigate to that has all the events from Emby listed?

[Luke 42078]

Quote

but when I turn off Emby for a while, I don't get the BSOD.

Hi, this doesn't necessarily mean Emby problem, in fact it probably doesn't. It most likely just means that Emby is just tapping into whatever part of your system is causing the blue screen. Usually those point to failing hardware.

[Luke 42078]

But if we're going to go down that path, then i would start by removing these plugins:

2024-06-13 21:07:07.948 Info App: Loading CoverArt, Version=4.1.27.0, Culture=neutral, PublicKeyToken=null from C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata\plugins\CoverArt.dll
2024-06-13 21:07:07.948 Info App: Loading DiskSpace, Version=1.0.6.3, Culture=neutral, PublicKeyToken=null from C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata\plugins\DiskSpace.dll
2024-06-13 21:07:07.948 Info App: Loading Emby.AutoOrganize, Version=1.7.3.0, Culture=neutral, PublicKeyToken=null from C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata\plugins\Emby.AutoOrganize.dll
2024-06-13 21:07:07.948 Info App: Loading Emby.Bulky, Version=1.0.20.0, Culture=neutral, PublicKeyToken=null from C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata\plugins\Emby.Bulky.dll
2024-06-13 21:07:07.948 Info App: Loading Emby.DiagnosticsPlugin, Version=4.8.0.80, Culture=neutral, PublicKeyToken=null from C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata\plugins\Emby.DiagnosticsPlugin.dll
2024-06-13 21:07:07.948 Info App: Loading MovieThemeSongs, Version=1.8.1.0, Culture=neutral, PublicKeyToken=null from C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata\plugins\moviethemesongs.dll
2024-06-13 21:07:07.948 Info App: Loading MovieThemeVideos, Version=1.8.2.0, Culture=neutral, PublicKeyToken=null from C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata\plugins\MovieThemeVideos.dll
2024-06-13 21:07:07.948 Info App: Loading playback_reporting, Version=2.1.0.5, Culture=neutral, PublicKeyToken=null from C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata\plugins\playback_reporting.dll
2024-06-13 21:07:07.948 Info App: Loading statistics, Version=3.3.1.1, Culture=neutral, PublicKeyToken=null from C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata\plugins\Statistics.dll
2024-06-13 21:07:07.948 Info App: Loading MediaBrowser.Plugins.StudioCleaner, Version=3.2.8.0, Culture=neutral, PublicKeyToken=null from C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata\plugins\StudioCleaner.dll
2024-06-13 21:07:07.948 Info App: Loading ThemeSongs, Version=1.8.1.0, Culture=neutral, PublicKeyToken=null from C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata\plugins\themesongs.dll
2024-06-13 21:07:07.948 Info App: Loading ThemeVideos, Version=1.8.1.0, Culture=neutral, PublicKeyToken=null from C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata\plugins\ThemeVideos.dll
2024-06-13 21:07:07.948 Info App: Loading VantagePoint, Version=2.1.0.5, Culture=neutral, PublicKeyToken=null from C:\Users\Administrator\AppData\Roaming\Emby-Server\programdata\plugins\VantagePoint.dll

Then I would disable the following features for all libraries:

• Intro detection
• Video preview thumbnails
• Realtime monitor

Then I would also disable the automatic port mapper in server network settings (note: this may require you to manually configure port forwarding for remote access).

And lastly I would disable all DLNA features.

The combination of all of these things will make the server a lot lighter on it's feed, drastically reduce disk access, network requests, etc. 

[rbjtech 5284]

If you are getting a BSOD, then look in the Windows logs for the cause...  alternatively, look for a time gap in the emby log while the windows logs the BSOD and reboots.

Edited June 14, 2024 by rbjtech

[ebr 16178]

Check your video drivers.  Those are probably the cause if 90%+ of BSODs.

[oldschool 16]

Well, I think I might have resolved the problem. I'm not sure if it was ultimately Emby or if it was one of my drives overheating and failing and causing the BSOD, but I removed the drive and then tried to fire up Emby again, but it kept crashing the server. I then ran a registry cleaner on it and it found entries for that drive still in the registry (along with a lot of other drives that I had added or removed in the past). After a reboot and a slow approach to bringing on all the plugins and scanning the library, and so far, everything is working well again.

Thanks for the quick and overwhelming assistance - you guys rock! Problem resolved - if I run into the BSOD again, I'll be back, but things are holding up now. Thanks again!

[oldschool 16]

Server was up for about 24 hours, most of that without Emby running. Started Emby, it ran for a good 3-4 hours, and then BSOD. Back to square one. 

I don't see any exclamation points in the Device Manager. I was pushing the server hard by moving files in and out of the server, and I was pretty hopeful that things were going well. Looks like the EventID 131 is still giving me problems with 6 errors, but volmgr, BugCheck, and EventLog all had one Error in the last hour per the Administrative Events listing. I don't know how to update drivers when CCleaner says all drivers are up to date.

Working with ChatGPT to troubleshoot the eventID's and try and resolve one by one.

[Luke 42078]

Let us know what you find. Thanks.

[rbjtech 5284]

1 hour ago, oldschool said:

Server was up for about 24 hours, most of that without Emby running. Started Emby, it ran for a good 3-4 hours, and then BSOD. Back to square one. 

I don't see any exclamation points in the Device Manager. I was pushing the server hard by moving files in and out of the server, and I was pretty hopeful that things were going well. Looks like the EventID 131 is still giving me problems with 6 errors, but volmgr, BugCheck, and EventLog all had one Error in the last hour per the Administrative Events listing. I don't know how to update drivers when CCleaner says all drivers are up to date.

Working with ChatGPT to troubleshoot the eventID's and try and resolve one by one.

Hmm 'volmgr' - that's storage...     

I'd start looking at all the disk physical connections and if those are secure, run full disk scans including surface scans on the storage.   This will take a while, but worth it to get a 100% bill of health on the physical disks.

Are you running any RAID controllers etc ?

[oldschool 16]

I've had a few error messages about a drive overheating, but it never went over the "maximum", so I assumed things were OK. Now I'm suspecting that when Emby starts scanning files on that drive, that the I/O is causing the drive to overheat and then it loses connection and causes the BSOD. I'm working on replacing that hard drive right now. I'll report back if that corrects the problem.

[rbjtech 5284]

39 minutes ago, oldschool said:

I've had a few error messages about a drive overheating, but it never went over the "maximum", so I assumed things were OK. Now I'm suspecting that when Emby starts scanning files on that drive, that the I/O is causing the drive to overheat and then it loses connection and causes the BSOD. I'm working on replacing that hard drive right now. I'll report back if that corrects the problem.

You need to get more airflow across the drives in your server if drives are overheating - I/O will increase the temp of the drive, but only a couple of degrees - they should never go about 40 degrees for maximum life, ideally sitting at mid to low 30's.

Above 45 degrees, then you are significantly lowering the life of the drive, above the drive max specification (depends on the drive, but usually about 50 degrees) then you'll probably start getting smart errors being reported by the drive - but they should not crash the system and I believe modern drives will throttle themselves when this hot to try and avoid further damage.

Lots of free and paid utilities out there to monitor this - and dynamically adjust fan speeds etc.

Edited June 15, 2024 by rbjtech

[oldschool 16]

After a lengthy, multi-day troubleshooting fiasco, I think everything is back up and running. I believe the problem was the faulty drive dropping out and causing the BSOD, but now things are resolved and I'm up and running 100%. Thank you for the fast replies!!