BMCC almost went dead

Hello! Something really frustrating happened nearly 5 mins ago!

So I was testing out my BMCC with some lights charging off Switronix Powerbase 70. The camera was at 100% but was showing "charging" icon, so I guess it wasn't fully charged. The battery was charged 2 steps out of 4. I wasn't even shooting, just testing out the looks and workflow with different FILM/VIDEO setting and shutter speed. But all of the sudden the BMCC screen went cut by half showinh a vertical line! One side was fairly darker than the other. I tried to turn the camera off, it went off and then immediately restarted itself, the problem was still there. I tried turining it off again and again, and finally it went off. I was so scared to turn it on again. So my first guess was to reboot it in 1.1 Firmware, and then installed back to 1.4.1. I turned it on, and the problem was gone!

I nearly had a heart attack, because I know it will be almost impossible for me to send it for a repair.

Has anyone experienced this? What bug is it? The camera was operated just fine for a month now.

I wouldn't immediately blame the camera. You may want to make sure you don't have a faulty power solution, first.

I wouldn't immediately blame the camera. You may want to make sure you don't have a faulty power solution, first.

It was working fine till that day.
And the "symptoms" are similar to the sensor issues people had from the start

But you definitely made a point!

I'd just try to rule out anything external first. A weird power regulation problem would definitely hurt your camera. IF you get it again, and hopefully you do not, try not using the Swit base and just charge it off of the wall charger for a few uses.

Did this happen when you changed the settings to DNxHD? That was a problem with the old firmware but should be fixed with updates.

Did this happen when you changed the settings to DNxHD? That was a problem with the old firmware but should be fixed with updates.

Well, don't remember exactly, maybe I did change. Anyway, I am at the latest firmware, so that wasn't the problem.