Yes, after I uninstalled PaaS and started PMS normally, I checked Task Manager; only one instance of PMS running.
Are you using SYSTEM account for the service or a normal user account?
I guess I’m not sure? I use my admin account, honestly dunno if that’s unique from a system account.
I suspect this issue has more to do with Tautulli, so I’m going to pop on over to that forum and try to get some answers.
I’m going to amend this statement after having tested some more. When I was not using PaaS, Tautulli was reporting the server going down and coming back every minute, but the server was actually always accessible. After I re-installed PaaS and started PMS using that, Tautulli again alerted me to the server going down and up, but this time the server actually jumped back and forth between unreachable and reachable.
I un-installed PaaS again, rebooted and started PMS normally, and now I’m back to the first behavior (Tautulli reporting, but server reachable).
I’m running Tautulli v2.1.25, and PMS v1.14.0.5470.
Has anyone figured out how to run as a service and have HW decode work? I know it’s been brought up a bunch but haven’t seen anything solid on a workaround or a fix.
1 Like
I’d like to know as well!
It’s been months and Plex is standing with their claim that it’s an Intel bug even though it’s not limited to just Intel, the only software that changed was PLEX, and they can’t tell you exactly what the conditions are to trigger the bug.
1 Like
Would also like to know if this is possible, need hardware transcoding and need to run plex as a service
1 Like
At this point I’m still stuck running 1.12.3 with PaaS. Installing anything 1.13.0 or higher causes it to not even launch with PaaS 1.1.7. With PaaS 1.1.2 newer versions will launch but then fail to play any media saying the conversion failed.
I’m about to give up on PaaS and move to either Ubuntu Server or just use Autologon for Windows.
Maybe Plex is right, and it is a (relatively newer) Intel issue.
My motherboard is an Asus Sabretooth Z77 with an Intel Core i7-3770 processor, which are 6-7 years old.
I don’t seem to be experiencing the crashes that others have noticed when hardware transcoding. My motherboard chipset is pretty old, in “computer years”.
Maybe Intel modified multimedia features / APIs that work fine with my older chipset, but the newer chipsets don’t handle them properly.
The nice thing is, while my motherboard chipset is over 6 years old, the ancient chipset isn’t impacting my overall performance very significantly. I can still run lots of games (in 4k) and run CPU-intensive stuff just fine.
Nah, Im pretty sure it’s a PLEX issue. The only software that changed when it broke was PLEX. I’ve tried several older drivers as well… Also, the guy who says it’s an Intel driver issue always blames PLEX bugs on other unrelated things and tosses out a laundry list of undecipherable “blah blah” 
There are numerous reports of similar issues with other graphics engines, other graphics chips, and even discrete cards.
This problem began early last summer if I recall correctly. I have an i7-4770 running my PLEX setup and it’s not an issue if you DON’T run the PMS as a service. I’ve disabled the service and switched to autologin which still has issues of restarting on crashes but …
https://ark.intel.com/compare/75122,65719
Which driver are you using? This was the driver I had installed before it stopped working and after it stopped working
Driver File Version: 20.19.0015.4963 (English)
Driver Version: 20.19.15.4963
Where did you find your Intel Motherboard Drivers listed in your Device Tree?
I have a “PCI Express Root Complex”, listed at the top of most of my PC motherboard related drivers, but that driver is by Microsoft.
One of these methods will work. IIR I had to use the DxDiag option
@Smokindog - OK, we’re talking graphics drivers, not motherboard drivers.
I’m using an Nvidia GTX-1060 GPU. I don’t have the (pretty much worthless) Embedded Intel Graphics enabled in my BIOS. This is an old processor, long before the industry decided that putting a somewhat usable GPU in the main processor could be a good thing.
I’m not seeing the Intel graphics drivers listed in DxDiag or via the desktop method.
That could easily explain why I don’t see transcoder crashing - I don’t have the Intel GPU drivers installed.
Your 3rd gen 3770 is fundamentally the same as my 4th gen 4770.
What motherboard drivers are you speaking to? The INF? I’m not clear on what you’re referring to.
I was originally thinking that you were referring to the Intel chipset drivers (aka, all the motherboard North Bridge / South Bridge and embedded functions).
Then, I realized that you were actually referring to the CPU-embedded Intel Graphics drivers, which I must have disabled in my BIOS - I don’t show any Intel Graphics in my Device Manager tree.
Maybe disabling the embedded graphics in the BIOS could be a Plex crash-prevention solution for folks who have installed a separate GPU?
Hi everyone,
I am troubleshooting hard why my Plex 1.14.1.54 crashes right away when ran by PMSS 1.1.7.
If anyone can give me pointers of where to dig to figure out what is going on I will definitely appreciate it.
Right now if I kill the PMSS windows service I can run PLEX no problem but the goal here is to have PMSS run Plex as a service which is not happening for an unknown reason.
- EventViewer gives no hint (at around the time of my tests with time stamp 10:11:00)
-
PMSS configured port is 32400
-
PMSS logs really tell the obvious which is that Plex crashes when ran
PMSS_Log.txt (3.1 KB)
PMSS_Log.txt (3.1 KB)
Ports 32400 and 8787 are fully opened (private & public) and all Plex related process are excluded from security limitations.
Rebooting doesn’t help.
Thank you haf-blade. The NSSM solution worked for me where PMSS didn’t for a still unknown reason.
Been using PMS as a Service for a few months now and it’s great!
Running it on Windows Server 2016.
Though I now run in to a problem.
I swapped my HDD for a SSD and since the upgrade PMS as a Service is no longer able to connect to my network drives
\\192.168.1.1\movies
etc
This is ONLY after a reboot. If I manually stop and start the service all network shares are mapped correctly.
Could it be the service is started to early (because of the SSD speed) and there for does not know which credentials to use?
I have the service setup with the Delayed Start option. Try it
