Another - My server keeps crashing

Server Version#: 1.17.0.1841
Player Version#: Various
Plex Media Server Logs_2019-10-07_08-15-48.zip (513.1 KB)

So I have PMS running on a Server 2016 host (OS Version: 10.0.14393 Build 14393). PMS keeps crashing, probably 1 or 2 times a week. Has been doing this for quite some time now (months).

I have done the following:

Behavior:
This does not happen while watching content, it happens at seemingly random times the server will just stop. I can login to the host, the icon will not be in the tray. No PMS processes/services running.
Manually start PMS start and its like nothing happened.
It can run for a week(s), a day, or any amount of time in-between.

I have looked at the logs with nothing glaring.
I’m currently trialing hardware transcoding, this issue was happening well before enabling that and happens when it is disabled.

Server is access by a number of services:
*Ombi
*Radarr
*Sonarr

The server does not have any plugins, nor does it do any D-TV work.
All media is local to PMS and does not need to go over a network to access.

Anyone got any ideas?

1 Like

I’m not sure why, but your collection of log files is missing the previous
Plex Media Server.1.log
Plex Media Server.2.log
etc, and I couldn’t find the system logs. What you left doesn’t show a complete boot and eventually a crash. There’s a crash log or two, yes, but not the important logs to go with it.

Nice post though. Thanks for taking the time to get organized.
What sort of antivirus, malware, or security software do you run?

Thanks for taking the time.
Ill collect the logs again when it inevitably crashes.

AV is standard MS Defender, no other security related software on the host.
It’s in-fact very spartan, just PMS and Hyper-V, Intel drivers.

Oh nicely sparse. Should be pretty straightforward to isolate.
Let us know.

Hello,

About 4 months ago Plex Media Server started crashing my computer with the Blue Screen of Dead at least once a week. It got so bad that Windows Updates could no longer install any updates in my system.

Got a new SSD hard drive (my mechanical drive was at least 10 years old) and I did a full installation of Windows from scratch and started installing all my programs with no trouble.

Eventually I got to Plex and after rebuilding the libraries for all my movies\TV show (stored in my Synology NAS) the crashing started happening; uninstalled Plex and the computer is running fine again.

A couple of weeks ago I installed Plex on a spare computer and the rebuilding of the libraries completed and it was working fine until it didn’t. Now I get BSD right away while booting, I tried to fix\scan\rebuild the PC for the last two days and nothing worked.

I don’t know what changed in Plex but it is eating up my systems and time at a rate I cannot afford. Time to look for alternative to Plex.

Roberto

Sorry to hear that Marionette_66. When a windows machine gets a BSOD, the Windows Operating System itself, referred to as the kernel, has panicked and can’t run the OS GUI anymore. That can happen when a low level driver and Windows aren’t communicating well.

If it was instead Plex that was crashing, Windows would keep running.
If instead you had hardware problems or BIOS problems, the computer would spontaneously reboot or lock up solid.

So the question is, why twice now are you able to create a Windows machine where the OS is so unstable at the kernel / driver level that when Plex is running it takes your computer to the point of OS failure. I’m guessing network card or gpu drivers or something really annoying.

I wish you luck sorting that out.

See also: the first result when searching

Thank you Nibbles,

I went over dozens of different articles about BSD and I could not fix the problem. The only thing that worked for me was:
a. Reinstall Windows from scratch
b. Do not run Plex

Well it happened again. I did have hope, it had been a while… A week maybe?
Same behavior, has been going ok, out of the blue just dies.

So here is the data:

Installed Server Roles/Features

  • File and Storage Services
  • File and iSCSI Services
  • File Server
  • Data Deduplication
  • Server for NFS
  • Storage Services
  • Hyper-V
  • Remote Desktop Services
  • Remote Desktop Virtualization Host
  • .NET Framework 4.6 Features
  • .NET Framework 4.6
  • WCF Services
  • TCP Port Sharing
  • Media Foundation
  • Remote Server Administration Tools
  • Role Administration Tools
  • Hyper-V Management Tools
  • Hyper-V GUI Management Tools
  • Hyper-V Module for Windows PowerShell
  • Remote Desktop Services Tools
  • Remote Desktop Licensing Diagnoser Tools
  • File Services Tools
  • Services for Network File System Management Tools
  • SMB 1.0/CIFS File Sharing Support
  • Windows Defender Features
  • Windows Defender
  • GUI for Windows Defender
  • Windows PowerShell
  • Windows PowerShell 5.1
  • Windows PowerShell ISE
  • Windows Server Backup
  • Wireless LAN Service
  • WoW64 Support

Installed Software:

  • Microsoft Visual C++ 2015 x86 Minimum Runtime - 14.0.24210
  • Plex Media Server
  • Microsoft Visual C++ 2015 x86 Additional Runtime - 14.0.24210
  • Microsoft Visual C++ 2005 Redistributable
  • ConfigMgr 2012 Toolkit R2

Hotfix(s):

  • KB3192137
  • KB4485447
  • KB4498947
  • KB4503537
  • KB4509091
  • KB4512574
  • KB4521858
  • KB4516061
  • KB4524152
  • KB4519998

Plex Media Server Logs_2019-10-12_08-24-57.zip (162.2 KB)

EDIT: Added another ZIP, for some reason the Plex log tool isn’t getting them all.
2019-10-12-ManualZip.zip (12.4 MB)

Raffish! what is up today? Your logs show one possible config issue, but there could be a deeper problem based on the crash pattern you described. They also show some filesystem errors that are odd.

First couple of things.

  1. Hey look you’re running v1.18.0.1913 not what you said at first :slight_smile:

  2. If crashes occur, it might be Windows which you can check and repair with Microsoft’s System File Checker, sfc

  3. IPv6 can affect PMS in subtle ways, and if you’re having problems, it’s worth disabling that in Settings - Show Advanced - Network and then restart PMS.

If those don’t get it sorted, your usage pattern + the crash pattern suggests we limit automatic tasks. I’ll continue to dig into your older logs looking for the crash time.

Thanks again Nibbles.

SFC completed, did find some issues, some of which were unable to be repaired.
I will have to begin the process of backing up my VMs and rebuild the OS and see how it goes.

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