As you may know, a huge number of variables can affect binking any movies; PC-Configuration, Swapping to Memory, Codecs - and what else!

From what i can gather of your small comment, it may have been caused when the initial encoding was processed. Bit rates and the amount of memory hogs through CPU piping or/and paging to some swap area can also "alter" the finalized output(s).
(I've seen hundred--S of bad playbacks & recordings overlayed by some stupid messenger warning popups, Lagging of tracks caused by an automatic virus-scan, routing of bug-bytes straight into high-CPU priorities decreasing clockpace - even by ISP pings, ETC!)
Thus, when playback occurs, the missing parts were already flawed and, as a result, bink can't reproduce simply absent frames. So, rad isn't the actual source of the problem, probably.

Depending on the PC conditions and how they are setup WHILE the recording takes place, creation of videos (any lengths, any compression ratios, options selected, etc) will always depend on you choosing specific parameters.

My guess is that the video itself might be or have been borked up. Or even, the program you use to play these has limited capacities which wouldn't otherwise happen on any other (but configured differently) PCs. Mine included.

As a general diagnostic tool i would recommend GSpot which can pinpoint at pretty much any flaws. And indirectly lead you to a possible solution.

- Zyxpsilon.