Recently upgraded plex from an old Windows 7 box to a new AMD TreadRipper 1950x box. So far so good but this evening I came home to the kids complaining plex was down. I checked in the event log and saw:
Faulting application name: Plex Media Server.exe, version: 1.12.1.4885, time stamp: 0x5aac03a1
Faulting module name: ntdll.dll, version: 10.0.16299.248, time stamp: 0x3a21d961
Exception code: 0xc0000374
Fault offset: 0x000da879
Faulting process id: 0x2e9c
Faulting application start time: 0x01d3c93eda17bd33
Faulting application path: C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe
Faulting module path: C:\WINDOWS\SYSTEM32
tdll.dll
Report Id: cb2bd85d-38c8-4c99-a9d5-587aba181083
Faulting package full name:
Faulting package-relative application ID:
Any ideas what’s going on and more importantly how to fix it? To be 100% clear I am not running plex as a service, I just run the icon and it sits in the tray. If running plex as a service is more stable and will automatically restart when failed then that may be the best solution?
With issues like this, it is very important to get the developers a so-called “crash dump”.
(see the above linked thread)
Side note: I faintly remember to have read in a different fourm thread that the Threadripper requires installation of a special driver software in Windows. Make sure you have the latest version of that installed, downloaded directly from the AMD website.
With issues like this, it is very important to get the developers a so-called “crash dump”.
(see the above linked thread)
Side note: I faintly remember to have read in a different fourm thread that the Threadripper requires installation of a special driver software in Windows. Make sure you have the latest version of that installed, downloaded directly from the AMD website.
Also this crash is different. The thread you linked the media server won’t start. In my case the media server was running for a few days and then it crashed. Simply starting it again brought the services back up, but that’s not an ideal solution.
With issues like this, it is very important to get the developers a so-called “crash dump”.
(see the above linked thread)
Side note: I faintly remember to have read in a different fourm thread that the Threadripper requires installation of a special driver software in Windows. Make sure you have the latest version of that installed, downloaded directly from the AMD website.
Also this crash is different. The thread you linked the media server won’t start. In my case the media server was running for a few days and then it crashed. Simply starting it again brought the services back up, but that’s not an ideal solution.
The similarities is the type of crash and the need to get windows to capture the dmp file
OK i turned off hardware acceleration and when the server is done recording the next show i’ll reinstall the graphics drivers with a fresh install. With the threadripper 1950x, it has plenty of CPU to handle transcoding. I’ll probably just leave hardware acceleration turned off?
@bnutting said:
OK i turned off hardware acceleration and when the server is done recording the next show i’ll reinstall the graphics drivers with a fresh install. With the threadripper 1950x, it has plenty of CPU to handle transcoding. I’ll probably just leave hardware acceleration turned off?
Need to establish why that driver is crashing and if it is the latest version. Also for the issue in the related forum topic, there were two types of drivers - and one of them crashed less.
If you are up to date with nvidia drivers, then i suggest raising an issue with their technical support and may providing that crash dmp file
@bnutting said:
Here is the crash dump as requested.
I have all drivers installed properly from the AMD and Asus websites. My Nvidia 760 GTX also has the proper drivers from the Nvidia website.
The server logs zip please covering time up to the crash
Sent you a PM with the log
The crash dmp provided was at on April 3rd at 19:02:19 GMT
The logs were for April 6th
So there isn’t any more information other than the crash and the crash arose whilst doing hardware encoding