[Crash - Nightly] - 1.15.3.876, 1.15.4.919, 1.15.4.994, 1.15.8.1198 and 1.16.1.1291- Windows Plex PMS - Plex Media Scanner has stopped working

Server Version#:1.15.3.876
Player Version#:N/A

For two days in a row since upgrading to new public version release listed above, both days “Plex Media Scanner has stopped working” during early hours nightly Plex maintenance window.

System:
Windows 7 - 64bit

Log Name: Application
Source: Application Error
Date: 4/7/2019 3:09:20 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: OSCAR
Description:
Faulting application name: Plex Media Scanner.exe, version: 1.15.3.876, time stamp: 0x5ca5a6ca
Faulting module name: ntdll.dll, version: 6.1.7601.24387, time stamp: 0x5c7f3802
Exception code: 0xc0000374
Fault offset: 0x000ce9a3
Faulting process id: 0x76b8
Faulting application start time: 0x01d4ed29f69ae8c0
Faulting application path: D:\Program Files (x86)\Plex\Plex Media Server\Plex Media Scanner.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 358474bd-591d-11e9-a495-382c4a6f0785
Event Xml:



1000
2
100
0x80000000000000

1788444
Application
OSCAR



Plex Media Scanner.exe
1.15.3.876
5ca5a6ca
ntdll.dll
6.1.7601.24387
5c7f3802
c0000374
000ce9a3
76b8
01d4ed29f69ae8c0
D:\Program Files (x86)\Plex\Plex Media Server\Plex Media Scanner.exe
C:\Windows\SysWOW64\ntdll.dll
358474bd-591d-11e9-a495-382c4a6f0785


Well, after three nights of consistent Plex Media Scanner crashes within 10-15 minutes of scheduled Plex maintenance task time window, I rolled back to Plex Windows PMS 1.15.2.793.

Problem solved.

How did you roll back to a older version…?

From the most recent previous stable version located under: C:\PlexAppData\Plex Media Server\Updates\

You have to stop the PMS that is currently running, then to go “Add/Remove Programs” and remove the current version, then install the most previous stable version under the folder path above.

Then you’re good to go with a more stable, recent previous version.

Decided to try 1.15.4.919 after 1.15.3.876 was crashing on Plex Media Scanner during the overnight maintenance window time. Well, 1.15.4.919 does the same thing. So will I ever be able to use a version of Windows Plex PMS after my last working version of 1.15.2.793 on my Windows 7 x64 system that won’t crash every night on Plex Media Scanner?

Really interesting as I’ve been having the same issue (1.15.4.919) and have narrowed it down to PMS scheduled tasks. I’ve disabled them for now and server no longer crashes / hangs but not really a long term fix.

I’ll rollback to previous version if not addressed in next release.

So I’m checking in with anyone running Windows 7 Pro x64 Plex Pass PMS with “Public” release versions after 1.15.2.793: Are you getting through the overnight PMS scheduled tasks without “Plex Media Scanner has crashed”? I’d like to hear from you. Thanks. TruckFan.

Experiencing the same with 1.15.4.993, Windows 10 1903 18362.53

Faulting application name: Plex Media Scanner.exe, version: 1.15.4.993, time stamp: 0x5cbdee62
Faulting module name: ntdll.dll, version: 10.0.18362.1, time stamp: 0x9bbcb4a9
Exception code: 0xc0000374
Fault offset: 0x000df8cd
Faulting process id: 0x46e4
Faulting application start time: 0x01d4fcd6ddfdabd7
Faulting application path: C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Scanner.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: e2a8dde7-5e4e-42bd-b113-55bd6a6e2f40
Faulting package full name:
Faulting package-relative application ID:

I upgraded just now to 1.15.4.994, and we’ll see how things go tonight for overnight PMS Scheduled Tasks and if Plex Media Scanner crashes.

There is a reported case of scanner heap corruption crashes (0xc0000374) when performing loudness deep analysis - logs captured just after the crash and before the scanner logs have recycled would help confirm if this is the same issue

1 Like

Well, same thing on 1.15.4.994 too. Am I being punished for still using Windows 7 x64 Professional? I rolled back again to 1.15.2.793.

sa2000,
I’m sorry, I don’t have time to collect logs for this. But at least you are getting notice.

Thanks,
Scott

I am having the heap corruption issues as well. I experienced a crash mid day when my tasks run at night. If the issue is truly around the scheduled tasks, I have them set to run when media is added which fits the symptoms. Is there a fix being worked on? I built an entirely fresh server to try to remedy this a week or so ago but no luck :frowning:

Version 1.15.4.994

Windows 10 Pro of some sorts

CONTEXT: (.ecxr)
eax=1b5aeafc ebx=771e4948 ecx=00000001 edx=771e4910 esi=00000002 edi=0c16a218
eip=771aa2b9 esp=1b5aead8 ebp=1b5aeb6c iopl=0 nv up ei pl zr na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246
ntdll!RtlReportCriticalFailure+0x88:
771aa2b9 eb36 jmp ntdll!RtlReportCriticalFailure+0xc0 (771aa2f1)
Resetting default scope

FAULTING_IP:
ntdll!RtlReportCriticalFailure+88
771aa2b9 eb36 jmp ntdll!RtlReportCriticalFailure+0xc0 (771aa2f1)

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 771aa2b9 (ntdll!RtlReportCriticalFailure+0x00000088)
ExceptionCode: c0000374
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 771e4910

BUGCHECK_STR: HEAP_CORRUPTION

DEFAULT_BUCKET_ID: HEAP_CORRUPTION

PROCESS_NAME: Plex Media Server.exe

ERROR_CODE: (NTSTATUS) 0xc0000374 - A heap has been corrupted.

EXCEPTION_CODE: (NTSTATUS) 0xc0000374 - A heap has been corrupted.

EXCEPTION_CODE_STR: c0000374

EXCEPTION_PARAMETER1: 771e4910

WATSON_BKT_PROCSTAMP: 5ccc8173

WATSON_BKT_PROCVER: 1.15.4.994

PROCESS_VER_PRODUCT: Plex Media Server

WATSON_BKT_MODULE: ntdll.dll

WATSON_BKT_MODSTAMP: 7b4896c1

WATSON_BKT_MODOFFSET: da2b9

WATSON_BKT_MODVER: 10.0.16299.936

MODULE_VER_PRODUCT: Microsoft® Windows® Operating System

BUILD_VERSION_STRING: 16299.637.x86fre.rs3_release_svc.180808-1748

ANALYSIS_SESSION_HOST: MAGNETAR

ANALYSIS_SESSION_TIME: 05-13-2019 17:41:06.0983

ANALYSIS_VERSION: 10.0.18869.1002 x86fre

THREAD_ATTRIBUTES:
ADDITIONAL_DEBUG_TEXT: Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]

FAULTING_THREAD: ffffffff

THREAD_SHA1_HASH_MOD_FUNC: aaac7d1c0cadeb665c2426cb05d2a9acf10230b4

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: b7657b1145246e74cd3abfa76bca6eab40720a27

OS_LOCALE: ENU

PRIMARY_PROBLEM_CLASS: HEAP_CORRUPTION

PROBLEM_CLASSES:

ID:     [0n262]
Type:   [HEAP_CORRUPTION]
Class:  Primary
Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
        BUCKET_ID
Name:   Add
Data:   Omit
PID:    [Unspecified]
TID:    [0x3c50]
Frame:  [0] : ntdll!RtlReportCriticalFailure

LAST_CONTROL_TRANSFER: from 771b29d9 to 771aa2b9

STACK_TEXT:
00000000 00000000 heap_corruption!Plex_Media_Server.exe+0x0

THREAD_SHA1_HASH_MOD: ca4e26064d24ef7512d2e94de5a93c38dbe82fe9

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: heap_corruption!Plex_Media_Server.exe

Same here…

Problem signature:
Problem Event Name: APPCRASH
Application Name: Plex Media Scanner.exe
Application Version: 1.15.4.993
Application Timestamp: 5cbdee62
Fault Module Name: LIBEAY32.dll
Fault Module Version: 1.0.2.16
Fault Module Timestamp: 5c8275d0
Exception Code: c0000005
Exception Offset: 0006b176
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

hope this can help…

I have responded to your duplicate post here Plex Media Server crashing every 24 hours - reinstall, rollback does not solve - #10 by sa2000

Would need logs for time of the crash - crash reports should get uploaded (if enabled) on restart. There was an issue in last week where this was not happening - a restart now should flush the backlog

Please run with debug logging enabled - settings / server / general / show advanced

Also crash reporting enabled

Restart the server and on next crash capture the logs zip and attach

Logs are still not being generated. I see folders in the %LOCALAPPDATA%\Plex Media Server\Crash Reports but they are empty. This time I had all schedule tasks off except for some of the maintenance tasks during scheduled maintenance. I believe it occurred during the maintenance window just by looking at Tautulli play history logs. I have used plex for like 8 years and haven’t even had this type of trouble.

I did say earlier that i was responding to your duplicate post Plex Media Server crashing every 24 hours - reinstall, rollback does not solve - #10 by sa2000 - so as you are continuing here, I will close the other topic and we can continue here.

To make sure we have continuity, this was my response which I posted 9 days ago

would need to see debug logs from the server for the period leading to the crash and need the full dmp file please - this can be uploaded somewhere and link sent to me by private message. Would need corresponding logs and dmp. Automatic crash reporting normally does not work with heap corruptions - but logs captured after the restart after the crash would show if the dmp was ok or not uploaded

With regards to this

I see folders in the %LOCALAPPDATA%\Plex Media Server\Crash Reports but they are empty.

What about this folder
%LOCALAPPDATA%\Plex Media Server\Logs

Also please export the windows Application Event Log filtered on event ids 1000,1001

%LOCALAPPDATA%\Plex Media Server\Logs has logs in it as normal. I will grab the most recent ones once another event occurs. With automatic update disabled from my scheduled tasks and all of the thumbnail/loudness/chapter tasks disabled, I have yet to have an issue. I will turn them on slowly one by one until I can recreate the issue.

Obviously there was a misunderstanding as these two statements are contradictory

Please ensure you run with debug logging enabled
See
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/

Restart the server once you know debug logging is enabled so that a fresh set of logs get created

After this when you get a crash. note down the time and restart the Plex Media Server and then use the web interface to download the logs zip
See
https://support.plex.tv/articles/200250417-plex-media-server-log-files/

Then please launch windows Event Viewer (eventvwr.exe) and open Windows Logs and select Application and filter the log for Event IDs 1000,1001 and save the filtered log as evtx file and zip and attach with the zipped logs.

Thanks