Feels like a software related issue. Always a problem on first run, never after.
Are you using the code from the tutorial? We have a few thousand of these out there and this is the first report of this kind of problem.
I do know that these displays are sensitive to noise and/or bad connections. One glitch during a command sequence and you have to reset the display to recover.