Server Version#: After 1.31.0.6654
Any version after this one, like 1.31.1.6716 or 1.3.2.6739 ends up crashing in the middle of the night during maintenance. Anyone else see this?
2 Likes
I am seeing this issue. Looks like a new version was installed on or around 2/19 for me. Since then Plex crashes entire windows 11 PC about 1 hour 20 minutes into daily maintenance. Windows 11 Pro PC is completely locked up, the screen is black and PC is non-responsive. It will not respond to pings and canāt be accessed via Remote Desktop either. I need to hard power the PC down to restart it.
Daily scheduled tasks were scheduled between 1 - 6AM for Plex, the PC would crash around 2:20AM. I moved maintenance window to 3 - 8 AM and PC crashed around 4:20AM. I just moved maintenance to 12PM-6PM and sure enough PC crashed at 1:08PM today. (I am pinging PC every 5 minutes to log when it stops responding)
I just enabled debug logging, hopefully there will be something useful in the logs.
Alsoā¦ I saw similar behavior about a year ago, but that cleared up after several months and things were smooth until now.
2 Likes
Seeing the same thing here on Server Version 1.31.1.6733.
Seems to be doing this almost nightly, but no luck tracking down exactly what was going on. I did see in the Plex logs some crash reports everytime after the reboot but not seeing anything that is stick out exactly what is causing the crash.
1 Like
I disabled intro & credit skipping and maintenance completed without crashing PC. I will leave them off overnight to see if PC is still working in the morningā¦
My Plex PC did not crash overnight after I disabled both intro & credit skipping. Can someone else try this and let me know if this fixes their issue?
Iām having the same issue. My Win11Pro 22H2 OS is crashing with āclock_watchdog_timeoutā BSOD at the Plex sched task. Total hang, no minidump generated. Will try disabling intro/credits sched-tasks.
Spam folder wasnāt sending me replies. Iād like to try the disable credit skipping but Iām sticking with the earlier version that works. I had to do a C: drive restore to a working version - good thing I backup the whole OS every few weeks.
Iāve skipped over the last 2 or 3 upgrades and said āno thanksā. I guess Iām waiting for confirmation it is fixed.
I do have intro and credit skipping on the version listed in the first post. I think it was one of the initial releases. It works okay. So Iām not sure what the Plex Gods did.
No BSOD after disabling the intro/credits detection task. Iām on PMS version 1.31.1.6733.
Day #2 of no crashes after disabling intro & credit skipping 
Iām also on PMS Version 1.31.1.6733
OK thatās good news. Now, how do we inform the Plex Illuminati of this problem?
I believe they are aware, there is an old thread from a week or more ago where I mentioned that turning off credit detection stopped the crashing. A staff member saw my comment and asked for logs but I wasnāt willing to hard crash my machine anymore as the drive was showing corruption that needed to be fixed.
Iād like to know how can they crash the PC so hard that windows locks up with a black screen and creates zero logs?
If someone from Plex is reading this, I am willing to provide debug logsā¦
I upgraded to v1.31.1.6782 and re-enabled intro & credit skipping. It made it through the night without crashing!
I think I skipped the latest pushed upgrade, so not sure which one that was, but Iāll accept the next one and see what happens. Thanks for the feedback.
Bad news! Plex v1.31.1.6782 crashed during maintenance last night. I am disabling credit skipping for nowā¦
Still BSODāing the computer at intro/credits detection on version 1.31.1.6782.
1.31.2 just released.
Itās amazing there arenāt more people complaining about this. I wonder whatās different about our setups.
Iām having the exact same issue and Iām on Linux. Hard crashing the entire machine. Itās 100% credit detection and I have 0 issues with my CPU. Iād assume itās affecting more people, they just either havenāt noticed the crashes because theyāre at weird times, or they donāt know the cause.
It happens in the middle of the night and if your plex server is single purpose you wouldnāt know until you logged in and seen that it was doing it. That was my experience anyway.
