I've been seeing the same for some of my tasks too. My guess is that we both have a bad connection and some of the tasks didn't get through to the BOINC manager. Then when the manager contacts the server for a second time, the server doesn't see the task in BOINC and marks it as "no response". I'm not really sure, but I've had many, many tasks that didnt get through and timed out this early.
waiting for a TdP prime...
Proth "SoB": 44243*2^440969+1