These are memory heap corruption crashes c0000374 and with such crashes, most of the time it is not possible for the crashing application itself to geneate a crash report
Premium Music Libraries have some advanced matching features which include generating a short fingerprint wav file which I believe is used as part of the identification process.
So what is my next move? I canāt afford to completely reinstall, as I would need to rerun all of the transcoding, so Iām very concerned about this.
Is it that your PC cannot cope with a lot of CPU usage and overheats and crashes out or is there a bug in Plex Media Server/Scanner that is leading to the crashes
If it is the former, then you need to check out cooling and minimize transcoding and if having a Premium Music Library makes it worse, then delete that library and create a Basic Music Library
If it is the latter, then we need to get closer to the issue. Which means capturing a dmp file and the associated scanner/server logs that covered the crash period. From there we can look at getting sample files to try and reproduce. To get here you may need to increase the number of log files to say 50 and to check for crashes in the event log and capture the logs as soon as you realize and configure windows so as it create the dmp file
My PC has only crashed out twice when doing a combination of overnight transcoding (outside of PLEX) and simultaneously transcoding a large number of new music additions. I can mange this process now that I know it is an issue.
My PC has not hardware crashed at any time during this discussion with you (over the past month).
Having said that, I will increase the log files to 100 and configure windows to create a dmp file. Since I get a āscanner crashā every night, I have to assume that the next morning Iāll have the appropriate crash files automatically available.
I noticed that the .dmp files and the entire dump process (whether Windows or Plex) relate to SERVER CRASHES. Iām having SCANNER crashes - will this actually report anything?
Iāve set the LogNumFiles registry key to 100 and Iāve created a LocalDumps registry key. Weāll see what we have captured over the Holiday. Please note that my Plex server runs 24/7, so we should not lose any data.
It should do - unless windows itself also would have issues generating a dump file when there is heap corruption
When providing the links to where you upload the evidence - may be to big for forum, please also include extracts from the application event log showing all exceptions for Plex Media Scanner.exe and Plex Media Server.exe and times of these events
Iāve been having Plex Media crashes every night as well. Running Windows Server 2012r2 with latest Plex Bata. I have included Plex logs and photo of error.Plex Media Server Logs_2018-11-29_15-37-24.zip (3.7 MB)
Did you mean to provide logs that are 2 weeks old?
Your post is dated 12th December. Your logs are from 29th November.
Regardless, for scanner crashes we need to identify the file that is getting the crash when scanned. So what would be important is capturing logs that include scanner logs for the time of a crash.
You will see from earlier dialogue in this forum thread that this is not easy and would most likely need increasing the number of log files and also making the registry changes to get windows to produce the dmp files for the crashes.
Go through the earlier dialogue in this forum thread and follow the advice given. Need to capture scanner and scanner analysis logs that cover the times of the crashes in the application event log
Just to help users that have Windows server and are getting these crashes I was able to fix the problem by installing Windows Server Media Service via Rolls Manager. I also installed Windows Server Essentials Media Pack from the Microsoft website and the errors completely cleared up.
