PMS 1.18.1.1973 Always crashing in Windows 10 Pro

Plex Media Server Desktops & Laptops
44

I’m very sorry to hear that :frowning_face:. I installed the latest version and it works fine for me. Only issue it always transcode videos with CPU instead of GPU even I enabled hardware encoding :roll_eyes: :thinking:

45

If running headless, you will need a dummy HDMI monitor plug.

46

Since when does it require a dummy HDMI plug? It’s been running fine for over a year until the latest updates without one.

47

I have posted this elsewhere in the forum

We now have a fix for one of the causes of crashes relating to intel graphics and hardware acceleration

See release note for 1.18.3.2156-349e9837e which was released earlier today Plex Media Server

  • Fix crash on Windows with Intel graphics adapter and hardware acceleration enabled (#10736)

This is also included in the 1.18.4 beta released today

Until I hear otherwise, we have two causes for the hardware acceleration related crashes:

48

I am interested to know if the issue of running headless or as a service or scheduled task is still happening with latest fixes in 1.18.3 and 1.18.4

49
50

copying my post from the other thread

Thanks for trying.

With 1.18.4 beta, there is now a new Server Advanced Transcoder setting for hardware encoding. One thing to try now is disabling this and keeping Hardware Acceleration enabled to see if this avoids the crashes when running as a Service or running headless via RDP and could be the way to configure hardware transcoding

See release notice for 1.18.4.2164

  • (Preferences) Enable “Use hardware-accelerated video encoding” by default.
51

There is nothing in release notes about a new setting. Just that HW acceleration is on by default.

Anyhow, personally I’ve moved on to the P2000 with a dummy monitor plug and everything is good again.

52

For everyone who doesn’t know what is headless means.

“Headless” in this context simply means without a graphical display. (i.e.: Console based.)
Many servers are “headless” and are administered over SSH for example.

https://stackoverflow.com/questions/4647719/what-does-headless-mean

53

Perhaps not clear - but it stated as “Preferences” and this is the term used internally for Server Settings. It is a new Preference.

54

Thanks for info and help. With hw transcoding (in any combination) turned on on any of recent Plex versions (including 1.8.4.x), server crashes with up-to-date Intel drivers. Downgrading drivers to .7000 did solve the problem. At least until Windows decides to update them again :slight_smile:

55

Following the test of new Intel driver by @Geran and previous feedback from @d0cx, we now have a conclusion to these crashes.

So to summarize the fixes for Plex Media Server crashes when hardware acceleration is in use

  1. Intel Graphics Adapter Driver bug - leading to crash of the Plex Media Server process in module igdumdim32.dll

This is now fixed in the latest driver - this table shows the versions and which version fixes the crash

image
image765×265 16 KB

See https://downloadcenter.intel.com/download/29274/Intel-Graphics-Windows-10-DCH-Drivers?product=197599 (or equivalent)

  1. Plex Media Server bug leading to crashes when testing the intel graphics adapter with hardware acceleration enabled

This was fixed as from Plex Media Server 1.18.3.2156-349e9837e Plex Media Server

  • Fix crash on Windows with Intel graphics adapter and hardware acceleration enabled (#10736)
  1. There may be still be crashes when running Plex Media Server headless through RDP or as a Service or Scheduled Task.

For these, as from version 1.18.4.2164 of Plex Media Server, there is a new Advanced Setting for the Transcoder that allows user to disable Hardware Encoding whilst leaving Hardware Acceleration enabled and used for decoding. That would be a better option than disabling all hardware acceleration in such environment

See Plex Media Server

  • (Preferences) Enable “Use hardware-accelerated video encoding” by default.
56

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