I have a task that took 26 hours to reach 100% and even at 100% it continues. The Windows task manager shows that Virtualbox still keeps a CPU core busy. The logfile that I get to see through the "show graphics" button also shows that there is still information added. This is the second time that I see this and the first time I let the file run another day but then I noticed that the running.log seemed to have reset so I aborted that task.

Current task:
https://lhcathome.cern.ch/lhcathome/result.php?resultid=431737820

Is there a graceful way to end this task? My pc has done 28 hours of productive work (although that is what it looks like) so I don't want to simply abort this one.
Any help is appreciated.

Regards, John

Theory tasks can be quite long. There are threads about 6-10days long running tasks. The % in BOINC is clueless about the state in the Virtual machine. So that is no useful indicator for this Project.

If you still see "217 of 760 integrations done" or "52800 events" and counting up then the task is fine(i think most task have been 100k events)
i have not exact knowledge of virtual box tasks. did run theory native tasks so can't help with the exact location of the log file if "show graphics" window is not printing that.

Theory is always a big surprise bag. with ultra short tasks and long runner randomly. If you prefer more stable runtimes then is atlas the better project.

Thanks, I'll allow it some more time then. Its now at "Integrating 328 of 760, iteration 3"

Like the others say, just keep it running. Some may take a long time on a not so powerful computer.
This long running task finished today.
https://lhcathome.cern.ch/lhcathome/result.php?resultid=431519777
Run time 30 days 13 hours 32 min 28 sec
CPU time 26 days 0 hours 45 min 47 sec
Credit 32,023.18

Yea I've had loads that have appeared to be stuck at 100% and I aborted quite a few too!
Would've been useful if the LHC guys had sent us a BOINC message warning about the long runtimes and the inaccuracy of the BOINC % for VM tasks, would've saved wasted crunching time :(.

My 'show graphics' button is greyed out, any idea why?

---

Team AnandTech - WCG, F@H, MW@H, Ast@H, LHC@H, R@H, CPDN, E@H.
Main rig - Ryzen 5800X, MSI B450 Gm Pro C AC, 32GB DDR4 3200, RTX 3060 Ti 8GB, Win10 64bit
2nd rig - i7 4930k @4.1 GHz, 16 GB DDR3 1866, HD 7870XT 3GB(DS), Win7 64

In reply to [TA]Assimilator1's message of 14 Feb 2026:

Yea I've had loads that have appeared to be stuck at 100% and I aborted quite a few too!
Would've been useful if the LHC guys had sent us a BOINC message warning about the long runtimes and the inaccuracy of the BOINC % for VM tasks, would've saved wasted crunching time :(.

My 'show graphics' button is greyed out, any idea why?

Read here: https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=6448&postid=53018

In reply to Crystal Pellet's message of 14 Feb 2026:

In reply to [TA]Assimilator1's message of 14 Feb 2026:

Yea I've had loads that have appeared to be stuck at 100% and I aborted quite a few too!
Would've been useful if the LHC guys had sent us a BOINC message warning about the long runtimes and the inaccuracy of the BOINC % for VM tasks, would've saved wasted crunching time :(.

My 'show graphics' button is greyed out, any idea why?

Read here: https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=6448&postid=53018

Thanks :), I see this for one task I have running :-

PYTHIA Warning in StringFragmentation::fragmentToJunction: bad convergence junction rest frame
PYTHIA Warning in JunctionSplitting::SplitJunPairs: parallel junction state not allowed.
PYTHIA Warning in JunctionSplitting::CheckColours: Not possible to split junctions; making new colours
PYTHIA Warning in JunctionSplitting::CheckColours: Made a gluon colour singlet; redoing colours
PYTHIA Error in StringFragmentation::fragment: stuck in joining
PYTHIA Error in Pythia::next: hadronLevel failed; try again
PYTHIA Error in MiniStringFragmentation::fragment: no 1- or 2-body state found above mass threshold
PYTHIA Warning in SimpleSpaceShower::pT2nextQCD: weight above unity
100 events processed
PYTHIA Error in SimpleSpaceShower::pT2nearThreshold: stuck in loop
PYTHIA Warning in SimpleSpaceShower::pT2nextQCD: small daughter PDF
200 events processed
PYTHIA Error in StringFragmentation::fragmentToJunction: caught in junction flavour loop
300 events processed
400 events processed
500 events processed
PYTHIA Warning in StringFragmentation::finalRegion: random axis needed to break tie
600 events processed
700 events processed
PYTHIA Warning in MiniStringFragmentation::ministring2two: random axis needed to break tie
800 events processed
900 events processed

ends :-


Pythia::next(): 19000 events have been generated
19000 events processed
19100 events processed
19200 events processed
19300 events processed
19400 events processed
19500 events processed
19600 events processed

I assume it's still running then? Is there anywhere in that file that shows progress point?
Are the warnings anything to worry about?

---

Team AnandTech - WCG, F@H, MW@H, Ast@H, LHC@H, R@H, CPDN, E@H.
Main rig - Ryzen 5800X, MSI B450 Gm Pro C AC, 32GB DDR4 3200, RTX 3060 Ti 8GB, Win10 64bit
2nd rig - i7 4930k @4.1 GHz, 16 GB DDR3 1866, HD 7870XT 3GB(DS), Win7 64

In reply to [TA]Assimilator1's message of 16 Feb 2026:

Thanks :), I see this for one task I have running :-

19300 events processed
19400 events processed
19500 events processed
19600 events processed

I assume it's still running then? Is there anywhere in that file that shows progress point?
Are the warnings anything to worry about?

Don't worry about warnings as long as you see the number of events processed (slowly) increasing.
In the very first line of runRivet.log you see the job parameters. The penultimate number on that first line is how many events should be processed. Mostly 100,000 events.
Be aware that the task will not survive a system restart,