@sa2000 it’s 64bit… I’ll get the output of listdlls.exe for you.
As I’ve mentioned, this was all working fine up until a few versions ago. Not sure what changed. I keep a minimal amount of software on this desktop, so I haven’t updated/added much other than Plex and the intel graphics drivers.
We have a new beta out. 1.18.0 with some further changes relating to hardware acceleration. But it is a major release with new music libraries functionality - have a look at the release note and linked forum thread and article
Are you using HW Acceleration with the Integrated Intel Graphics? I’m running an Nvidia Quadro P2000 in the same box as you, except I swapped the CPU from the E3-1225 v5 (thought it was a gutless wonder personally) to an Intel E3-1280 v5. Just pull the old chip, put in the new one. Picks it up and works like a champ. My two plex servers are running that config and no issues with the latest versions. I found the Intel HW Acceleration lacking. I do have the Integrated Intel Graphics disabled though.
As I mentioned, everything was fine up until a month or two ago. No problems with the HW acceleration and the Intel GPU on the board. But then Plex started crashing immediately as any file was played.
I may just do the CPU swap. Thanks for letting me know that worked well for you.
It was somewhere between 1.16 and 1.17. Since I direct stream/play at home mostly, I didn’t notice the problem until I used a client outside my home. The crashing doesn’t seem to be isolated to a certain set of media.
Tried latest 1.18.0.1906 and still no luck. Crashes immediately.
I thought about doing the rollback, but I’m fine with it off for now. However, it would be great if it would work again and take some stress off the CPU. I’m hoping this get resolved soon.
I do not know if intel have means for you to refer the crash dumps to them or the crash stack and dll versions - the crashes are in their module from a call from a Microsoft module d3d9.dll
We would not be able to debug what is going on in the intel dll - of course if the issue can be easily reproduced by the development team then that would give it a good chance of getting understood
I will add a note to the raised issue to indicate that the crashes are persisting,
@housepark Ahhh! I was hoping to score some sort of black friday deal on the Quadro P2000 to solve my problem. But even with disabling the intel GPU, you still have the same issue?!
@sa2000 Was there any ever progress on this issue? Is there any way I could submit a bug ticket/incident to follow up on and track?
I bought the Dell T30 (Win 10 pro) about 2 weeks ago and was having the same issue even with the p2000 installed until i disabled the igpu. Now HW Acceleration works fine.
Posting this in the threads relating to the crashes when enabling hardware acceleration
There may be several causes for the crashes
I would like any one getting the crashes and running Plex Media Server as a service or scheduled task or via RDP / Headless to stop doing that so we can concentrate on any new crashes. The issue with crashes in the intel driver when running headless / as service goes back over a year
With regards to recent crashes - we have one crash that appears to have come in between version 1.18.0.1944-f2cae8d6b and version 1.18.1.1966-10fc2f8d3. These are the crashes that manifest themselves in the server logs with this logged error before crashing ERROR - [FFMPEG] - Error setting child device handle: -xxx where xxx is a number that varies
We have another crash that I am trying to establish when it started or see if it is an intel driver issue
I have feedback from the development team that there is a suspected intel driver bug on Apollo Lake systems
And we have the RDP/Service/headless issue - which we should eliminate by not running in this mode whilst trying to find the cause of the recent crashes
We have been unable to reproduce this crash to investigate the cause of the crash.
If there was a Plex Media Server regression, I would like to establish which version this started with. There was some feedback that may be this specific crash was in changes between version 1.16.6.1592-b9d49bdb7 and 1.17.0.1709-982421575. I would like to confirm if that is the case.
Do you have access to the 1.16.6 versions ? Perhaps in the updates directory?
Yes I disabled the Intel GPU and still having the problems unfortunately. I may take the route of getting a difference processor per the earlier thread, but it’s disappointing that it’s been failing quite a bit. I believe this has been going on for about a month, and I do believe one of the 1.16 versions was the last one it was working fine in?