BUG - Windows PMS crashing constantly since update to 1.18.1.1973 - ntdll.dll

Plex Media Server Desktops & Laptops
1

Plex has always been solid for me, until the last few days. After the latest update the server would crash within 60-90 seconds of me connecting to media from a client. After reinstalling multiple times and doing searches online I took someone’s advice to go back to the last version and now it appears I’m stable again. I’m afraid I did that before I saw the log collection process, but I did at least want to post this in case others are looking for confirmation for behavior they’re seeing as well. The info I got from Event Viewer is below.

Server Version#: 1.18.1.1973
Player Version#: Multiple (Android and Windows, latest version)

Faulting application name: Plex Media Server.exe, version: 1.18.1.1973, time stamp: 0x5da83608
Faulting module name: ntdll.dll, version: 10.0.18362.387, time stamp: 0xa4208572
Exception code: 0xc0000374
Fault offset: 0x000df94d
Faulting process id: 0xe60
Faulting application start time: 0x01d595e9056c79ef
Faulting application path: C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 6fe7bd82-9f59-4776-b7e3-5ff6ef35009c
Faulting package full name:
Faulting package-relative application ID:

4 Likes
4

I am seeing other reports of this happening on these latest updates when streaming to Fire TV and such. It’s happening on other clients for me as well, but I imagine they’ve realized there’s a real issue and they’ve started working on it. I rolled back for now and it’s been stable.

6

I can confirm I have the exact same error in my event log and have been unable to update my Plex server since this revision.

It is no good checking the PMS logs - the error abends the main task abruptly so zero diagnostic information is written to the log.

I also note that the crash happens if I play some media, but not others. So, for example, playing something like this works:

MKV AVC (Main@L4) with DTS audio, 1440*1080 5300kbps

…but something like this crashes PMS immediately…

AVI MPEG4 XviD (Advanced Simple@L5) AC3/DD audio 944kbps

Again, the logs just terminate abruptly with no error information and only this below gets written to the Windows Event Viewer:

Faulting application name: Plex Media Server.exe, version: 1.18.2.2029, time stamp: 0x5dcbd98c
Faulting module name: ntdll.dll, version: 10.0.18362.387, time stamp: 0xa4208572
Exception code: 0xc0000374
Fault offset: 0x000df94d
Faulting process id: 0x76c
Faulting application start time: 0x01d59b901c20af09
Faulting application path: C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 0955abb3-1b57-436f-9350-0f92c64e812e
Faulting package full name:
Faulting package-relative application ID:

7

I have the exact same problem from version 1.18.1 and after. even the latest 1.18.2 doesn’t solve this issue. Is there any developer havong a solution to that?

2 Likes
8

The same thing happened to me too. I updated to 1.18.2 from 1.18.0 and PMS started crashing on me. I have noticed that certain videos seem to trigger it and it depends on what device I’m trying to stream from. I was able to roll back to 1.18.0 (AppData\Local\Plex Media Server\Updates) and everything is solid again. First time I’ve ever had an issue with Plex.

9

For me the same problem. Rolled back to 1.8.0 with the steps from this post: I need to rollback from the latest Plex update

10

Can confirm that v1.18.1.xxx and .2.xxx definitely have crashing issues for my install of Plex Media Server. Reinstallations of those versions don’t help. Reinstalling 1.18.0.xxxx works for me. Will have to see if it’s fixed in next update.

11

Can anyone report success with 1.18.3.xxx?

12

Just wanted to say thank you for posting, experiencing the same issue, rolled back to 1.18.0 and so far have not had the same issue. Most common problem has been streaming to a Roku Premiere+.

13

Update: I took a chance on updating to 1.18.6.2368 and the problem I had appears to be resolved.

14

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