BinaryBoy's reply to pgb205 #15767 @
Logging might actually contribute to the problem, but if you want to try it, make sure only the regular log -log and the decoding log -declog are enabled. Then if the problem happens again and you have to shutdown, look at the last lines of Documents\Binary Boy\log.txt to see what Binary Boy was doing right before it was terminated.
In task manager did you see what the CPU percentage was for Binary Boy and is it possible a different process is eating the CPU time?