I have 10 machines running Asteroids, and ALL of them just started computation errors. I had to open my machines to other projects until this is fixed.

---

Heh, something odd happened a few hours ago, my i5 on Linux started completing
WUs in 1.5 minutes instead of normal 1.2 hours, guess thats related, they get validated so I guess they are ok.

These are with app "Period Search Application v102.10 (avx)" and wus ps_160915_input..

Very weird.. ;-P

Yesterday I added six computers to my account and today I got very pleasantly surprised with my statistics. I then got pleasantly shocked and later sadly so to see the rate at which my stats kept increasing...

There are two problems (maybe two different symptoms of the same issue):

A. Several computational errors, on one computer that I watched the tasks barely get to start before they get marked as failures. However not all tasks fail but I've got more than 200 tasks labeled with Error in just a day.

B. Extremely fast completion times. I have several computers running trough tasks in 150-300s but it should take more like 4000-8000s. I've seen it happen to the AVX tasks. They do get validated though...!

I'm guessing the results are rubbish? What will happen to stats, will someone eventually clean out these short run time tasks?

Melvyn and Alex, Same issues. Hope the moderators check this and post a response. In the mean time, I had to change to different projects. I hate doing that, Asteroids has been what started my BOINC "career", and I want to get back to it.

---

Yep, also a bunch of failures here. Some with SSE2, others with SSE3. But these are only a handful, most runs complete successfully.
As for the short run times, I do get those occasionally. I also had one with CUDA that completed in 172 seconds! http://asteroidsathome.net/boinc/workunit.php?wuid=52894026
It was validated with AVX by someone else who did it in ~300 secs. Maybe it's just a short WU, and not a bug.

The errors have stopped. I do not have ANY buffer set up, so those that have buffers may find errors for WUs received from 9/21 thru 9/23.

---

I'm still getting computation errors when using a Pascal gpu (gtx 1080). freshly downloaded tasks, btw.

Have a look, are those work units originally started in that time period of 21-23? It maybe new to you, but not new overall.

I guess they're old. Here's one that failed

http://asteroidsathome.net/boinc/workunit.php?wuid=52226661

I'll just let them error out and see if I start getting some good ones.

The problem with that though, is that I tried it before and one task, instead of erroring out immediately (no big deal) actually consumed my GPU for 100% for over 14 hours... that is some SERIOUS electricity wasted.

i just errored out over 500 tasks... i dont think i'm ever going to get a good one.

Errors just came back on all machines.

---

Happening to me as well. Opened my machine up to tasks and all I get are computation errors.

This has clearly been going on for a while, has no one modding the project noticed?

I am getting 24 errors at a time, likely, falsely reported as computational errors. The error occurs the moment the work unit is completely downloaded, not when actual computations are started, as this laptop can only process 4 work units at a time and is, at the moment, processing the last work 2 error-free work units, and 2 World Community Grid work-units. (I suppose, it is possible, that BOINC may stop processing the WCG units, given the high priority I have given Asteroids@Home, and the errors, immediately, occur then.)

I attached one fresh "Microsoft Windows running on an AMD x86_64 or Intel EM64T CPU" host to see how CPU tasks are doing at the moment.

All tasks with SSE2 and SSE3 application finish with immediate computation error.
Tasks with AVX application complete unnaturally fast, but without error. I can't see yet if they will validate successfully.

I can't see yet if they will validate successfully.

Yes, they seem to validate successfully. A task which now takes a couple of minutes to complete is treated similarly with old tasks that used to take hours to complete.

So, this current situation is basically damaging the long time "badge system" by heavily twisting the requirements of how much work is needed.

Hi, I am going to check this. I am very sorry, I still had some unexpected issues so I couldn't check the project.

I thought replacing my old graphics card with a new one caused it, but it seems that this has been happening to me since I started back on Asteroids@home a few days ago. Before the new card had arrived.

Went from an nVidia GTX 460 to an nVidia GTX 1060.

GPU GTX 1060 wrote:

<core_client_version>7.6.22</core_client_version>
<![CDATA[
<message>
The system cannot find the file specified.
(0x2) - exit code 2 (0x2)
</message>
<stderr_txt>
CUDA RC12!!!!!!!!!!
CUDA Device number: 0
CUDA Device: GeForce GTX 1060 6GB
Compute capability: 6.1
Multiprocessors: 10
Unsupported CC detected (CC2.0 and better supported only).

</stderr_txt>
]]>

GPU GTX 460 wrote:

<core_client_version>7.6.22</core_client_version>
<![CDATA[
<message>
The system cannot find the file specified.
(0x2) - exit code 2 (0x2)
</message>
<stderr_txt>
CUDA RC12!!!!!!!!!!
CUDA Device number: 0
CUDA Device: GeForce GTX 460
Compute capability: 2.1
Multiprocessors: 7
Grid dim: 56 = 7*8
Block dim: 128
Unsupported CC detected (CC2.0 and better supported only).

</stderr_txt>
]]>

I've also had a few CPU access violations or unknown errors, but I'm primarily concerned about GPU for now since it's rejecting them all flat-out. As far as I can tell, I can still do CPU fine.

Historically, the GTX 460 worked fine. Or rather, stderr said roughly the same thing but the exit status was success. The only difference was that instead of "Unsupported CC detected (CC2.0 and better supported only)" it said "05:15:13 (8272): called boinc_finish" or a similar string.

Please let me know if there's anything I can do to help.

I don't believe Asteroids supports Pascal GPUs yet.

I appear to be causing computation errors when I run and debug a c program. Asteroids seems to run fine when left alone. I recently looked at all sixteen asteroids tasks running on my computer and all of them were doing fine. After running my c program several of the tasks had computation errors. Am I causing those errors? If so, what can I do to fix the problem? Thank you.

Pretty obvious. Don't run your C program debug at the same time as crunching Asteroids.

---

A proud member of the OFA (Old Farts Association)