Posts by Jeff Buck


log in
1) Message boards : Number crunching : Is it possible to swap a guppi assigned to GPU with a Arecibo assigned to CPU? (Message 1799522)
Posted 1 hour ago by Profile Jeff Buck
I don't think temporarily going over the 100 task limit by a modest amount should be a problem, but others may differ on that point. In a sense, I can justify it by the fact that I also have 3 crunchers which never come anywhere near that limit, and one that rarely does. For instance, my daily driver here currently only has 10 tasks assigned to the CPU. Even when I next make a rescheduling run (probably shortly after I write this) it appears that only 9 additional tasks will be added to the CPU, still 81 tasks under that arbitrary limit. I also have an old laptop running, with no GPU, that currently has just 7 tasks assigned, 93 tasks under the limit. Now, I could certainly bump up my work buffer to 10+ days, like some SETIzens do, and still be under 100, but I won't. So, I don't feel particularly guilty about having my two big crunchers temporarily exceed that limit after a rescheduling run.

<soapbox> Besides, I think many folks here feel like the CPU limit should be a core-based limit, rather than a host-based limit. And even if that limit is much less than 100 (50/40/25/whatever), an 8-core system should still be able to have more than 100 tasks ready to run on the CPUs.</soapbox>

I wouldn't say that swapping isn't beneficial for multiple GPU heavy crunchers. If I use RAC as a measure (tenuous, at best, I know, but...), even my big boxes have increased about 5-6% in the last week. Now, one of my concerns with rescheduling was that the rescheduling itself (quantum rescheduling?) would skew the credits and render that measure more unreliable than usual. That's why I did the comparisons shown in my post last evening, which I believe show no material effect on credits.

As far as finding a combination of CPUs and GPUs which would render rescheduling a (carbon) neutral endeavor, I haven't a clue. Certainly, you could look at your existing setup and physically count how many of each would theoretically be swapped in a rescheduling run at this moment. Then, perhaps do that once a day at the same time for a week and see how the mix changes. Then estimate how much additional processing time the CPU will be facing versus how much less the GPU will have. Then do math. Good luck! ;^)
2) Message boards : Number crunching : Is it possible to swap a guppi assigned to GPU with a Arecibo assigned to CPU? (Message 1799476)
Posted 4 hours ago by Profile Jeff Buck
I can only tell you what my rather limited experience has been over the last 9 days or so, and that is that your scenario #3 is almost always the one that I've run into. I think only once have I made a rescheduling run where there were more non-VLARs assigned to CPU than there were VLARs assigned to GPU, and the difference was only a couple of tasks. Usually, it's greatly tilted in the other direction. It's impossible to know whether that will remain generally true over the long haul or not, but Breakthrough Listen seems to be generating far more new data from Greenbank than what little we've gotten from Arecibo.

Now, my little app, which appears to work just fine for my 5 GPU-enabled boxes running Cuda, isn't as sophisticated as what it appears Mr. Kevvy is developing and is not something I plan to build up and distribute. It does not, for instance do the approximate 1:1 replacement that he's doing and which, I think is an excellent approach. I simply move all currently available VLARs from GPU to CPU and all non-VLARs from CPU to GPU. Since your scenario #3 is almost always in play, that tends to create a temporary imbalance with an overage of tasks on the CPU and an underage on the GPU.

I usually maintain no more than a 2-day work buffer on any of my boxes so, on my two dual-core boxes with GT 630s, which are never even close to any queue limits, that imbalance is never a big deal and corrects itself very quickly. I find that rescheduling once, or occasionally twice, a day works best. On my dual-core with a GTX 550Ti, I think I've exceeded the 100-task CPU limit once, for a short time. (In fact, right now that machine has just 43 tasks on the CPU, all VLARs. Unfortunately, out of the 100 tasks on the GPU, 72 of those are also VLARs, which I'm just going to let run for now. I don't reschedule until the scheduler starts requesting more CPU tasks.)

My two big boxes, one with 3 GPUs and one with 4 GPUs, are a different story. With all those GPUs to reschedule "from" (at 100 tasks per GPU), the CPU queue is almost certain to go over the 100-task limit with all the VLARs. I don't see that as a significant problem, as long as I just let it steadily drain back down before I make another rescheduling run. It appears that one run every 4-5 days is about right. Of course, that means that the GPUs still end up processing a lot of #@#$%#$^ VLARs, but at least I know that they're also doing all of the non-VLARs. Again, I don't make a rescheduling run at least until the scheduler starts requesting CPU work again. Implementing more of a 1-for-1 swap approach would certainly avoid the temporary imbalance in the queue, but in the end wouldn't actually change the overall CPU/GPU balance and would just require more frequent rescheduling runs.

Anyway, I'd really prefer to see the project treat VLAR MBs as an entirely different data class, alongside non-VLAR MBs and APs, which could be selected and scheduled in the same manner that those two are. That would avoid this whole rescheduling conundrum, but I finally got tired of waiting for that to happen. I figured I'd be old and gray by then.....oh, wait....too late!
3) Message boards : Number crunching : Is it possible to swap a guppi assigned to GPU with a Arecibo assigned to CPU? (Message 1799300)
Posted 21 hours ago by Profile Jeff Buck
For those interested in some hard data in regard to rescheduling VLARs from GPU to CPU and non-VLARs from CPU to GPU, the table below contains a small sample of tasks from two of my machines.

Yes, I've been rescheduling VLARs and non-VLARs for a little over a week now, after feeling like I had waited long enough for project administration to implement some sort of VLARs-to-CPUs, non-VLARs-to-GPUs option. I'm satisfied with the results so far and can see no more impact to the credits than is caused by the random number generator that assigns them in the first place.

VLAR Rescheduling - Credit Comparison
Host: 6942834 (AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ w/ NVIDIA GeForce GT 630)]
VLARs
Run on GPU (as originally scheduled) | Run on CPU (as originally scheduled) | Run on CPU (rescheduled from GPU) Task # AR Run Time Credits | Task # AR Run Time Credits | Task # AR Run Time Credits 4993528119 0.009093 2:11:09 118.50 | 5008922033 0.008328 5:21:27 82.30 | 5008922165 0.008749 5:06:20 100.32 4993528118 0.009093 2:07:35 117.12 | 4996046222 0.011193 5:34:10 98.26 | 5008448553 0.008749 5:26:16 91.73 4993205931 0.009236 2:06:24 126.80 | 4995601343 0.008251 5:01:52 102.82 | 4996408050 0.009326 4:52:23 118.85 4993206390 0.009236 2:18:06 88.43 | 4994390993 0.008735 5:03:36 100.12 | 4999213561 0.008251 5:07:44 106.11

Non-VLARs (approx. normal AR)
Run on GPU (as originally scheduled) | Run on CPU (as originally scheduled) | Run on GPU (rescheduled from CPU) Task # AR Run Time Credits | Task # AR Run Time Credits | Task # AR Run Time Credits 5008448355 0.416306 1:10:49 111.53 | 4992035680 0.422157 5:49:21 103.52 | 5008150151 0.416043 1:30:00 109.70 5008245540 0.416235 1:11:23 118.92 | 4990401265 0.410352 7:36:01 122.05 | 4995310479 0.425248 1:09:50 100.30 5008150014 0.416043 1:14:04 114.88 | 4990223694 0.426270 6:51:07 106.43 | (no more available in same approx. AR) 4997635645 0.405997 1:14:47 107.64 | 4989815754 0.426296 6:35:29 113.67

Host: 7057115 (Intel(R) Xeon(R) CPU E5430 Dual Quad Core - 3 GPUs but using only NVIDIA GTX 670 in examples)]
VLARs
Run on GPU (as originally scheduled) | Run on CPU (as originally scheduled) | Run on CPU (rescheduled from GPU) Task # AR Run Time Credits | Task # AR Run Time Credits | Task # AR Run Time Credits 5009326355 0.011098 0:59:30 67.35 | 4998596435 0.008582 3:29:24 95.90 | 5005715436 0.009883 2:53:42 174.39 5009319007 0.011107 0:52:38 73.52 | 4998573969 0.007367 3:41:18 81.81 | 5005696056 0.009883 3:00:58 75.95 5009318351 0.011107 1:12:54 143.42 | 4998573960 0.008582 3:36:21 81.09 | 5005696054 0.009883 3:00:39 77.07 5009318998 0.011107 1:35:08 90.18 | 4998573956 0.008582 3:24:56 76.55 | 5005602376 0.007995 2:57:01 90.37

Non-VLARs (approx. normal AR)
Run on GPU (as originally scheduled) | Run on CPU (as originally scheduled) | Run on GPU (rescheduled from CPU) Task # AR Run Time Credits | Task # AR Run Time Credits | Task # AR Run Time Credits 5009318949 0.414921 0:35:37 81.11 | 4995157224 0.442436 5:03:02 101.95 | 4999189921 0.408052 0:30:16 105.91 5005650157 0.426203 0:28:36 53.68 | 4995150139 0.442730 5:19:15 118.65 | 4998551166 0.431675 0:25:45 116.46 5005556435 0.426150 0:28:50 111.66 | 4994207188 0.422130 5:36:43 127.21 | 4997635293 0.405690 0:30:25 110.20 5005470004 0.423057 0:26:44 115.31 | 4994151453 0.422029 5:10:36 85.22 | 4996909612 0.442163 0:27:01 59.37

All tasks used for the comparisons achieved normal completion (i.e., no -9 overflows). All GPU tasks were run using cuda50. In fact, all my hosts are running either cuda50 or cuda42, making the rescheduling much simpler, since both CPU and GPU apps currently have the same version number (8.00).

I'm not going to try to do any statistical analysis of those credit numbers (good luck to anyone who wants to try), but I think it should be clear that the range of credits granted to tasks run as originally scheduled is little different than the range for those that were rescheduled.

Most of the tasks listed have already dropped off the BOINC database, but I still have all the task detail pages in my archives, if anyone's interested in more detail on any of them.
4) Message boards : Number crunching : Error while downloading - ideas?? (Message 1799241)
Posted 1 day ago by Profile Jeff Buck
What has changed in the environment? Based on timelines ... it all started when I began using Kaspersky Internet Security. My suspicion is that the AV program is not obeying my exclusions or is slowing the systems down right at the exact time a downloaded task needs to be written to disk.

You might want to see if you can correlate the timing of the download failures with the times that Kaspersky is downloading its definition file updates on any of your machines. I know that McAfee, which I have here on my daily driver, seems to hog the whole system when it's doing that update. And that probably affects the throughput for my whole network for the duration of the download.
5) Message boards : Number crunching : Error while downloading - ideas?? (Message 1799156)
Posted 1 day ago by Profile Jeff Buck
I notice that on your second example, BOINC is starting to download 3 tasks simultaneously. I believe the default for a single project is just 2 tasks (or files). Do you have a different value set in cc_config.xml for <max_file_xfers_per_project>N</max_file_xfers_per_project>? If so, perhaps your pipeline is getting clogged and packets are getting dropped. Could you try going back to the default and see if that makes a difference?
6) Message boards : Number crunching : Error while downloading - ideas?? (Message 1799118)
Posted 2 days ago by Profile Jeff Buck
My rebooting of both the router and gateway did not change the download errors in both of my crunchers. So I am out of ideas of what could be causing these random downloads to fail. Anyone have any further ideas of what is going on and any remedies I have not tried yet?

I looked back over the various download errors and their associated error codes that I've gotten over the past 3+ years and found only one group that ended up with the "<error_code>-200 (wrong size)</error_code>" that you appear to be getting. That happened a couple years ago when an AT&T technician was checking my DSL line and managed to disconnect it right smack in the middle of a download sequence. I ended up with 11 tasks with that "-200" error. There could have been only 2 of them actually downloading at the time of the interruption, but apparently all the files waiting to be downloaded got whacked too.

So, I would say that a temporary interruption in your Internet connection could be at the root of the problem. Whether that might be your modem, router, or something further up the line, is anybody's guess. Does your Event Log show anything for those files that might supplement what's shown in the task Stderr?
Nothing happening on the DSL technician front as far as I know. No trucks on the street when these errors happen. I have never found anything in the gateway logs coinciding with the times of the errors either. Also, since I run MilkyWay at the same time as Seti, the download activity is darn near constant since Milkyway downloads every minute or so and often very near the times that Seti tried downloading a work unit and failed. Again, no download errors for either Einstein nor MilkyWay. I did see the last download error report in the logfile as it happened for the single CPU task BOINC asked for. Slightly different entries than what got reported in stderr.txt for that task.

27-Jun-2016 13:28:45 [SETI@home] Requesting new tasks for CPU and NVIDIA GPU 27-Jun-2016 13:28:49 [SETI@home] Scheduler request completed: got 1 new tasks 27-Jun-2016 13:28:51 [SETI@home] Started download of 30no10ab.31740.5903.12.39.204 27-Jun-2016 13:28:53 [SETI@home] Incomplete read of 43.000000 < 5KB for 30no10ab.31740.5903.12.39.204 - truncating 27-Jun-2016 13:28:53 [SETI@home] Finished download of 30no10ab.31740.5903.12.39.204 27-Jun-2016 13:28:53 [SETI@home] File 30no10ab.31740.5903.12.39.204 has wrong size: expected 365927, got 0 27-Jun-2016 13:28:53 [SETI@home] Checksum or signature error for 30no10ab.31740.5903.12.39.204

Can you try going back into your stdoutdae.txt and even the stdoutdae.old files and see if that "has wrong size: expected" response has ever shown up on any files where the download was immediately started again and then succeeded without getting the error? I was just looking at a couple of old forum threads where that situation also occurred. For instance, see "[error] File ... has wrong size: expected ... got ...". Again, the suggestion there was that "It is displayed when the connection is interrupted during download." If it is a temporary interruption, though, I have no idea why only S@H would be affected and not MilkyWay or Einstein, unless they're more fault tolerant somehow and always initiate a retry of any interrupted downloads.
7) Message boards : Number crunching : Error while downloading - ideas?? (Message 1799070)
Posted 2 days ago by Profile Jeff Buck
My rebooting of both the router and gateway did not change the download errors in both of my crunchers. So I am out of ideas of what could be causing these random downloads to fail. Anyone have any further ideas of what is going on and any remedies I have not tried yet?

I looked back over the various download errors and their associated error codes that I've gotten over the past 3+ years and found only one group that ended up with the "<error_code>-200 (wrong size)</error_code>" that you appear to be getting. That happened a couple years ago when an AT&T technician was checking my DSL line and managed to disconnect it right smack in the middle of a download sequence. I ended up with 11 tasks with that "-200" error. There could have been only 2 of them actually downloading at the time of the interruption, but apparently all the files waiting to be downloaded got whacked too.

So, I would say that a temporary interruption in your Internet connection could be at the root of the problem. Whether that might be your modem, router, or something further up the line, is anybody's guess. Does your Event Log show anything for those files that might supplement what's shown in the task Stderr?
8) Message boards : Number crunching : Lose WUs after resetting SETI? (Message 1798083)
Posted 6 days ago by Profile Jeff Buck
Any remedy to get these "lost" jobs processing again after to fact?

I know this subject has been discussed before, but I don't recall specifics.

It really depends on how much effort you're willing to put into getting those tasks back but, yes, it can be done. If you choose not to try to recover them, they will still time out and be resent when their deadlines are reached.

There was some discussion of this topic earlier this year in the "Abandoned Tasks" thread, primarily beginning with Richard Haselgrove's comments about the "report the same task twice" trick in Message 1758672.

I offered a step-by-step approach that worked for me in Message 1758737. I've since refined that slightly and, in fact, just a few days ago used it to recover 33 of 34 lost tasks on my host #6949656. Here's the updated version of my approach.

1. Wait until you have a single task that has finished uploading and is ready to report.
2. Before it can report, suspend processing, suspend network activity, and set NNT.
3. Make a backup copy of the BOINC data directory.* (see NOTE, below)
4. Resume network activity, then "update" the project to report the waiting task (although, with NNT set, that may happen automatically).
5. Suspend network activity.
6. Exit BOINC completely.
7. Restore the BOINC directory backup.* (see NOTE, below)
8. Restart BOINC.
9. Increase your work buffer to accommodate your "lost" tasks. (BOINC won't send any tasks if it thinks your buffer is already "full".)
10. "Allow new tasks", then resume network activity.
11. Be sure at least 5 minutes has passed since the scheduler request in Step 4 completed, then resume normal processing.
12. If BOINC doesn't automatically initiate a scheduler request, hit "Update" to once again report the same waiting task. This "should" result in one or more "lost" tasks being resent.

NOTE: As was also suggested in that thread, it is probably sufficient to simply backup and restore client_state.xml (and perhaps client_state_prev.xml), but I tend to like to be sure I'm keeping everything in sync and so I choose to do the entire BOINC data directory. It's just as simple, really.

Offered "as is" and without warranty of any kind! :^)
9) Message boards : Number crunching : 1073741205 Error Code (Unknown Error) (Message 1796896)
Posted 12 days ago by Profile Jeff Buck
Today I got 26 WU fail with this error while I was updating windows. One software refused to close while Windows was shutting down and Windows showed that this software was prohibiting windows shutdown. So I had to cancel the Windows restart and kill the stuck software and then do the restart. Unfortunately 26 WUs were trashed during this.

I'm now uninstalling the KB3145739 and see what this does.

To be honest, that's the first time I see GPU WUs trashing this way.

It's from one of the OpenCL apps, which behave like the CPU apps in this situation. The CUDA apps don't get that same error.
10) Message boards : Number crunching : 1073741205 Error Code (Unknown Error) (Message 1796658)
Posted 13 days ago by Profile Jeff Buck
Installed KB3145739 on the 32-bit Windows and now it matches the 64-bit Windows.

So, that would definitely seem to point to the KB3145739 update as being the trigger for the recent appearance of the 0xc000026b errors. It's too bad that Microsoft bundled that change into a security update. Otherwise, rolling back the update might be another workaround to avoid the error, since any fix in a future BOINC version might never get implemented by some users. However, I don't think it would be wise to back out a Windows security update.
11) Message boards : Number crunching : 1073741205 Error Code (Unknown Error) (Message 1795960)
Posted 16 days ago by Profile Jeff Buck
On 32-bit Windows 7 SP1 with approximately no updates on top of the SP, after I initiated the reboot, both apps failed to re-start with c0000142=STATUS_DLL_INIT_FAILED error.

On fully updated 64-bit Windows 7, after I initiated the reboot, the GUI app failed to re-start with c000026b=STATUS_DLL_INIT_FAILED_LOGOFF error. The console app continued to fail to re-start with c0000142=STATUS_DLL_INIT_FAILED error.

Those references reminded me that I had intended to check my Windows updates from April to see if I could notice anything that might have caused these task errors to suddenly start appearing (at least on my 2 Win7 boxes) only beginning in late April, even though the "restart during shutdown" behavior has been occurring for much longer.

So, I just did that and I ran across a curious security update, KB3145739, which also includes "Non-security-related fixes that are included in this security update", to wit:
When you repeatedly run a script in session 0, a "0xc0000142" error is recorded in the System event log. In some cases, you may receive a "0xc0000142" error message in a popup window.

For example, this problem may occur if you use task scheduler to start a batch file (*.bat). In this scenario, Windows starts the cmd.exe process, and then the 0xc0000142 error occurs.

Is it possible that in trying to eliminate the 0xc0000142 error in these particular circumstances, Microsoft exposed the 0xc000026b error in other cases? Would it be worthwhile, or even possible, to install this update on your 32-bit machine and rerun your test, to see if the results are altered?

BTW, I installed this particular Windows update on my two Win 7 boxes (both of which have gotten the errors) on April 22, on my Win 8.1 box (which gets the "restart during shutdown" occasionally, but no errors, yet) on April 13, and my Win Vista box (no restarts and no errors, so far) on April 22.
12) Message boards : Number crunching : Daily quota of three tasks? (Message 1795834)
Posted 17 days ago by Profile Jeff Buck
As TBar suggested, the explanation can be found in 1073741205 Error Code (Unknown Error). The errors result from a BOINC problem that's sometimes caused when the BOINC client and its science applications are still running during a system shutdown. It primarily seems to be occurring on Windows 7 systems. The simplest workaround at present is to ensure that you exit BOINC and the client applications first, before performing a system shutdown or restart.

The latest beta version of BOINC, 7.6.33, appears to address the tail end of the problem (though not the root cause), thus managing to avoid (in most cases) causing the tasks to get the errors you've experienced, but that version hasn't been released for general use as yet.
13) Message boards : Number crunching : Windows 10 - Yea or Nay? (Message 1794606)
Posted 20 days ago by Profile Jeff Buck
It's baaaaaaack!

2952664 - Last Review: 06/08/2016 16:11:00 - Revision: 21.0
14) Message boards : Number crunching : 1073741205 Error Code (Unknown Error) (Message 1794060)
Posted 23 days ago by Profile Jeff Buck
Okay, I suspended all my CPU tasks, both running and ready to start, except for 3 freshly launched tasks (so that I wouldn't lose too much if they failed), launched Process Monitor, then did a system shutdown/restart. The results, limited though they are, look encouraging as far as the Band-aid goes.

06-Jun-2016 11:26:18 [SETI@home] task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.7399.831.18.27.189.vlar_1 suspended by user
06-Jun-2016 11:26:19 [SETI@home] [cpu_sched] Preempting blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.7399.831.18.27.189.vlar_1 (removed from memory)
06-Jun-2016 11:27:05 [SETI@home] Task 30my10aa.7465.20108.15.42.50_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:05 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:05 [SETI@home] Task 30my10aa.7465.21335.15.42.155_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:05 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:05 [SETI@home] Task 03se10ab.12907.21748.6.33.177_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:05 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:05 [SETI@home] Task 20au10ab.18727.11114.16.43.202_3 exited with zero status but no 'finished' file
06-Jun-2016 11:27:05 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:05 [SETI@home] Task 29au10ad.12786.1707.10.37.44_2 exited with zero status but no 'finished' file
06-Jun-2016 11:27:05 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:05 [SETI@home] Task 31mr10ac.18449.15621.8.35.184_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:05 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:05 [SETI@home] [cpu_sched] Restarting task 30my10aa.7465.20108.15.42.50_0 using setiathome_v8 version 800 (cuda50) in slot 2
06-Jun-2016 11:27:05 [SETI@home] [cpu_sched] Restarting task 30my10aa.7465.21335.15.42.155_0 using setiathome_v8 version 800 (cuda50) in slot 5
06-Jun-2016 11:27:05 [SETI@home] [cpu_sched] Restarting task 03se10ab.12907.21748.6.33.177_0 using setiathome_v8 version 800 (cuda50) in slot 17
06-Jun-2016 11:27:05 [SETI@home] [cpu_sched] Restarting task 20au10ab.18727.11114.16.43.202_3 using setiathome_v8 version 800 in slot 20
06-Jun-2016 11:27:05 [SETI@home] [cpu_sched] Restarting task 29au10ad.12786.1707.10.37.44_2 using setiathome_v8 version 800 in slot 21
06-Jun-2016 11:27:05 [SETI@home] [cpu_sched] Restarting task 31mr10ac.18449.15621.8.35.184_0 using setiathome_v8 version 800 in slot 22
06-Jun-2016 11:27:07 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2089.416.17.26.230.vlar_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task 31mr10ac.31259.23801.7.34.60_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.15672.0.17.26.168.vlar_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.15672.831.17.26.44.vlar_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task blc5_2bit_guppi_57451_27034_HIP69732_0025.16545.0.18.27.3.vlar_2 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task 03se10ab.12907.13977.6.33.87_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task 03se10ab.12907.16840.6.33.67_1 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task 30my10aa.7465.20108.15.42.50_0 exited with a DLL initialization error.
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:07 [SETI@home] Task 30my10aa.7465.21335.15.42.155_0 exited with a DLL initialization error.
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:07 [SETI@home] Task 03se10ab.12907.21748.6.33.177_0 exited with a DLL initialization error.
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:07 [SETI@home] Task 20au10ab.18727.11114.16.43.202_3 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task 29au10ad.12786.1707.10.37.44_2 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] Task 31mr10ac.18449.15621.8.35.184_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:07 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:07 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2089.416.17.26.230.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 15
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 31mr10ac.31259.23801.7.34.60_0 using setiathome_v8 version 800 (cuda50) in slot 7
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.15672.0.17.26.168.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 16
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.15672.831.17.26.44.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 19
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27034_HIP69732_0025.16545.0.18.27.3.vlar_2 using setiathome_v8 version 800 (cuda50) in slot 10
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 03se10ab.12907.13977.6.33.87_0 using setiathome_v8 version 800 (cuda50) in slot 0
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 03se10ab.12907.16840.6.33.67_1 using setiathome_v8 version 800 (cuda50) in slot 8
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 30my10aa.7465.20108.15.42.50_0 using setiathome_v8 version 800 (cuda50) in slot 2
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 30my10aa.7465.21335.15.42.155_0 using setiathome_v8 version 800 (cuda50) in slot 5
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 03se10ab.12907.21748.6.33.177_0 using setiathome_v8 version 800 (cuda50) in slot 17
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 20au10ab.18727.11114.16.43.202_3 using setiathome_v8 version 800 in slot 20
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 29au10ad.12786.1707.10.37.44_2 using setiathome_v8 version 800 in slot 21
06-Jun-2016 11:27:08 [SETI@home] [cpu_sched] Restarting task 31mr10ac.18449.15621.8.35.184_0 using setiathome_v8 version 800 in slot 22
06-Jun-2016 11:27:09 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19917.416.17.26.156.vlar_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:09 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19958.0.18.27.184.vlar_1 exited with zero status but no 'finished' file
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:09 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2089.416.17.26.230.vlar_0 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task 31mr10ac.31259.23801.7.34.60_0 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.15672.0.17.26.168.vlar_0 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.15672.831.17.26.44.vlar_0 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task blc5_2bit_guppi_57451_27034_HIP69732_0025.16545.0.18.27.3.vlar_2 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task 03se10ab.12907.13977.6.33.87_0 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task 03se10ab.12907.16840.6.33.67_1 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task 30my10aa.7465.20108.15.42.50_0 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task 30my10aa.7465.21335.15.42.155_0 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task 03se10ab.12907.21748.6.33.177_0 exited with a DLL initialization error.
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reboot your computer.
06-Jun-2016 11:27:09 [SETI@home] Task 20au10ab.18727.11114.16.43.202_3 exited with zero status but no 'finished' file
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:09 [SETI@home] Task 29au10ad.12786.1707.10.37.44_2 exited with zero status but no 'finished' file
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:09 [SETI@home] Task 31mr10ac.18449.15621.8.35.184_0 exited with zero status but no 'finished' file
06-Jun-2016 11:27:09 [SETI@home] If this happens repeatedly you may need to reset the project.
06-Jun-2016 11:27:09 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19917.416.17.26.156.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 6
06-Jun-2016 11:27:09 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19958.0.18.27.184.vlar_1 using setiathome_v8 version 800 (cuda50) in slot 3
06-Jun-2016 11:27:09 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2089.416.17.26.230.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 15
06-Jun-2016 11:27:09 [SETI@home] [cpu_sched] Restarting task 31mr10ac.31259.23801.7.34.60_0 using setiathome_v8 version 800 (cuda50) in slot 7
06-Jun-2016 11:27:09 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.15672.0.17.26.168.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 16
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.15672.831.17.26.44.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 19
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27034_HIP69732_0025.16545.0.18.27.3.vlar_2 using setiathome_v8 version 800 (cuda50) in slot 10
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task 03se10ab.12907.13977.6.33.87_0 using setiathome_v8 version 800 (cuda50) in slot 0
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task 03se10ab.12907.16840.6.33.67_1 using setiathome_v8 version 800 (cuda50) in slot 8
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task 30my10aa.7465.20108.15.42.50_0 using setiathome_v8 version 800 (cuda50) in slot 2
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task 30my10aa.7465.21335.15.42.155_0 using setiathome_v8 version 800 (cuda50) in slot 5
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task 03se10ab.12907.21748.6.33.177_0 using setiathome_v8 version 800 (cuda50) in slot 17
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task 20au10ab.18727.11114.16.43.202_3 using setiathome_v8 version 800 in slot 20
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task 29au10ad.12786.1707.10.37.44_2 using setiathome_v8 version 800 in slot 21
06-Jun-2016 11:27:10 [SETI@home] [cpu_sched] Restarting task 31mr10ac.18449.15621.8.35.184_0 using setiathome_v8 version 800 in slot 22
06-Jun-2016 11:29:37 [---] Starting BOINC client version 7.6.33 for windows_intelx86
06-Jun-2016 11:29:37 [---] log flags: file_xfer, sched_ops, task, cpu_sched

I've highlighted one of the three CPU tasks in the Event Log, above. All 3 seem to have behaved the same. Each was apparently shut down by Windows 3 times, then restarted by BOINC 3 times before the system finished shutting down. None of them actually displayed the DLL Initialization error (unlike the GPU tasks), but I don't suppose that's definitive as to whether or not they actually encountered them. They all restarted successfully after the system restart.

A look at the Stderr from Slot 20 for the highlighted task shows:

Build features: SETI8 Non-graphics FFTW USE_SSE3 x86 CPUID: Quad-Core AMD Opteron(tm) Processor 2389 Cache: L1=64K L2=512K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSE4A ar=0.414118 NumCfft=199195 NumGauss=1141825356 NumPulse=226448017394 NumTriplet=452862338944 In v_BaseLineSmooth: NumDataPoints=1048576, BoxCarLength=8192, NumPointsInChunk=32768 Windows optimized setiathome_v8 application Based on Intel, Core 2-optimized v8-nographics V5.13 by Alex Kan SSE3xj Win32 Build 3330 , Ported by : Raistmer, JDWhale SETI8 update by Raistmer Work Unit Info: ............... Credit multiplier is : 2.85 WU true angle range is : 0.414118 Build features: SETI8 Non-graphics FFTW USE_SSE3 x86 CPUID: Quad-Core AMD Opteron(tm) Processor 2389 Cache: L1=64K L2=512K CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3 SSE4A ar=0.414118 NumCfft=199195 NumGauss=1141825356 NumPulse=226448017394 NumTriplet=452862338944 In v_BaseLineSmooth: NumDataPoints=1048576, BoxCarLength=8192, NumPointsInChunk=32768 Windows optimized setiathome_v8 application Based on Intel, Core 2-optimized v8-nographics V5.13 by Alex Kan SSE3xj Win32 Build 3330 , Ported by : Raistmer, JDWhale SETI8 update by Raistmer Work Unit Info: ............... Credit multiplier is : 2.85 WU true angle range is : 0.414118

Although it doesn't display any timestamps, it appears to show the task only restarting once, which I assume would be the restart after the system restart.
15) Message boards : Number crunching : 1073741205 Error Code (Unknown Error) (Message 1794044)
Posted 23 days ago by Profile Jeff Buck
But the question is - does the new build, either version, reduce the number that fall all the way through to 0xC000026B?

Temporary exits are untidy and to be avoided if possible, but are nothing like as serious as task errors. If we've eliminated the real horrors, I can live with the untidiness.

Funny, I would have thought any effort should have been directed toward fixing the broken leg, not just putting a bandage on it. Ah, well, socialized medicine seeps into everything eventually, I guess. ;^)

I'll have to see if I can manage to test that minor fix without sacrificing more than a couple of my CPU tasks.
16) Message boards : Number crunching : 1073741205 Error Code (Unknown Error) (Message 1794020)
Posted 23 days ago by Profile Jeff Buck
I just ran a shutdown test of the BOINC 7.6.33 version. It doesn't seem to have fixed the problem. The results appear to be about the same as that test I ran a few days ago of Richard's private build.
06-Jun-2016 10:00:45 [SETI@home] Started upload of 30my10aa.24060.21335.8.35.46_0_0 06-Jun-2016 10:00:53 [SETI@home] Finished upload of 30my10aa.24060.21335.8.35.46_0_0 06-Jun-2016 10:01:29 [SETI@home] Task 31mr10ac.31259.11122.7.34.193_1 exited with zero status but no 'finished' file 06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:29 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19917.416.17.26.156.vlar_0 exited with zero status but no 'finished' file 06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:29 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19958.0.18.27.184.vlar_1 exited with zero status but no 'finished' file 06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:29 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2089.416.17.26.230.vlar_0 exited with zero status but no 'finished' file 06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:29 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2120.416.18.27.29.vlar_1 exited with zero status but no 'finished' file 06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:29 [SETI@home] Task blc5_2bit_guppi_57451_28083_HIP69824_OFF_0028.2768.416.17.26.110.vlar_0 exited with zero status but no 'finished' file 06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:29 [SETI@home] Task 30my10aa.12339.476.14.41.113_0 exited with zero status but no 'finished' file 06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:29 [SETI@home] Task 31mr10ac.31259.23801.7.34.60_0 exited with zero status but no 'finished' file 06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:29 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.7399.831.18.27.189.vlar_1 exited with zero status but no 'finished' file 06-Jun-2016 10:01:29 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task 31mr10ac.31259.11122.7.34.193_1 using setiathome_v8 version 800 (cuda50) in slot 8 06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19917.416.17.26.156.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 6 06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19958.0.18.27.184.vlar_1 using setiathome_v8 version 800 (cuda50) in slot 3 06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2089.416.17.26.230.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 15 06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2120.416.18.27.29.vlar_1 using setiathome_v8 version 800 (cuda50) in slot 5 06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_28083_HIP69824_OFF_0028.2768.416.17.26.110.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 17 06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task 30my10aa.12339.476.14.41.113_0 using setiathome_v8 version 800 in slot 18 06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task 31mr10ac.31259.23801.7.34.60_0 using setiathome_v8 version 800 (cuda50) in slot 7 06-Jun-2016 10:01:29 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.7399.831.18.27.189.vlar_1 using setiathome_v8 version 800 in slot 11 06-Jun-2016 10:01:30 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.18897.416.17.26.187.vlar_1 exited with zero status but no 'finished' file 06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:30 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.18799.831.18.27.189.vlar_0 exited with zero status but no 'finished' file 06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:30 [SETI@home] Task 30my10aa.6571.13052.11.38.24_0 exited with zero status but no 'finished' file 06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:30 [SETI@home] Task 30my10aa.18777.17654.12.39.199_1 exited with zero status but no 'finished' file 06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:30 [SETI@home] Task 30my10aa.12339.19699.14.41.124_0 exited with zero status but no 'finished' file 06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:30 [SETI@home] Task 29au10ad.31633.244789.12.39.72_2 exited with zero status but no 'finished' file 06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:30 [SETI@home] Task 31mr10ac.31259.11122.7.34.193_1 exited with a DLL initialization error. 06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reboot your computer. 06-Jun-2016 10:01:30 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19917.416.17.26.156.vlar_0 exited with a DLL initialization error. 06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reboot your computer. 06-Jun-2016 10:01:30 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19958.0.18.27.184.vlar_1 exited with a DLL initialization error. 06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reboot your computer. 06-Jun-2016 10:01:30 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2089.416.17.26.230.vlar_0 exited with a DLL initialization error. 06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reboot your computer. 06-Jun-2016 10:01:30 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2120.416.18.27.29.vlar_1 exited with a DLL initialization error. 06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reboot your computer. 06-Jun-2016 10:01:30 [SETI@home] Task blc5_2bit_guppi_57451_28083_HIP69824_OFF_0028.2768.416.17.26.110.vlar_0 exited with a DLL initialization error. 06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reboot your computer. 06-Jun-2016 10:01:30 [SETI@home] Task 30my10aa.12339.476.14.41.113_0 exited with zero status but no 'finished' file 06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:30 [SETI@home] Task 31mr10ac.31259.23801.7.34.60_0 exited with a DLL initialization error. 06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reboot your computer. 06-Jun-2016 10:01:30 [SETI@home] Task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.7399.831.18.27.189.vlar_1 exited with zero status but no 'finished' file 06-Jun-2016 10:01:30 [SETI@home] If this happens repeatedly you may need to reset the project. 06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.18897.416.17.26.187.vlar_1 using setiathome_v8 version 800 (cuda50) in slot 0 06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.18799.831.18.27.189.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 19 06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task 30my10aa.6571.13052.11.38.24_0 using setiathome_v8 version 800 in slot 12 06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task 30my10aa.18777.17654.12.39.199_1 using setiathome_v8 version 800 in slot 13 06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task 30my10aa.12339.19699.14.41.124_0 using setiathome_v8 version 800 (cuda50) in slot 10 06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task 29au10ad.31633.244789.12.39.72_2 using setiathome_v8 version 800 in slot 1 06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task 31mr10ac.31259.11122.7.34.193_1 using setiathome_v8 version 800 (cuda50) in slot 8 06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19917.416.17.26.156.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 6 06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.19958.0.18.27.184.vlar_1 using setiathome_v8 version 800 (cuda50) in slot 3 06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2089.416.17.26.230.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 15 06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.2120.416.18.27.29.vlar_1 using setiathome_v8 version 800 (cuda50) in slot 5 06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_28083_HIP69824_OFF_0028.2768.416.17.26.110.vlar_0 using setiathome_v8 version 800 (cuda50) in slot 17 06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task 30my10aa.12339.476.14.41.113_0 using setiathome_v8 version 800 in slot 18 06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task 31mr10ac.31259.23801.7.34.60_0 using setiathome_v8 version 800 (cuda50) in slot 7 06-Jun-2016 10:01:30 [SETI@home] [cpu_sched] Restarting task blc5_2bit_guppi_57451_27376_HIP69732_OFF_0026.7399.831.18.27.189.vlar_1 using setiathome_v8 version 800 in slot 11 06-Jun-2016 10:04:40 [---] Starting BOINC client version 7.6.33 for windows_intelx86 06-Jun-2016 10:04:40 [---] log flags: file_xfer, sched_ops, task, cpu_sched

Fortunately, the shutdown didn't take long enough for any of the CPU tasks to error out, even though about half of them did restart once.
17) Message boards : Number crunching : 1073741205 Error Code (Unknown Error) (Message 1793700)
Posted 24 days ago by Profile Jeff Buck
Just ran across a host, 7321604, which has gotten some of these errors on v8.12 (opencl_intel_gpu_sah), in addition to CPU tasks. That's the first time I've seen that happen. The host is running Windows 7, BOINC 7.2.42.
18) Message boards : Number crunching : Open Beta test: SoG for NVidia, Lunatics v0.45 (Message 1793580)
Posted 25 days ago by Profile Jeff Buck
...the installer works fine...

That's about the only on topic post you've made here today. Would you please take the non-installer issues elsewhere. I'm getting quite tired of coming back to this thread when I see new posts, expecting to get the latest info on the installer, and finding post after post that are totally unrelated. Thank you.
19) Message boards : Number crunching : 1073741205 Error Code (Unknown Error) (Message 1793272)
Posted 25 days ago by Profile Jeff Buck
I'm getting the sense that if we really looked for them, we'd find that this is becoming an increasingly common error and something worth keeping an eye on to see if it's possible to nail down the configurations where it occurs.

Well, to kill a half hour or so before bedtime, I decided to go looking. It wasn't that difficult to find several more hosts that have recently experienced this error. Some of the configurations are ones that we've seen before, but there are a couple new ones, too.

7972610 - Windows 7 - BOINC 7.6.22
5630554 - Windows 7 - BOINC 7.6.22
7987945 - Windows 7 - BOINC 7.6.22
7995362 - Windows 7 - BOINC 7.6.22
7177464 - Windows 7 - BOINC 7.0.64
7031086 - Windows 7 - BOINC 7.0.64
7370900 - Windows 7 - BOINC 7.0.64
7032239 - Windows 7 - BOINC 7.0.64
7364388 - Windows Server 2008 "R2" - BOINC 7.2.42

Some of them just have one or two of the errors currently in their task lists, others a dozen or so, but I think I saw one with over 40. I'm pretty sure all were CPU tasks.

Ahhh...that should help put me to sleep. ;^)
20) Message boards : Number crunching : 1073741205 Error Code (Unknown Error) (Message 1793183)
Posted 26 days ago by Profile Jeff Buck


...There would have been 8 CPU tasks and 12 GPU tasks running at the time of shutdown,.....


Now that sounds like a well over committed CPU there. :-O

Actually, under S@H v8, that seemed to be just right....prior to guppi VLARs going to the GPU, anyway. Once all the dust settles with those and SoG and such, I do need to revisit it.

Have you tried using less CPU cores to see if that behaviour persists?

Cheers.

Actually, the problem can be traced back at least as far as last December (when I was running fewer tasks under v7), and I think Richard posted some even earlier examples in other projects. It also occurs here on my daily driver, with only two cores and a single GPU task on a GT630. I'm not sure what some of the other RPs configurations are but it's likely that, while a heavier load might magnify the problem at shutdown, it's not at the root of it.


Next 20

Copyright © 2016 University of California