Thank you for the logs and dumps. The 2nd dump file was 0 bytes size - but it does not matter - sounds same issue as in the earlier set of diagnostics
It appears that some scanner processes are hanging overnight when running analysis / metadata refreshes as part of scheduled tasks. So we need to look into those by getting files that the scanner hung on and then see if it can reproduced and referred to the development team
There appears a second issue in that on exiting Plex Media Server, the attempt to kill and terminate those Plex Media Scanner processes does not seem to work and database locks remain stopping shutdown from completing
When this happened and you took the process dump, did you notice 3 Plex Media Scanner.exe processes still running in task manager in first case and 4 processes for the 2nd ?
You could filter the Windows Application Log for events 1000,1001 and see if there were any Plex Media Scanner.exe exceptions
Is this Windows 10 ? or Windows Server ?
I have sent you the paths for the media files that the scanner jobs were stuck on
So if you can get me these files - and send me link by private message, I will see if I can repro the problem
There was also a hang when starting to process this directory
F:\tvshows\Brooklyn Nine-Nine\Season 7
In case I cannot replicate, the next time this happens and you have scanner processes hung from many hours before, you could after securing all the logs, force process dumps for the scanner processes that are stuck
Yes when those crashes happened I tries end tasking PMS and noticed there were multiple PM scanners running , and attempted to end task them which did not work.
All of these crashes make the computer unable to “software restart” , that is , Windows never manages to close them to be able to reboot. Which is terrrrible since I often can only remotely manage the server.
Thanks for your PM. So you got a hang similar to what the scanner was encountering when attempting to copy these files. Sounds like disc drive issues but I would expect that there would be some windows event log entries within the SYSTEM event log for any disc I/O errors. Or may it just hangs. What is the F Drive? Internal / external ?
Suggest running an integrity check and also surface read scan of all blocks and any other system tests available from the drive manufacturer