doesn't that link take you directly to the post with the screenshots showing the problem?
It is basically deinterlacing behaving in a not obviously deterministic fashion (i.e. not driven by content)
switching to a custom config so I can configure LAV myself does resolve the problem. I'm not sure why hiding deinterlacing config contributes to stability though, doesn't seem any different to choosing whether to use hardware decoding (which is exposed).
from screenshots looks like you using dxva ... turn that off ... then try film mode
Like wer ... I try different different deinterlacing settings to determine what works best for particular content ... then move file to different folders (/film mode ... /video mode) then apply setting in madVR base on location
like madVR forum mentioned ... deintetkacing technique depends on the content ... whether it was shot interlaced ... or was shot progressively then converted to interlaced ... later process can be reversed with IVTC (film mode)
usually IVTC should give perfect result ... but often content is edited after it was interlaced ... so it’s not so simple and results will never be perfect (few glitches there and there)
I have PAL futurama that theoretically should give perfect result with IVTC ... albeit it was mastered so badly that madVR struggle to give good result (in some scene MadVR did great ... in others LG C6 did better ... drove me nuts) ... then I hunted down US NTSC version and madVR deinterlacing look great (not perfect ... but hardly noticeable from normal viewing distance)
PS. also screenshot looks weird ... frame rate is 25 which suggest film mode is being used but there is no cadence detection ... if video mode is used frame rate for pal should be 50 ... must be dxva thingy ... try turning dxva off