Sure, will do. But do people using this for work actually use the very latest nightly build at any given time? I would think you stick to the ones that works safely..?
People shouldn't use a hack for work and the developers are very clear about this fine point. However I can see how ML's stability can tempt people to feel overly confident about it.
Here's the thing...nowadays the nightly builds are being updated, but not at the same frantic pace as a few months ago. Most of the new improvements concern optimization for .mlv files.
Some people are still using builds from July, and that's plain stupid. However if you're using a build from November 1st, it shouldn't be too different than one from today.
I don't think it's a build issue (although if you're going to re-install, you might as well update to the latest). The way to re-install (at least the way I do it) is this:
1. Format the card in camera
2. Run the Boot script to prepare the card for in-camera booting
3. Drag manually onto the card the ML folders and the auto exec.bin
You'll need to re-configure your ML settings and modules, but it's the safest way I know to make sure that the ML install is clean.
The only time I've seen this type of problem on my 5D3 has been when I was shooting in Crop mode....I suspect the errors are results of data not being written quite fast enough on the card and becoming corrupted here and there.
