Yes, occasionally the client (what version?) get's confused when the first soft-stop point of 6 hours is reached (was it?)... the hard stop is at 12 hours. Presume you've already checked that real CPU use is still high. If not, a client restart may have to be performed to see if it breaks out of that position.

Why waiting till midnight? 12 hours is 12 CPU hours is when these tasks should quit at the most. How much time is the BOINC Manager showing as having been taken by the task?

The 3:53 wallclock (aka elapsed) is still no 6 hours as first possible stop, assuming you're in the grid view and not in the simple view interface.

Given you're on 6.10.21, select the task, and hit the properties button in left margin. Look at the CPU time and take note, then close that window. In a few minutes repeat. It should have incremented almost at the same speed as elapsed.

Ok, if you can plz edit the opening post and insert [RESOLVED] in the title.

There was a chance that the 6.10 client lost part of the elapsed time [wallclock] under various conditions such as a restart. Some versions did that, the silly situation where the correct CPU time would show higher than elapsed.

happy crunching