Football (pre)season starts this weekend, so this issue is relevant again 
Hi @sa2000 any update on this issue, by chance?
No update yet
You can experiment with different Nvidia drivers in the meantime
Thank you for the update, @sa2000, it is appreciated. Ironically, it appears doing an “advanced” search on drivers turns up all results from last year, so it appears I am using the latest drivers already:
Not sure why your lookup returned old drivers, it should be:
NVIDIA Studio Driver - WHQL
Driver Version: 516.94 - Release Date: Tue Aug 09, 2022
Those are beta drivers, @pl_5309 ?
Note that I am currently on 512.95 which are RTM.
Also, to be sure, when I read “experiment with different Nvidia drivers” I assume this means Beta drivers as the only drivers that I am aware of that will work with my device are either RTM or Beta. As there have been no announcements that this is fixed in RTM, then I am further assuming to try the Beta band of drivers.
(Although I am pretty sure if this was fixed in a beta we would have heard of this by now)
If there is something obvious I am overlooking here with my thinking a pointer would be appreciated.
Not sure where you are seeing “Beta”, WHQL are the Windows Certified drivers.
Per the image above:
Please do let me know if I have something misunderstood.
Beta in regards to the Plex Server release, not the Nvidia drivers. Definitely need to be on 515 or higher.
In that case, I can see why you are not sure where I am getting beta Plex Server from, as I never mentioned it and it has never been a part of this discussion. 
To be certain, the problem being experienced here is not a Plex Server problem but one that is occurring in NVidia drivers.
Are you saying that 515 is required for beta Plex Server? If you have further resources on this please do share. I am running Plex Server RTM but it would be nice to know why a particular product requires a particular display driver version.
Should be visible in the Plex Media Server.log each time the driver is initialized for transcoding.
Pardon my confusion but this makes very little sense to me
Keeping this thread alive… any updates (if any) would be appreciated 
Just had this happen during the Bills vs. Chiefs game… a good reminder to check in with its status 
Asked our devs to ask nvidia for update
1 Like
We got this response from NVIDIA
Do you happen to have more dumps from other users? It would be great to confirm if the problem point is the same or might vary for every failure.
I have not seen this from our users so we will have to stick with dumps and diagnostics from your system
Could you get diagnostics for several crashes using the latest NVIDIA driver and the current version of Plex Media Server 1.29.1.6316-f4cdfea9c (or the 1.29.2 beta that is expected to be released very soon)
Thanks
Thank you for your reply @sa2000 I hope you will understand that getting these crashes is very difficult for me and I have already done two of them. Additionally I am not using beta as the environment is very stable (outside of this issue). Is the previous set of reports sufficient (the first set I reported) perhaps?
I can be talked into a third capture but I hope you can understand the frustration here of having to do this three times now over the course of over a year. It would really seem that doing this not once but twice would be enough to get the required information for a critical exception fault in a driver.
I do understand
We can get more diagnostics this time because there are now Plex Media Server settings that allow automatic capture of the channel stream and also retention of the Transcoder sessions files
I will give more details shortly about these settings
To enable the settings that result in capture of the channel stream data and retention of the Transcoder sessions files:
Regedit and navigate to
HKEY_CURRENT_USER\SOFTWARE\Plex, Inc.\Plex Media Server
Right Click on Plex Media Server and select
New → DWORD (32-bit) Value
to create the following 4 settings
TranscoderPersistSessionDirs Set the value to 1
TranscoderInputTracing Set the value to 1
TranscoderPruneBuffer Set the value to 0
TranscoderLivePruneBuffer Set the value to 0
These will add DVR channel stream capture plus will ensure that the temp files used for the streaming by the transcoder are not purged
The files will be in the transcoder temp directory which by default would be
C:\Users\xxxxx\AppData\Local\Plex Media Server\Cache\Transcode\Sessions
Please try to get diagnostics for 2 failures as they want to see if the failures are always in the same place
zipped Transocder dmp files for the crashes as before plus debug server logs and zip of all the transcoder sessions directories
At end of tests - delete the 4 registry added settings (or invert the values changing 1 to 0 and 0 to 1 to disable)
1 Like
