2024-11-08, 05:04 PM
(This post was last modified: 2024-11-08, 05:06 PM by qwerty12. Edited 2 times in total.)
(2024-11-08, 12:48 PM)Viper21 Wrote: You may see this differently than me, but the bug seems to be with Jellyfin and not my files.
This is, really, a Windows issue. Jellyfin is just trying to run ffprobe.exe but ffprobe.exe is crashing. Your Jellyfin logs show is that it's trying to run ffprobe.exe and failing. Jellyfin expects the output to be in a certain format - the log messages you're seeing from Jellyfin basically means there was no parseable output from ffprobe.exe which tracks because, well, ffprobe.exe is crashing. So the problem's outside of Jellyfin.
0xc0000142 means STATUS_DLL_INIT_FAILED which I think means that some DLL file getting loaded by ffprobe.exe isn't able to load. A quick look at Jellyfin's ffprobe.exe shows it depends on absolutely nothing but DLLs that are shipped with Windows. Check your Event Viewer and look around the dates and times you're seeing a ffprobe crash - the full entry pertaining to the crash will have something like "faulting module name" in it with, hopefully, the name of the third-party DLL that's causing a crash. If you're having trouble finding an entry try manually running "C:\ProgramData\Jellyfin\Server\ffprobe.exe" -analyzeduration 200M -probesize 1G -i file:"C:\Sample2.mp4" -threads 0 -v warning -print_format json -show_streams -show_chapters -show_format in a Command Prompt to induce a crash there and then.