I’ll be back in the office tomorrow, but I can offer a bit more detail beforehand.
The Matinee sequences in question are all very barebones, 1 to 2 cameras created directly from within Matinee, otherwise unchanged, which for testing purposes only move in a straight line, keeping 2 out of 3 axes unchanged. No focusing over time / distance, post processing or otherwise enabled on the camera actors. Those are in turn kept as minimal as it gets - two keyframes each, start and end, over spans of 2-10 seconds.
They’re naturally linked to a once again otherwise unmodified director group, which only switches from one cam to the next. Nothing else is in there. The Matinee playback is only forced to play via its play on level start flag, at the moment I have no need for any blueprints controlling that / triggering them otherwise.
It even happens when I only create a blank Matinee with no cameras / director groups or animated actors whatsoever and try to record manual movement through a scene, which ought to rule out a conflict stemming from the animations - which play just fine in-editor.
Like I said, it only began when I switched over to 4.6.1 and newer. I’ve tried it on a project which started out in 4.3, and has since been migrated to 4.6.1 and now 4.7.1, though I’ll bump it to .2 tomorrow. Back during the initial creation, it worked fine. Ever since 4.6.1, matinee recording just crashes regardless of settings, and I’ve tried a whole variety of them 
. Setting up animations / keyframes works without a hitch, it’s really only when I want to render it to movie or frames that it dies on me.
Given how it happens even in a new project created from the starter templates, I’d fault the engine version somehow. Maybe some files got corrupted, I couldn’t say. I could try doing a fresh install, though that happened with 4.7.1 and it didn’t alleviate the issue.