Thanks for sending me the server logs from the 15th September
The Update Service should not be relevant to you because you are running Plex Media Service as a Windows Service and you should not be auto updating Plex Media Server when running in that way
When running as a service - updates should be manually done with the service / Plex stopped when doing that and restarted at the end. If doing the updates in a different windows user account from the one the Plex Service is running in, then it would also be necessary to do a registry edit after every update to ensure Plex Media Server does not auto launch on login - see PMS as a service - #4 by sa2000
There may be tools / add-ons for auto updates when running as a service but these would be outside the scope of any support
The logs show a crash on the 15th September which arose after running out of system resources - perhaps the memory usage climbed to 2Gb - we would need to add some extra logging to troubleshoot
Ensure Debug Logging remains enabled
Please add this registry setting for the local user where Plex Service runs in
Stop Plex
Ensure all Plex processes (except for the Update Service) have exited
In RegEdit whilst logged into the windows account that the Plex Service runs under, find
*KEY_CURRENT_USER\Software\Plex, Inc.\Plex Media Server*
Right Click on Plex Media Server
Select New → DWORD (32-bit) value
and name the entry LogMemoryUse
and set the value to 1
Start Plex (Plex Service Tray app)
Wait for next crash and then capture the logs
On a crash we attempt to upload the crash reports to back end systems - this does not always succeed but we copy the files to the %TEMP% directory
When we run out of memory - the crash reports tend to end up being zero bytes long - and this was probably the case here
The logs show crash reports with these file name prefixes were created
Sep 15, 2021 01:13:05.298
ed6063c1-89d2-4302-9b4a-78c27082bade
Sep 12, 2021
7468e3e2-3eef-4cd1-b010-6229fc207cc2
219b48b9-21c9-4fcc-85c1-3e57adfd545b
Sep 09, 2021
81f30b47-f615-4ec9-8d82-72cc317e9fd6
Sep 06, 2021
8b7a46d3-fbfa-46ae-98d0-ea32c3ee3089
Could you look in the %TEMP% directory for these - not sure if there would be a filename extension - could be no extension or .dmp
If you find them - zip them and send me the zip
If you get a new crash look for similarly named files in the %TEMP% directory and zip and send with the logs zip
