Welcome to MilkyWay@home

Just had a BOINC unexpectedly quit when starting an Nbody unit


Advanced search

Message boards : Number crunching : Just had a BOINC unexpectedly quit when starting an Nbody unit
Message board moderation

To post messages, you must log in.

AuthorMessage
Captiosus

Send message
Joined: 9 Apr 14
Posts: 24
Credit: 3,954,796
RAC: 5,745
3 million credit badge7 year member badge
Message 66151 - Posted: 1 Feb 2017, 3:15:59 UTC

Has anyone been having issues with BOINC crashing while computing Milkyway@home tasks? I just had BOINC quit while it was in the process of starting a workunit, and it gave no warning, no error nothing.

The last line of the log says it was starting an Nbody Tighter Constraints MT unit (de_nbody_11_7_16_v162_20k_tighterconstraints_1_1484858102_344533_1).
The only other behavior I can add is that it appears BOINC had just paused the CPU modfit programs (all 8 of them) to start the MT unit when it happened.

I'm not sure if its nbody being derp again, or I just got a bad unit, or what is going on. This rig had successfully gone through easily a dozen or two Nbody units before the crash.

This machine is overclocked, but I dont think that has anything to do with it as this machine has successfully passed running 12hr prime95 large inplace FFTs, and has processed a number of both Collatz and Milkyway@home units, with all units being considered valid by their respective projects. The Collatz CPU units in particular took the machine about 5 days to chew through the 8 units (one per thread) it was given, and those 8 were all considered valid.

I dunno, I'll cook the remaining Milkyway units I have left then try other projects, see if anything can get BOINC to quit again.
ID: 66151 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Just had a BOINC unexpectedly quit when starting an Nbody unit

©2022 Astroinformatics Group