LHC@home

... show a difference between the run time and CPU time of 9-10 hours. Are these examples of what Crystal Pellet is referring to?

Most of the endless loopings I've seen, the job needs the normal CPU-load, so a big difference between elapsed time and used cpu must have another cause.

With your first mentioned task (109863415), the VM seems to have had a problem with the 6th job.
Not sure what, but when you have the time for baby sitting, next time you can access the log files inside the VM with BOINC Manager's 'Show graphics'

The second task you mentioned (109863451) seems to be another problem, I also have seen several times.
The VM did not get a new job after the last result was uploaded.
Normally the VM should be stopped after about 10 minutes idling, but it not always do.

The VM is running over 1 hour without processing a job.

The connection was successful reset, but no new job was sent.

12/14/16 10:53:18 CCBListener: failed to receive message from CCB server vccondor01.cern.ch
12/14/16 10:53:18 CCBListener: connection to CCB server vccondor01.cern.ch failed; will try to reconnect in 60 seconds.
12/14/16 10:53:48 condor_write(): Socket closed when trying to write 2312 bytes to collector vccondor01.cern.ch, fd is 12, errno=104 Connection reset by peer
12/14/16 10:53:48 Buf::write(): condor_write() failed
12/14/16 10:54:18 CCBListener: registered with CCB server vccondor01.cern.ch as ccbid 128.142.142.167:9618?addrs=128.142.142.167-9618+[2001-1458-301-98--100-99]-9618#1227380

On the other 3 VM's I'm getting new jobs.

Normally the VM should gracefully shutdown after 10 minutes idling.
I've the VM-loggings available.