Do the asic timeouts at :950 persist or are they just a short time transient? I think that if the configuration is changed for a 'running board', then there is a short time transient until present values from the previous session are cleared. If the timeouts are persistent, then you might try 'incremental' increases as suggested by one of the people on the drillbitsystem forum.
Cheers
I think that was me? My boards can be a little finicky when setting them to 950mV. What I've done so far is start mining at
int:48:2:950 for anything from a few seconds to a few minutes, and then change to
int:53:2:950. Got this automated using CGWatcher (in Windows 7) to begin mining on startup at 48:2:950, and then switch to 53:2:950 after three minutes (the smallest time increment possible with that program).
Lately however, they haven't been reliably starting this way. I've had to manually toggle between 40:1:850, 48:2:950 and 53:2:950 before they can run at 53:2:950. Made a few batch files to make this easier.

BTW, got a lovely 42 degrees day coming up on Saturday (EDIT: been updated to 43 degrees, wat...). Either gonna run the boards at 850mV or just turn them off for the day. Yay!