# My plex server crashes everyday

**URL:** <https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727>\
**Category:** Plex Media Server\
**Tags:** server-windows\
**Created:** [April 3, 2022, 11:32am UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727 "2022-04-03T11:32:40Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zildjian91](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/zildjian91/32/273533_2.png) [@Zildjian91](https://forums.plex.tv/u/Zildjian91)\
**Post date:** [April 3, 2022, 11:32am UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/1 "2022-04-03T11:32:40Z")

</div>

Server Version#: 1.25.8.5663,

My plex server crashes everyday. This is on a fresh install of Windows 10.  
Can someone please help?

Faulting application name: Plex Media Server.exe, version: 1.25.8.5663, time stamp: 0x62386c02  
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x82dc99a2  
Exception code: 0xc0000409  
Fault offset: 0x0009eddb  
Faulting process id: 0x21f4  
Faulting application start time: 0x01d8467ac5bd8c11  
Faulting application path: C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe  
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll  
Report Id: bfe627d3-4905-4a77-86d9-ac49a8cf6761  
Faulting package full name:  
Faulting package-relative application ID:

---

<div class="post-metadata">

**Author:** ![Olli](https://avatars.discourse-cdn.com/v4/letter/o/919ad9/32.png) [@Olli](https://forums.plex.tv/u/Olli)\
**Post date:** [April 3, 2022, 11:36am UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/2 "2022-04-03T11:36:43Z")

</div>

> [@Plex keeps crashing/closing](https://forums.plex.tv/t/plex-keeps-crashing-closing/723437/68):
>
> I have sent a development 1.26.0.5703 to a number of users where I have confirmed this crash I can make it available to others if I get confirmation of the same crash arising - that would be either debug [server logs](https://support.plex.tv/articles/200250417-plex-media-server-log-files/) and zipped crash dump (sent privately) or screenshot of Application Exception details showing in the WIndows Application Event Log viewed through Windows Event Viewer

---

<div class="post-metadata">

**Author:** ![Zildjian91](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/zildjian91/32/273533_2.png) [@Zildjian91](https://forums.plex.tv/u/Zildjian91)\
**Post date:** [April 3, 2022, 11:40am UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/3 "2022-04-03T11:40:51Z")

</div>

You want me to send my logs to you?

---

<div class="post-metadata">

**Author:** ![Olli](https://avatars.discourse-cdn.com/v4/letter/o/919ad9/32.png) [@Olli](https://forums.plex.tv/u/Olli)\
**Post date:** [April 3, 2022, 11:47am UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/4 "2022-04-03T11:47:07Z")

</div>

No, not me.  
Is’s just a known Problem on Windows-PMS.  
You can switch the thread and ask @sa2000 or wait for a new build 1.26.1+ next week.

---

<div class="post-metadata">

**Author:** ![Zildjian91](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/zildjian91/32/273533_2.png) [@Zildjian91](https://forums.plex.tv/u/Zildjian91)\
**Post date:** [April 3, 2022, 11:51am UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/5 "2022-04-03T11:51:54Z")

</div>

> [@Olli](#):
>
> wn Problem on Windows-PMS.  
> You can switch the thread and ask @sa2000 or wait for a new build 1.26.1+ next week.

Ok, thanks for the help. Hope they fix it next week.

---

<div class="post-metadata">

**Author:** ![hellcowboy](https://avatars.discourse-cdn.com/v4/letter/h/7c8e57/32.png) [@hellcowboy](https://forums.plex.tv/u/hellcowboy)\
**Post date:** [April 4, 2022, 2:12am UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/6 "2022-04-04T02:12:49Z")

</div>

Hello,

So I wrote a PowerShell script for this issue as it was happening on my server and I thought I should share it.

```auto
$Process = Get-Process -Name "Plex Media Server" -ErrorAction SilentlyContinue
If ([string]::IsNullOrEmpty($Process)) {
    Start-Process -FilePath “C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe”
}

```

Then I setup a scheduled task to start running at midnight and run every 5 minutes after that. The action/program powershell with the arguements “-file “C:\Scripts\Check-PlexRunning.ps1” -ExecutionPolicy Bypass”.

Not a perfect solution but since my server seems to die in the middle of the night this script/setup keeps it running and the only thing the end user might see a error saying error retrieving this content or whatever and if they try again it will start right up without issue.

Any questions let me know.

---

<div class="post-metadata">

**Author:** ![sa2000](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/sa2000/32/6922_2.png) [@sa2000](https://forums.plex.tv/u/sa2000)\
**Post date:** [April 4, 2022, 8:47am UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/7 "2022-04-04T08:47:23Z")

</div>

> [@Zildjian91](#):
>
> My plex server crashes everyday. This is on a fresh install of Windows 10.  
> Can someone please help?

I have included you in the private message thread that will give you access to development build 1.26.1.5712 - which is looking good so far

---

<div class="post-metadata">

**Author:** ![Billy2025](https://avatars.discourse-cdn.com/v4/letter/b/ecb155/32.png) [@Billy2025](https://forums.plex.tv/u/Billy2025)\
**Post date:** [April 4, 2022, 2:32pm UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/8 "2022-04-04T14:32:12Z")

</div>

I have been experiencing the same for the past week myself. @sa2000 can I get the development build 1.26.1.5712 as well?

---

<div class="post-metadata">

**Author:** ![Krashkource](https://avatars.discourse-cdn.com/v4/letter/k/7ba0ec/32.png) [@Krashkource](https://forums.plex.tv/u/Krashkource)\
**Post date:** [April 4, 2022, 2:43pm UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/9 "2022-04-04T14:43:24Z")

</div>

I have the same issue and after running the .dmp file through WinDpg preview app I was able to get the following info. I hope this helps for correcting the buffer overrun detected by Windows. Oh and just to note this is Server 2012 R2 not Windows 8.1 running my current server.

EY\_VALUES\_STRING: 1

```
Key : Analysis.CPU.mSec
Value: 3359

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 7411

Key : Analysis.Init.CPU.mSec
Value: 749

Key : Analysis.Init.Elapsed.mSec
Value: 5035

Key : Analysis.Memory.CommitPeak.Mb
Value: 102

Key : FailFast.Name
Value: FATAL_APP_EXIT

Key : FailFast.Type
Value: 7

Key : Timeline.Process.Start.DeltaSec
Value: 316510

Key : WER.OS.Branch
Value: winblue_ltsb

Key : WER.OS.Timestamp
Value: 2016-01-24T00:53:00Z

Key : WER.OS.Version
Value: 6.3.9600.18217

Key : WER.Process.Version
Value: 1.25.8.5663

```

FILE\_IN\_CAB: Plex Media Server.exe.6540.dmp

NTGLOBALFLAG: 0

PROCESS\_BAM\_CURRENT\_THROTTLED: 0

PROCESS\_BAM\_PREVIOUS\_THROTTLED: 0

APPLICATION\_VERIFIER\_FLAGS: 0

CONTEXT: (.ecxr)  
eax=00000001 ebx=05b6fedc ecx=00000007 edx=00000000 esi=00000003 edi=05b6f43c  
eip=645a84cb esp=05b6f0c0 ebp=05b6f0d4 iopl=0 nv up ei pl nz na po nc  
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202  
ucrtbase!abort+0x4b:  
645a84cb cd29 int 29h  
Resetting default scope

EXCEPTION\_RECORD: (.exr -1)  
ExceptionAddress: 645a84cb (ucrtbase!abort+0x0000004b)  
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)  
ExceptionFlags: 00000001  
NumberParameters: 1  
Parameter[0]: 00000007  
Subcode: 0x7 FAST\_FAIL\_FATAL\_APP\_EXIT

PROCESS\_NAME: Plex Media Server.exe

ERROR\_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION\_CODE\_STR: c0000409

EXCEPTION\_PARAMETER1: 00000007

FAULTING\_THREAD: 0000136c

STACK\_TEXT:  
05b6f0d4 645a7dbb 4f42e2b0 05b6f43c 05b6f260 ucrtbase!abort+0x4b  
05b6f108 00446e94 656f3097 05b6f43c 05b6f260 ucrtbase!terminate+0x3b  
WARNING: Stack unwind information not available. Following frames may be wrong.  
05b6fee8 00342de1 c672eb5a 00342da0 04ca95e8 Plex\_Media\_Server+0x156e94  
05b6ff08 6455feff 04b2a2c0 4f42ecfc 6455fec0 Plex\_Media\_Server+0x52de1  
05b6ff44 75966a14 04ca95e8 759669f0 1beff0d1 ucrtbase!thread\_start\<unsigned int (\_\_stdcall\*)(void \*)\>+0x3f  
05b6ff58 77d8a9ff 04ca95e8 9841b8ac 00000000 kernel32!BaseThreadInitThunk+0x24  
05b6ffa0 77d8a9ca ffffffff 77d6fdd3 00000000 ntdll!\_\_RtlUserThreadStart+0x2f  
05b6ffb0 00000000 6455fec0 04ca95e8 00000000 ntdll!\_RtlUserThreadStart+0x1b

STACK\_COMMAND: ~8s ; .cxr ; kb

SYMBOL\_NAME: ucrtbase!abort+4b

MODULE\_NAME: ucrtbase

IMAGE\_NAME: ucrtbase.dll

FAILURE\_BUCKET\_ID: FAIL\_FAST\_FATAL\_APP\_EXIT\_c0000409\_ucrtbase.dll!abort

OS\_VERSION: 6.3.9600.18217

BUILDLAB\_STR: winblue\_ltsb

OSPLATFORM\_TYPE: x86

OSNAME: Windows 8.1

IMAGE\_VERSION: 10.0.14393.2990

FAILURE\_ID\_HASH: {e31753ac-c98a-8055-3663-47e707543d20}

## Followup: MachineOwner

---

<div class="post-metadata">

**Author:** ![Stakado](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@Stakado](https://forums.plex.tv/u/Stakado)\
**Post date:** [April 4, 2022, 8:04pm UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/10 "2022-04-04T20:04:21Z")

</div>

Same here, every night, between 21h and 23h GMT, my plex server closes itself since the last update, Versión 1.25.8.5663

---

<div class="post-metadata">

**Author:** ![frankkasten](https://avatars.discourse-cdn.com/v4/letter/f/49beb7/32.png) [@frankkasten](https://forums.plex.tv/u/frankkasten)\
**Post date:** [April 5, 2022, 2:31pm UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/11 "2022-04-05T14:31:23Z")

</div>

Same for me. Where’s fix?

---

<div class="post-metadata">

**Author:** ![Olli](https://avatars.discourse-cdn.com/v4/letter/o/919ad9/32.png) [@Olli](https://forums.plex.tv/u/Olli)\
**Post date:** [April 5, 2022, 3:41pm UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/12 "2022-04-05T15:41:03Z")

</div>

while it looks good, hopefully tomorrow when @sa2000 is back.

meanwhile you can try to disable maintainance jobs (daily / 3 days) until the new release is there.

---

<div class="post-metadata">

**Author:** ![EAGLEi222](https://avatars.discourse-cdn.com/v4/letter/e/90ced4/32.png) [@EAGLEi222](https://forums.plex.tv/u/EAGLEi222)\
**Post date:** [April 5, 2022, 4:03pm UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/13 "2022-04-05T16:03:55Z")

</div>

This has happened to me now two days in a row and I see I am not alone.

April 4, 2022 at 4:27 am CDT  
April 5, 2022 at 10:21 am CDT

Faulting application name: Plex Media Server.exe, version 1.25.8.5663  
Faulting module name: ucrtbase.DLL, version 10.0.19041.789

Source: Application error

Glad to hear a fix is in progress

---

<div class="post-metadata">

**Author:** ![2ndreality](https://avatars.discourse-cdn.com/v4/letter/2/7cd45c/32.png) [@2ndreality](https://forums.plex.tv/u/2ndreality)\
**Post date:** [April 5, 2022, 6:30pm UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/14 "2022-04-05T18:30:09Z")

</div>

I’m having the same issue, good to hear it isn’t just me. Have used Plex for years now, this issue is sudden with the current build.

---

<div class="post-metadata">

**Author:** ![sa2000](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/sa2000/32/6922_2.png) [@sa2000](https://forums.plex.tv/u/sa2000)\
**Post date:** [April 6, 2022, 7:42am UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/15 "2022-04-06T07:42:26Z")

</div>

All

I am pleased to say that the fixes in development release 1.26.1.5712 that have fixed the Plex Media Server crashes with 0xc0000409 in ucrtbase.dll have now been ported back into the 1.25.9 beta and the release of 1.25.9.5721 made available yesterday has these fixes

Release Notes:

> [@Plex Media Server](https://forums.plex.tv/t/plex-media-server/30447/496):
>
> Plex Media Server 1.25.9.5721 is now available to Plex Pass users in the Beta update channel. NEW: (Series Scanner) Allow the server owner to create “.plexmatch” files providing hints for more accurate matching of nonstandard file naming schemes (#13211) see details at [Match Hinting for TV Series | Plex Support](https://support.plex.tv/articles/plexmatch/) (Web) Updated to 4.76.1 FIXES: (AdDetector) Fix potential crash (#13421) (PubSub) A pubsub server with sub-optimal latency could be selected (#13480) (Scanner) Improved parsing of …

- Fix for Window related EventSource crashes (#13437)

---

<div class="post-metadata">

**Author:** ![markus.will](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/markus.will/32/24031_2.png) [@markus.will](https://forums.plex.tv/u/markus.will)\
**Post date:** [April 6, 2022, 9:21am UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/16 "2022-04-06T09:21:17Z")

</div>

Nice to read. A quite fix fix. 😉

But… when trying to update no newer version than 1.25.8.5663 is found - nether at my local Plex nor on your download page. When will it be available for common?

---

<div class="post-metadata">

**Author:** ![sa2000](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/sa2000/32/6922_2.png) [@sa2000](https://forums.plex.tv/u/sa2000)\
**Post date:** [April 6, 2022, 10:30am UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/17 "2022-04-06T10:30:55Z")

</div>

> [@markus.will](#):
>
> When will it be available for common?

very soon - may even be today.  
Currently beta only for Plex Pass users

---

<div class="post-metadata">

**Author:** ![tom9933](https://avatars.discourse-cdn.com/v4/letter/t/51bf81/32.png) [@tom9933](https://forums.plex.tv/u/tom9933)\
**Post date:** [June 13, 2022, 2:12am UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/18 "2022-06-13T02:12:35Z")

</div>

I’m still having what sounds like a similar issue and I just checked, my Windows 11 server is running Version 1.26.2.5797. I assume I should have the fix?

---

<div class="post-metadata">

**Author:** ![sa2000](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/sa2000/32/6922_2.png) [@sa2000](https://forums.plex.tv/u/sa2000)\
**Post date:** [June 13, 2022, 7:49am UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/19 "2022-06-13T07:49:58Z")

</div>

> [@tom9933](#):
>
> I’m still having what sounds like a similar issue and I just checked, my Windows 11 server is running Version 1.26.2.5797. I assume I should have the fix

That specific crash has already been fixed. Is this happening on both servers or just the windows PMS ?

I cannot see any uploaded crash reports for your account

Best to get debug [server logs](https://support.plex.tv/articles/200250417-plex-media-server-log-files/) captured after one of these crashes and if it is on windows, then look into the %TEMP% directory for dump files created at the time of the time of the crash - the filenames will not have any file extension and will have a name of random characters with dashes

---

<div class="post-metadata">

**Author:** ![dhomas](https://avatars.discourse-cdn.com/v4/letter/d/7ba0ec/32.png) [@dhomas](https://forums.plex.tv/u/dhomas)\
**Post date:** [August 31, 2022, 4:56pm UTC](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727/20 "2022-08-31T16:56:52Z")

</div>

I just saw what seems to be a similar crash this morning after updating to version 1.28.2.6151 yesterday.

I recognized it right away since I was also getting this issue before the patch and my last crash was on April 4th on version 1.25.9.5673, right before applying the fix.

Today, on version 1.28.2.6151, I got a similar crash with “code c0000409” on ucrtbase. Might it be regression on the previous fix?

Here is the analysis of today’s dmp file:

```auto
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 2156

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 2260

    Key : Analysis.Init.CPU.mSec
    Value: 421

    Key : Analysis.Init.Elapsed.mSec
    Value: 5204

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 103

    Key : FailFast.Name
    Value: FATAL_APP_EXIT

    Key : FailFast.Type
    Value: 7

    Key : Timeline.Process.Start.DeltaSec
    Value: 51295

    Key : WER.OS.Branch
    Value: vb_release

    Key : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key : WER.OS.Version
    Value: 10.0.19041.1

    Key : WER.Process.Version
    Value: 1.28.2.6151

FILE_IN_CAB: Plex Media Server.exe.2788.dmp

NTGLOBALFLAG: 0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: (.ecxr)
eax=00000001 ebx=1fffffff ecx=00000007 edx=000001e9 esi=00000003 edi=0207e118
eip=75beeddb esp=0748e3a8 ebp=0748e3bc iopl=0 nv up ei pl nz na po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
ucrtbase!abort+0x4b:
75beeddb cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 75beeddb (ucrtbase!abort+0x0000004b)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 00000007
Subcode: 0x7 FAST_FAIL_FATAL_APP_EXIT 

PROCESS_NAME: Plex Media Server.exe

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 00000007

FAULTING_THREAD: 00002de0

STACK_TEXT:  
0748e3bc 75bee17b 4079455c 0207e118 0000000a ucrtbase!abort+0x4b
0748e3ec 71fd3097 0207e118 0000000a 0748e40c ucrtbase!terminate+0x3b
0748f578 00e4d76a 0002c233 37a5f97d 01683f20 VCRUNTIME140!_NLG_Return
WARNING: Stack unwind information not available. Following frames may be wrong.
0748f658 00e4fb25 0748f754 00e4fb25 00000003 Plex_Media_Server!essentia::Configurable::name+0x80a4a
0748f670 00df0618 0d6433c0 37a5f98d 064c8898 Plex_Media_Server!essentia::Configurable::name+0x82e05
0748f6a8 01683f72 0748f700 37a5f9d5 01683f20 Plex_Media_Server!essentia::Configurable::name+0x238f8
0748f6f0 01684fa2 01f9dec8 00000000 0d6433b0 Plex_Media_Server!sqlite3_spellfix_init+0x4d8d2
0748f748 01684ec3 064c8894 00001cf0 01684ec3 Plex_Media_Server!sqlite3_spellfix_init+0x4e902
0748f7b0 01684da4 064c8898 0748f7e0 37a5f71d Plex_Media_Server!sqlite3_spellfix_init+0x4e823
0748f838 00df4113 008b4558 06e9bdd8 0748f86c Plex_Media_Server!sqlite3_spellfix_init+0x4e704
0748f8b4 01684869 008b4558 0748f8d8 0748f918 Plex_Media_Server!essentia::Configurable::name+0x273f3
0748f944 0168408f 0748f960 135f4588 0c54b300 Plex_Media_Server!sqlite3_spellfix_init+0x4e1c9
0748f974 70464728 4405cc71 135f4588 70464707 Plex_Media_Server!sqlite3_spellfix_init+0x4d9ef
0748f99c 75b94f9f 0c54b300 40795f64 75b94f60 boost_thread!boost::detail::get_current_thread_data+0x103
0748f9d4 763cfa29 135f4588 763cfa10 0748fa40 ucrtbase!thread_start<unsigned int (__stdcall*)(void *),1>+0x3f
0748f9e4 77787b5e 135f4588 423c46f5 00000000 kernel32!BaseThreadInitThunk+0x19
0748fa40 77787b2e ffffffff 777a8cab 00000000 ntdll!__RtlUserThreadStart+0x2f
0748fa50 00000000 75b94f60 135f4588 00000000 ntdll!_RtlUserThreadStart+0x1b

SYMBOL_NAME: ucrtbase!abort+4b

MODULE_NAME: ucrtbase

IMAGE_NAME: ucrtbase.dll

STACK_COMMAND: ~44s ; .cxr ; kb

FAILURE_BUCKET_ID: FAIL_FAST_FATAL_APP_EXIT_c0000409_ucrtbase.dll!abort

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x86

OSNAME: Windows 10

IMAGE_VERSION: 10.0.19041.789

FAILURE_ID_HASH: {e31753ac-c98a-8055-3663-47e707543d20}

Followup: MachineOwner
---------

```

Here are the results of the last time I had a similar crash on the pre-fix version of PMS, back on April 4th:

```auto
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 2078

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 2156

    Key : Analysis.Init.CPU.mSec
    Value: 390

    Key : Analysis.Init.Elapsed.mSec
    Value: 8599

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 77

    Key : FailFast.Name
    Value: FATAL_APP_EXIT

    Key : FailFast.Type
    Value: 7

    Key : Timeline.Process.Start.DeltaSec
    Value: 259280

    Key : WER.OS.Branch
    Value: vb_release

    Key : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key : WER.OS.Version
    Value: 10.0.19041.1

    Key : WER.Process.Version
    Value: 1.25.9.5673

FILE_IN_CAB: Plex Media Server.exe.3148.dmp

NTGLOBALFLAG: 0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: (.ecxr)
eax=00000001 ebx=07e8f848 ecx=00000007 edx=000001e9 esi=00000003 edi=07e8eee0
eip=76e8eddb esp=07e8eb68 ebp=07e8eb7c iopl=0 nv up ei pl nz na po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
ucrtbase!abort+0x4b:
76e8eddb cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 76e8eddb (ucrtbase!abort+0x0000004b)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 00000007
Subcode: 0x7 FAST_FAIL_FATAL_APP_EXIT 

PROCESS_NAME: Plex Media Server.exe

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 00000007

FAULTING_THREAD: 000026ec

STACK_TEXT:  
07e8eb7c 76e8e17b 169fa336 07e8eee0 07e8ed04 ucrtbase!abort+0x4b
07e8ebac 00906ee4 728c2fe7 07e8eee0 07e8ed04 ucrtbase!terminate+0x3b
WARNING: Stack unwind information not available. Following frames may be wrong.
07e8f854 00802e41 61e0756e 00802e00 06f5e9c0 Plex_Media_Server+0x156ee4
07e8f874 76e34f9f 072bbf68 169fb036 76e34f60 Plex_Media_Server+0x52e41
07e8f8ac 759efa29 06f5e9c0 759efa10 07e8f918 ucrtbase!thread_start<unsigned int (__stdcall*)(void *),1>+0x3f
07e8f8bc 77aa7a7e 06f5e9c0 17e97e17 00000000 kernel32!BaseThreadInitThunk+0x19
07e8f918 77aa7a4e ffffffff 77ac8a4c 00000000 ntdll!__RtlUserThreadStart+0x2f
07e8f928 00000000 76e34f60 06f5e9c0 00000000 ntdll!_RtlUserThreadStart+0x1b

STACK_COMMAND: ~7s ; .cxr ; kb

SYMBOL_NAME: ucrtbase!abort+4b

MODULE_NAME: ucrtbase

IMAGE_NAME: ucrtbase.dll

FAILURE_BUCKET_ID: FAIL_FAST_FATAL_APP_EXIT_c0000409_ucrtbase.dll!abort

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x86

OSNAME: Windows 10

IMAGE_VERSION: 10.0.19041.789

FAILURE_ID_HASH: {e31753ac-c98a-8055-3663-47e707543d20}

Followup: MachineOwner
---------

```

They are not quite identical, but similar enough that it made me think of this thread.

I have the entire dmp file, if helps, though I don’t know if it contains any personally identifying information.

Also, if I should create a new thread for this, let me know. Thanks for any help!

Regards,

D

[Next page](https://forums.plex.tv/t/my-plex-server-crashes-everyday/785727.md?page=2)
