I can’t for the life of me figure out what’s going on.
PMS running on a windows 10 64bit version.
checked PMS today morning (11 UTC), the pms icon disapeared from system tray, so I restarted the PC, and PMS auto started with windows.
again at 2pm UTC, I couldn’t connect remotely, went back home to check, it disappeared again.
This time instead of restarting my PC, I just manually started PMS as an admin. However it did not work, as in the PMS icon was in system tray (server should be online) but when going to 127.0.0.1:32400 localhost web, it does not open, as if the server did not start.
I checked the FAQ about crashes, followed it to check the logs, I do not have any crash logs. Tried searching for the dll files, did not even understand what i’m looking for.
Running out of ideas here. This is the first time it ever happened to me. I tried to backtrack my steps on what was different between yesterday and the days before… there’s nothing new, its the usual stuff.
If someone could help me out here, would really appreciate it!
EDIT: I saw theres a beta version out (Version 1.15.8.1163) just installed it automatically via web UI
EDIT2: For now, the new beta version stopped my server from crashing.
i am also experiencing this issue but it seems to be related with Samsung Tizen app . not sure but if i use amazon fire tv to stream it doesnt seem to crash
I’m having the same issue with PMS crashing on a Windows 10 64bit. Had someone look at the logs previously and they questioned if I had any Cygwin apps installed. I’ve disabled any “exttra” apps like Radarr, Tautulli, PlexConnect & Ombi… however no luck. I guess I can go ahead and try out the beta.
I too am also having this issue, windows 10, plex server was working fine until one day i noticed it was off. I ran it the icon would appear in tray then immediately close. no way for me to connect. I tried rebooting, reinstalling, repairing, new directory install, ect nothing is helping, been going on a month now.
Did your windows 10 OS got updated recently?
For me it did and messed up one of my drivers. I knew that when I opened task manager and say “System” taking up around 15% of CPU while PMS was trying to scan.
Its not related but worth a shot.
Try opening up your PMS and stop its auto scan. Or disable your libraries so PMS would not scan anything and see if it lasts.
My PMS would start for a little while then crashed. It may have been related to when it started its auto scan and optimizing my data.
I didn’t really look into what was triggering as once I tried the beta update, it became stable again.
I also noticed it started crashing when this “System” was taking up CPU 15%. I fixed that by re-installing drivers and updating my BIOS version.
Windows auto updated my drivers and somehow it got corrupted while my BIOS version was 3years old. Update to the bios and re-installing all drivers to the latest fixed it.
It may not be related but I felt they were all connected to the same problem. PMS was only 50% of the problem while my OS was the other half.
Edit: I just read @sa2000 post about H/W decoding and that makes a lot of sense. My crash happened after enabling hw decoding a day before. Beta fixed it.
I have been running PMS for years and this is the first time I’ve had problems like this. I use Tautulli to monitor my server and get alerts and there seems to be a coloration between the update that I got the alert for (1.16.0.1220-147963d87) and my crash issues. I am still going through the DLL list but this i a dedicated server and isn’t used for anything else. I have Windows updates deferred and unfortunately I took the opportunity to install 4 Windows updates at the same time. I did install the update for PMS that stated it fixed some crashing issues but the issue persists for me.
Currently I am removing the 4 Windows updates 1 by 1 to see if one of them is causing the issue. The PMS update called out a fix for crashing related to trans-coding however at home everything uses Direct Play. I’m currently about 10 mins into an episode after removing the first update and so far so good,
I can see several crash reports from your server May 29th and then on June 12th to June 16th. All the crashes are in the intel hardware encoding dllL mfx_mft_h264ve_32.dll
These are known to arise if the Plex Media Server is run as a service, scheduled task or through RDP,
The solution is a choice between
hardware acceleration being disabled,or
not to run Plex Media server as service / shceduled task or via rdp
Hardware Acceleration setting is in server / settings / transcoder
Up until the 12th or so right when I installed thpae updates, any crashes that were occuring weren’t noticeable to myself or any of the users and I hadn’t had to manually open Plex more than once or twice over a span of many many months. Glancing at the logs myself the crash log itself had a lot of messages saying “error - failed to upload the crash log”. I will make a new thread for myself and attach the full crash logs instead of continuing here on someone else’s thread.
