HW Acceleration crashes on Dell PowerEdge T30 / Windows 10 Pro

Plex Media Server Desktops & Laptops
1

Running Plex Media Server on a Dell Poweredge T30 with Windows 10 Pro. Recently noticed that when Hardware Acceleration is on Plex immediately crashes if any client gets a transcoded stream. Hardware Acceleration has worked flawlessly since I got the server set up last year. So, something recently has caused it not to work anymore in my setup. Not sure if it’s Plex or the Intel driver for the onboard P530 gpu.

Plex Server Version#: 1.17.0.1709
Windows Version#: Windows 10 Pro Version 1903 (Build 18362.356)
Intel P530, Driver Version#: 26.20.100.7158

Thoughts?

2

Hey sorry to hear that. We could server log files in debug mode after it happens again. Zip up the whole folder it gives you and attach it with your next reply. Let’s also have you reboot all your hardware without haste, giving everything 10min or so to completely initialize before testing.

If you want to have a look yourself, things to search

  • error
  • fail
  • critical
  • TPU:
3

Yeah, pretty much as it tries to run h264_qsv, which I’m assuming is the process to leverage intel quick sync, it dies. What happens to that crash data that gets reported to Plex?

Sep 24, 2019 20:59:36.696 [0788] DEBUG - Codecs: testing h264_qsv (encoder)
Sep 24, 2019 20:59:36.696 [0788] DEBUG - Codecs: hardware transcoding: testing API qsv
Sep 24, 2019 20:59:37.271 [9164] DEBUG - Job running: C:\Program Files (x86)\Plex\Plex Media Server\CrashUploader.exe “–directory=removed\AppData\Local\Plex Media Server\Crash Reports\1.17.0.1709-982421575” --version=1.17.0.1709-982421575 --platform=Windows “–platformVersion=10.0 (Build 18362)” --serverUuid=removed --userId=removed --sentryUrl=https://sentry.io/api/1233455/minidump --sentryKey= --vendor=Microsoft --model=x64 --device=PC
Sep 24, 2019 20:59:37.286 [9164] DEBUG - Jobs: Starting child process with pid 5948

4

I think there is a new issue with the new transcoder, where it does not properly fall back to software (cpu) decoding for media that is not compatible with the GPU.

5

Following the wording in my log file, it tries to test the API of qsv and then crashes. So based on that log, it doesn’t look like it even gets to start to transcode a video, but querying it to see if Intel Quick Sync is there and then crashes it.

Maybe something up with the h264_qsv version plex is using or with the latest intel drivers for the P530 GPU?

6

Looks like it may be related to this thread:

@sa2000 Said it should have been fixed… doesn’t look like it tho.

7

Not disputing what you found, but it’s worth mentioning that PMS tests each hwaccel codec and uses the fail or success results to find the best one that works. Without the whole PMS log folder, we can’t see the context, and even then it’s an art, reading those files.

If you’re able to easily correlate the crash to right then, that’s good news.
It will make it easier for people to debug.

8

Appears to be a different crash from the intel one - still intel but in different module. Crashing in igdumdim32.dll after call from d3d9.dll which is called by dxva2.dll

I will discuss with the development team.

Did you before have the crashes in the linked forum topic ? Did hardware acceleration work without crashes prior to 1.17.0.1709 ?

To submit it to the development team would need full logs - best to repro after a relaunch of Plex Media Server

Might need to get a full dmp file out of windows for these crashes instead of the minimal crash report that gets uploaded

See section here on registry edit to get windows to create a dmp file
https://support.plex.tv/articles/201455336-crash-logs-plex-media-server/

1 Like
9

@sa2000 Alright. I’ll work on getting the dmp and logs. Family is using the server now…

Hardware acceleration probably stopped working for 1.16… Previous to those versions tho, everything was fine and the acceleration worked like a champ. I eventually realized it was causing a problem a month or two ago, so I turned it off… Shrugged it off as a bug that would probably eventually get fixed, but never reported it when I should have.

Can you look back at crash reports submitted from my account for the past few months?

10

I can only see a couple of crashes at around
Sep 25, 2019 12:59:37 AM UTC
Sep 25, 2019 1:00:07 AM UTC

Crash Uploading is rate limited so not all crashes upload - but the Crash Reports subdirectories would still have any that did not upload

11

Your Windows Application Event Log will have all crashes and versions

12

Don’t know if you have already done this but please do check for updated Intel drivers for the graphics card

1 Like
13

@sa2000 There is a new Intel driver set, just released today. Version xx.xxx.7212. Let me see if this fixes it first, then I’ll get you the logs.

14

New Intel drivers didn’t fix. Still crashes with HW acceleration on.

15

@sa2000 Any luck with the logs I sent along?

16

I have been trying to see if i can get the crash but have not been successful to reproduce the crashes

It is crashing in the intel driver igdumdim32.dll

STACK_TEXT:  
098adbb0 65494a1d 00000000 098add3c 098adc84 0x0
098adbc8 65492923 09ecc700 098add38 098add3c igdumdim32+0xa4a1d
098adbf0 654624c1 09ecc700 098add38 098addb8 igdumdim32+0xa2923
098adc9c 65465109 09ecc700 098add2c 098add7c igdumdim32+0x724c1
098add80 662b62b9 09ecc700 098addec 09f91978 igdumdim32+0x75109
098add98 661be559 14901040 098addec 00000001 d3d9!CBatchFilterI::LHBatchCreateResource2+0x29
098ae2bc 661be104 00000000 00000000 661be0e0 d3d9!CreateSurfaceLH+0x409
098ae328 661be09f 098ae388 35728c09 04400000 d3d9!DdCreateSurfaceLH+0x24
098ae36c 661bdc52 098ae388 00000000 0a35ee00 d3d9!DdCreateSurfaceFilter+0x3f
098ae498 661bd95f 00000438 00000000 3231564e d3d9!CSurface::CreateOffscreenPlainSurface+0x271
098ae4e0 688956c5 0a35ee00 00000780 00000438 d3d9!CDxva2Container::CreateSurface+0xdf
098ae520 6889534f 00000780 00000438 00000000 dxva2!CVideoAccelerationService::CreateSurfaceInternal+0x43
098ae554 66f373c7 0451babc 00000780 00000438 dxva2!CVideoAccelerationService::CreateSurface+0x3f
098ae63c 7728dc16 00000000 00000000 00000000 avutil_56+0x673c7

Could you run dxdiag and select save all information and send me a zip of the saved info file DxDiag.txt - i would like to compare with mine

17

@sa2000 DxDiag sent via PM

18

Thanks.

I have referred this to our development team. Total number of users getting this crash is very low

20

@whoiscarmine
I don’t know if this is relevant but I noticed in the dump all the dll paths eg the ones involved in the crash are from the C:\Windows\System32 directory and not C:\Windows\SysWow64 directory

C:\Windows\System32\dxva2.dll
C:\Windows\System32\d3d9.dll
C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_080d478a80aafa87\igdumdim32.dll

On my system, when i did a listDLLs for the Plex Media Server.exe process, all were from the 32-bit directory

C:\WINDOWS\SysWOW64\d3d9.dll
C:\WINDOWS\SysWOW64\dxva2.dll
C:\WINDOWS\SysWOW64\DriverStore\FileRepository\iigd_dch.inf_amd64_0b0616d2947ad88b\igdumdim32.dll

Could you download the SysInternal Suite https://docs.microsoft.com/en-us/sysinternals/downloads/sysinternals-suite and run listdlls.exe in an elevated command line window and capture the output to a text file and send it to me.

Is the system / windows 32-bit or 64-bit. On a 64-bit system, the 32-bit modules are held in C:\Windows\SysWow64. Plex Media Server.exe is a 32-bit application

21

The dump shows this path for kernel32.dll

75d30000 75e10000   kernel32 C:\Windows\System32\kernel32.dll

I came across this on a web page

… check the full path of “Kernel32.dll” since x64 OS will load “C:\Windows\Syswow64\Kernel32.dll” instead while x86 OS will load the plain “C:\Windows\System32\Kernel32.dll” for x86 executables.

So is this a 32-bit windows OS installation ? (or ths info here is not accurate)