sa2000
April 6, 2020, 9:40am
4
Amoureux9:
I’m getting the same error and I’m not very happy to find this thread hasn’t been replied to since google searching error -138 for the TCP failure results in only 2 pages with this being one of them.
We’ve noticed that while we have NZBGet downloading we receive the errors much more frequently. If the NZBGet queue is paused then it seems to be a lot more stable (and if not a server restart is required to kick it back into gear). I investigated the logs expecting to find HDD locks as the culprit and was surprised to find the error to be pertaining to a failure to open a TCP session and downloading the segment list.
Maxtoid:
Having all sorts of issues with my latest PMS build on Win10 1903 - First I never could get hardware transcoding to work so I just disabled it, but I’m still having all sorts of issues with transcoding. Seems to only affect some players like Chromecast, or some media types such as HEVC. I didn’t notice it at first because I use Apple TV for 95% of what I watch, but my users tell me it crashes even on Apple TV when they watch HEVC content. Meanwhile I tried to use Chromecast today and it crashed 4 times during one stream. I note this from the logs that looks to line up with the crashes:
I am looking into similar errors here Recording failures after update to 1.19.1 beta
Such errors previously were seen when Malwarebytes Premium was in use but the one I am looking into does not have that running and the security software in use Trend Micro Maximum Security was disabled but did not help
Is Malwarebytes Premium in use ?
When did these errors start. The one I am investigating appears to arise on 1.19.1 but not 1.18.8.2527