PMS crashes on windows 11, wont restart unless reboot PC

Plex Media Server Desktops & Laptops
1

Hey Guys, just seeking some advice on this.

Wasnt an issue until i moved from Windows 10 to 11. Yea i know, stupid.
Long story short, pretty much once a day, time varies, not specific, PMS will crash.
The crash isnt the issue, its the fact that ill restart the service, but it wont actually connect. It shows operational, but if i use the webui, not reachable.

The only way it actually starts to work is if i reboot my PC, and that gets old fast, im usually not home and need to do it remotely, which is a pain.

Can anyone offer any advice on this issue? And how to fix the damn thing so it stops happening?

2

Please upload a set of server logs that capture the crash.

  1. Check that Plex Media Server is configured for debug, not verbose, logs.
    Settings → Server_Name → General + Show Advanced

    debug
    debug715Ă—154 20.9 KB

  2. If you change the log level, restart Plex Media Server.

  3. After the next crash, reboot PC (since Plex is otherwise unreachable) and start Plex Media Server.

  4. Wait three minutes for Plex to fully start and log the sequence.

  5. Pull the log files (Settings → Troubleshooting) and upload the ZIP file to the thread.

1 Like
3

Hey,

Ill pull the data from yesterdays crash, and once it happens again today ill load up todays data.

4

Plex Media Server Logs_2024-06-02.zip (6.9 MB)

5

And here is todays after the usual crash.
Plex Media Server Logs_2024-06-02_18-13-39.zip (7.3 MB)

6

Thanks for the log files.

You are running the 32-bit version of Plex Media Server. Notice (a) the build is -x86, not -x86_64, and (b) the install location.

Jun 02, 2024 18:08:46.728 [24916] INFO - Plex Media Server v1.32.7.7621-871adbd44 - Microsoft PC x64 - build: windows-x86 windows - GMT 10:00
Jun 02, 2024 18:08:46.729 [24916] INFO - 24 3187 MHz processor(s): Architecture=0, Level=6, Revision=38658 Processor Identifier=Intel64 Family 6 Model 151 Stepping 2, GenuineIntel
Jun 02, 2024 18:08:46.729 [24916] DEBUG - "C:\Program Files (x86)\PlexMediaServer\Plex Media Server.exe"

PMS is hitting a Windows resource limitation. This message repeats several hundred times before the system crashes (at the end of Plex Media Server.1.log).
Jun 02, 2024 18:06:17.171 [22780] ERROR - Thread: Couldn't add a new thread to the pool of size 14: resource unavailable try again: resource unavailable try again


Suggestion: Download the 64-bit version from plex.tv and perform a manual install (link).

I searched the forum for “Couldn’t add a new thread.” There were several reports, and all were running the 32-bit version of PMS. Updating to the 64-bit version of PMS resolved the problem.

You can install the 64-bit version on top of the 32-bit version. The installer will remove the old version.

Before updating:

You are running PMS v1.32.7.7621. The current public release is 1.40.2.8395.

PMS 1.40 introduced many database changes.

You may see a “503 maintenance” message after installing the PMS update.

If so, wait. It will take Plex some time to update the database to the new format. The amount of time depends on the size of the database and the speed of your system. For some, it takes minutes, others have reported hours (ex: PMS on Celeron based systems).

Do not stop PMS. Doing so only delays things. The database migration process will restart when PMS is restarted.

Do not try to downgrade. This risks database corruption.

Check on the system every 15 minutes or so. The “503 maintenance” message does not auto update. You will need to refresh the browser window (or close & re-open).


FYI 1: A side benefit of updating to 64-bit PMS is more efficient transcoding and hardware accelerated HDR to SDR tone mapping when using the Nvidia GPU. Specifically select the Nvidia GPU in Settings → Transcoder instead of leaving it at Auto.

FYI 2: PMS 64-bit has been available since Sept. 2022. However, the Plex installer does not mention that a 64-bit version was available (resolved in current beta). So, if you installed PMS before that date, you were never informed that a 64-bit version was available.

7

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