Random crashing of Plex Media Server suddenly after a year of stable running

Plex Media Server
1

Server Version#: 1.25.0.5282
Player Version#:

Plex Media Server has been very stable for me for a while now. Suddenly over the last 3 days it has suddenly been crashing without have made any changes to my setup.

I have tried optimizing the database and I have also checked that I don’t have any rogue dll files that might cause any conflict. I am running Plex Media Server on a dedicated Intel 11th Gen NUC with 16gb of ram on Windows 10 Home vs 21H1 OS Build 19043.1348.

I am also running Tautulli V2.7.7 on the NUC and not even running Radaar or Sonaar or NZBGet on the device. It is solely dedicated to running PMS.

Plex Media Server Logs_2021-12-04_17-24-30.zip (3.8 MB)

Any help in deciphering the logs would be really helpful. I would also like to get some advice on where I should look in the logs to try and figure out how to find the culprit of the crashes.

Thank you very much

2

The PMS logs may have some clues but depending on the problem, nothing may show up… PMS might die before it knows what hit it.

Don’t overlook the Windows Event Viewer, there may well be a clue in there.

3

Hi thanks for that. I have uploaded the PMS logs in my post but I am not sure of where to look for the issue, any pointers on what I am looking for?

I will have a look at Windows Event Viewer too. Thanks.

4

Bumping for Visibility. I really would appreciate some help as my server is crashing every few hours and I can’t find the reason for it. I have gone into the crash report folder of plex meta data but all the folders are empty so I can’t even try and figure out what is going on. Any help with this would be very very appreciated.

Thank you.

5

Bumping and also announcing that I am willing to pay for tech support if anyone can help me out with my issue.

6

Did you see anything in the Windows event viewer?

If you know about what time PMS crashed you can look for exceptions around that time.

I looked at your logs but I don’t know enough about Plex’s inner workings to determine if any of the errors could become critical.

I saw some times where a video on drive M: could not be opened due to a permissions error. (Maybe it was open by another process or something reasonable like that.)

I saw a lot of transcoder errors:

ERROR - [Transcode] [FFMPEG] - Cannot load nvcuda.dll

So maybe your drivers are not set up right, but I wouldn’t expect that to make Plex bomb out. (Or maybe Plex spams that error if an Nvidia card is not present, and it is harmless – I don’t know.)

If it were me, I would back up my Plex database to another volume, remove PMS, run chkdsk C: /f /r /x, completely reinstall PMS, and restore the backup. That is spray and pray troubleshooting, but it is easy enough to do and it might help.

7

Looking at your log, I can confirm PMS recorded the crash. Unfortunately, there isn’t much info on the cause. Can you turn off the option to send crash reports to Plex? Next time there is a crash, the report will stay on your computer. Upload that report to me along with the PMS logs from that crash.

Harmless. Now you know. :smiley:

1 Like
8

Hi there Moviefan.plex. Thank you for looking into this for me.

I have actually uninstalled the latest version of PMS: Server Version#: 1.25.0.5282 and rolled it back to: Version 1.24.5.5173. I realised that the crashes started exactly on the day that PMS auto updated to the latest version. It is now stable and running as before. It definitely has to do with the latest version of PMS.

Would you like for me to try and reinstall the version of plex and send you the crash report so you can figure out what the issue is?

If so I will have to do it after this weekend as I want to find a time to update and wait for another crash.

Thanks.

9

Same thing is happening with me. Will be watching with my roku and then all of a sudden my computer will shut down in the other room taking the server with it. Keeps happening frequently and Im getting frustrated. I tried going back a version to 1.24 and thought I had fixed the problem but its still happening today. help please

10

Yes, that’s the only way we can look into a crash. Next week is fine, whenever you can.

Wooh! You’ve got bigger issues there if your computer is shutting down. Plex crashing should not shut down the computer. Have you looked that it’s not doing that due to excess heat or something hardware related?

1 Like
11

Yes, its definitely plex causing the issue. I switched to Emby and have no more issues. If plex cant keep things stable then no use in using it anymore, especially when it can damange my computer and hardware

12

The only thing I can think is that transcoder is pushing your cpu and your cooling system isn’t able to keep up so it shuts down due to the heat.

13

My server has crashed again but even though I have turned off Send Crash Reports to Plex, the Plex Crash Report folder is still empty.

Am I not looking in the right place?

14

Please provide your latest logs. Exactly when was the crash if you know?

15

Hi there @anon18523487.

When I originally had the crashing issues I realised that it started when the server automatically upgraded to PMS v: 1.25.0.5282

I rolled it back to PMS v 1.24.5.5173 and it was stable again.

I have now upgraded my plex server to the latest version: 1.25.5.5492-12f6b8c83 and the random crashing has come back.

Also just as further background, I had completely rebuilt my PMS from scratch as the SSD Drive that I had my previous server completely died on me and I had to send it away for RMA but that is a separate matter.

I have noticed that my crash reports are being uploaded but I am unable to see what is contained in them.

I am attaching my latest plex crash uploader logs and also my plex media server logs:
Plex Crash Uploader.1.log (613 Bytes)
Plex Crash Uploader.log (614 Bytes)
Plex Media Server.1.log (10.1 MB)
Plex Media Server.2.log (10.1 MB)
Plex Media Server.log (2.2 MB)

Any help would be greatly appreciated as I really would like to get to the bottom of the issue.

Thank you very much in advance.

16

The PMS logs you provided don’t cover when the crash occurred or did it happen at the end of the latest PMS log (i.e. it just crashed now and you grabbed the logs right away)? If so

The crash uploader logs don’t contain anything, they only say the logs were sent to Plex. I don’t have access so I can’t see them. In your PMS settings, turn off sending the crash reports to Plex. This will leave the actual crash log on your computer, send that to me instead. Also include the PMS log from that future crash.

17

Yes I had grabbed the log immediately after the crash. So the server logs were from before I relaunched Plex. I will turn off uploading the crash report to Plex but whenever I have done that in the past the local Crash reports on my PC doesn’t show up with anything in them.

I will try again now and then see what is there to upload. Thank you very much in advance.

18

Ok, I see that PMS did log sending the crash report. That’s odd. Typically on a crash, the reports are not sent until the restart.

Before the crash, it was testing your system for hardware transcoding capabilities. It’s possible that caused the crash. The last video was King’s Men. Try playing that and force it to transcode and see if you can reproduce the crash.

19

Hi @anon18523487,

I have been able to get some crash .dmp files. The server has crashed a few times since my last post.

PMS Crash DMP.zip (148.4 KB)

I am also uploading a full PMS Log download here.

Plex Media Server Logs_2022-02-27_21-08-07.zip (5.1 MB)

I am not sure what is causing the crashes still. It isn’t as often as when I was on PMS Version: 1.25.0.5282. But it is definitely happening every few days.

I have also disabled 4k transcoding from my server as I felt that was potentially causing my CPU to run at full 100% capacity.

I am using an intel NUC with a 11th Gen Intel(R) Core™ i7-1165G7 @ 2.80GHz. So it is quite a powerful processor with intel quick sync for the video transcoding. But I wanted to play it safe and just disable all 4k video transcodes from my PMS.

20

I have looked at the crash dump for Feb 27, 2022 20:54:01
The crash was in the Intel graphics adapter driver
igdumdim32.dll

Similar crash to what was seen some time ago with some versions of the intel drivers

See bullet 1 in this old forum post

So suggest you try different versions of the Intel graphics adapter driver and see if there is a recent version that does not crash

If you need to refer this to Intel tech support - the folllowing was the stack for the crash

Memory Map line from “lm f” output

69a20000 69b5c000   igdumdim32 C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_61d55e35d1ef8146\igdumdim32.dll

0:075> .ecxr
eax=00200000 ebx=167720c0 ecx=00000000 edx=00000000 esi=00000000 edi=07c5d304
eip=00000000 esp=07c5d234 ebp=07c5d248 iopl=0         nv up ei ng nz na po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
00000000 ??              ???

STACK_TEXT:  
WARNING: Frame IP not in any known module. Following frames may be wrong.
07c5d230 69aa9eb1 00000000 07c5d3bc 07c5d304 0x0
07c5d248 69aa7cba 167720c0 07c5d3b8 07c5d3bc igdumdim32+0x89eb1
07c5d270 69a7df8f 167720c0 07c5d3b8 23777030 igdumdim32+0x87cba
07c5d31c 69a8133f 167720c0 07c5d3ac 07c5d3fc igdumdim32+0x5df8f
07c5d400 54bf8249 167720c0 07c5d46c 12df70a8 igdumdim32+0x6133f
07c5d418 54afe2e3 69eea040 07c5d46c 00000001 d3d9!CBatchFilterI::LHBatchCreateResource2+0x29
07c5d93c 54afdea4 00000000 00000000 54afde80 d3d9!CreateSurfaceLH+0x3f3
07c5d9a8 54b07d0f 07c5da08 a675280c 04400000 d3d9!DdCreateSurfaceLH+0x24
07c5d9ec 54b8dfb7 07c5da08 00000000 1a76e040 d3d9!DdCreateSurfaceFilter+0x3f
07c5db18 54b88b11 00000100 00000013 30313050 d3d9!CSurface::CreateOffscreenPlainSurface+0x503
07c5db64 6c2156d5 1a76e040 00000180 00000100 d3d9!CDxva2Container::CreateSurface+0x1a1
07c5dba4 6c21535f 00000180 00000100 00000013 dxva2!CVideoAccelerationService::CreateSurfaceInternal+0x43
07c5dbd8 652ba3e8 09eea3cc 00000180 00000100 dxva2!CVideoAccelerationService::CreateSurface+0x3f
07c5dc8c 7764627f 0000004f 00000020 00000000 avutil_56+0x4a3e8