Maybe something got corrupted in the cgminer (or related cgwatcher) settings? Perhaps it's worth trying a 'clean instance' of cgminer, first by itself without cgwatcher. You may want to raise this at the DrillbitSystem forum where it may get more exposure/response from fellow drillbit users/developers.
Cheers
What temp should the board be and which temp is high?
ed. fan(s) on heat sink a must but fan on otherside recommended
Congrats, persistence pays....
I agree about the cooling, now have 3 fans 'surrounding' the drillbit8 board. My board was previously connected directly to the PC USB2 port, yesterday I tried it through a hub with other devices and it worked fine with int:53:2:950 (has been running now for about 9 hours). Temp reported by cgminer 3.8.5 is 32.1C. I think that this board reached something like 36 C with poorer cooling and some people on the drillbitsystem forum http://drillbitsystem.com/forum/index.php?topic=230.0 show higher temps. In general running it hotter would reduce reliability and possibly trigger some on-chip protection mechanisms.
It would be interesting if you find some consistent method to reach the OC settings reliably.
Cheers
HA! spoke to soon after a 5min router restart cgminer disconnected due to no internet no asic timeouts no hashing so back to 54:2:850