Executing via a SQL Agent job? SQL Agent has had issues allowing called programs to handle their own errors in the past and the response to end the job happens in an inconsistent timeframe after the error initially occurs. I am not saying that's what this is, but the description fits except for the fact that you're saying it happens on every one of your servers, or is it just some?
Do you capture the warnings and errors coming from the TSQL Task in a file? Anything interesting there? Have you run the DBCC task in an SSMS query window to see that the TSQL runs clean?
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato