Plex media scanner has stopped working

Server Version#: 1.14.1.5488 (latest)
Player Version#:unsure.

I am constantly getting the error ‘Plex media server has stopped working’. This occurs several times a day, and I have to delete all the warnings each time I open my PC. The server itself seems to be working just fine so it’s more of an annoyance that anything.
I have scanned my PC for each of the ‘rouge’ .dll files and do not have any of them present.
I have deleted Plex, and reinstalled from scratch also.
I have read he other posts about the same issue, but each solution has not worked for me, plus these were all over a year old so I am running the latest release which presumably has the ‘fix’?
Any suggestions would be grateful. Pete

Plex%20Media%20scanner%20issue

1 Like

I’m getting a similar error. No errors previously but it started recently.
Sounds like another memory error like, after reading a lot, happened in 2017.

@jdheil… did you manage to fix this? I am still getting this annoying error every day. I travel a lot and when I get home there must be dozens of open windows with the same error message that I have to close.
I really hope this can be fixed. Again, it was fine for years until recently, but I cannot nail down an event that may have triggered it. Delete and re-load Plex has not worked… Aggggg!

Same issue here. Windows 7 machine running PMS Version 1.15.2.793, but this started happening a few versions ago (I only just went to 1.15.x from 1.14.x, so it was happening then). I anyone from plex wants my logs, let me know and I’ll send them to you. I did notice hundreds of these lines in “Plex Media Scanner Analysis.log”

Apr 08, 2019 20:02:01.591 [13796] DEBUG - [FFMPEG] - Skipping B slice due to open GOP
Apr 08, 2019 20:02:01.598 [13796] DEBUG - [FFMPEG] - Skipping P slice due to !sync

Same here, OS is Windows 7, latest Plex.
Any Idea / help very appreciated

I’ve been trying to investigate this further, but I haven’t solved it yet. I tried running Plex Media Scanner in command line mode.

I first tried this:

"Plex Media Scanner.exe" --scan --refresh --verbose

I would occasionally get stuck on a file. I checked the files themselves and didn’t find anything, but sometimes renaming them would let it pass those files. But eventually, it always got stuck.

So I tried going through each and every library by first using --list to find the numbers of them. Then I did:

"Plex Media Scanner.exe" --scan --refresh --verbose --section 2

For each library. And it got through all of them successfully! Then I tried just doing --scan and it got through all of that just fine. Then just --refresh and again it got stuck, though I’m not sure where.

I’m wondering if there’s a deleted library in the database it’s getting stuck on, or something like that. It’s really weird that it can go through ALL of the libraries one at a time just fine, but when doing them all at once (without the --section flag), it gets stuck.

I’ve gone through all of the “plex media scanner.log” files, but I don’t see anything obvious.

Any suggestions on where to go next? This is really frustrating.

OK, no joy yet. So let me try this as a “solution”… how do I stop Plex from even running the media scanner on its own? I want to keep the Plex server running, but I don’t want it to run “Plex Media Scanner”. Thoughts?

Same issue over here as well. I never had any issues until about two weeks ago when I updated my Plex. I tried to remove it and install an older version again, but this didn’t solve the problem.
I updated my PMS a few times now, hoping this issue would be fixed in an update, but no luck until this far.

Is there anyone from staff who can help us with this?

I am getting the same thing. Nightly crashes, usually a couple per night. Win error logs go back to April when this started occurring repeatedly.
Beginning with:
Faulting application name: Plex Media Scanner.exe, version: 1.15.3.876
Current version:
Faulting application name: Plex Media Scanner.exe, version: 1.15.6.1079
Usually 2-4am.
There seems to be a lot of FFMPG references in the logs, but I am not sure what I am looking for.
Would welcome some suggestions to narrow down a file fault or something.

Well, I disabled verbose. When I got the 2 new errors this morning, I pulled event viewer, got the timestamps, and pulled the nearest scanner logs (Plex Media Scanner Deep Analysis 1-5). The Regular PMS Analysis logs seem to indicate issues with some of my audiobooks.
They were from iTunes, I think… My Blood of Kerensky series, and HPLovecraft show as download available, but the Thrawn trilogy is not, so I am not sure on those books.
They are all m4b.
FTR Win7.
I have removed them from the directory, so I will see what happens tomorrow morning.

OK, well I checked Monday evening and no crash reports. So it seems the QAudiobooks were the culprit.

Well, yet another day without Scanner crashes, so I think the files were likely the issue. Curious as to why.

My errors (9 to be precise) showed up at 22:04:53 to 22:04:58 on my event viewer, however the deep analysis log was last updated 8:00 this morning.
I have so much logs, I don’t know where to look. Some of them log stuff at 22:04:30, but nothing around 53 to 58 seconds

Having the same issue. Looking into the logs and deep logs don’t show anything “bad” at the time of the crash. I have no idea what I’m looking for in the logs. How do I find the problem. My old server never had this issue, my new one does. Same OS, same hardware, just rebuilt it.

Also on a side note I found that the “send crash reports” option doesn’t actually work because in the logs it shows that where they are posting the reports returns a 400 error.

I am having the same issue, the Plex Scanner is crashing everyday. I am running Windows 7, I believe it actually started about 2 updates ago. I have been using plex for several years and have never had this issue.

I tried downgrading but this didn’t help unfortunately.

I’ve had it happen a few times but its random.
hasn’t crashed in two days… Windows 7 Ultimate

I still have this issue, when are they going to fix this? It’s very annoying!

Still happening to me. Updated to latest beta version (1.16.3.1433) and still the same.
Really needs to be fixed.