Message boards : Graphics cards (GPUs) : Gigabyte GTS 450 OC2 crashes
Author | Message |
---|---|
Cant help me , every day it happens, my cuda app | |
ID: 22178 | Rating: 0 | rate: / Reply Quote | |
Several of the tasks that failed on your system also failed on other systems. | |
ID: 22182 | Rating: 0 | rate: / Reply Quote | |
Some clients corrupt files on upload, and subsequent workunits fail as a consequence. Luckily they do so immediately. We are investigating. It might be related to new boinc client versions. | |
ID: 22183 | Rating: 0 | rate: / Reply Quote | |
Yes, looks like it; the 6.12.x Boinc Clients are not doing so well. Somewhat obfuscated by the odd CC1.1 card (to be ignored). Then there are the mixed GPU-series systems (GTX200 + GTX 400 or GTX500); the GTX 200 cards are failing some tasks. | |
ID: 22184 | Rating: 0 | rate: / Reply Quote | |
If you see | |
ID: 22185 | Rating: 0 | rate: / Reply Quote | |
It seems his host running XP is also running BOINC 6.13.1 which is unstable to say the least. I would suggest he goes back to 6.12.34 (the last official release) until the 6.13 series become stable. Even I haven't touched 6.13 yet and normally I run the latest and greatest. | |
ID: 22186 | Rating: 0 | rate: / Reply Quote | |
On this example task, all but one of the 6 failures was on Boinc 6.12.x. The exception was a Linux system with a GeForce 9800 GT (using the 6.14app) and Boinc 6.10.58 installed. | |
ID: 22187 | Rating: 0 | rate: / Reply Quote | |
If you see Here's an example of that from my errored tasks list. The first host to receive it runs BOINC 6.10.18 and it failed with the bincoordfile error. The second iteration went to a BOINC 6.10.58 host and failed with bincoordfile error. Third host runs 6.12.34, failed with bincoordffile error. Fourth host is 6.12.33, bincoordfile error. Fifth host is 6.10.58, bincoorfile error. Sixth host is 6.12.33, bincoordfile error. So it's the unreadable bincoordfile, not the BOINC version. I've been running 6.12.33 for a few months and have had very few errors, most of my errored tasks failed for all 6 iterations. This task from my errored tasks list went first to a Linux host on 6.10.58, then to my Linux host with 6.12.33 then to a Windows host with 6.12.33 which finished the task error free. No bincoordfile error on that WU, can't blame it on 6.12 versions, seems Linux or app version 6.14 was to blame. | |
ID: 22188 | Rating: 0 | rate: / Reply Quote | |
If you see As far as I understand how this project works, the workunint you make reference to is the same step issued to different hosts. All failed, because the previous step of this thread was processed by a new version BOINC client (this host corrupted the result on upload), but this host is not on this list. This task from my errored tasks list went first to a Linux host on 6.10.58, then to my Linux host with 6.12.33 then to a Windows host with 6.12.33 which finished the task error free. No bincoordfile error on that WU, can't blame it on 6.12 versions, seems Linux or app version 6.14 was to blame. This task failed on the first and the second host for different reasons, none of them are the "Unable to read bincoordfile" error. | |
ID: 22189 | Rating: 0 | rate: / Reply Quote | |
As far as I understand how this project works, the workunint you make reference to is the same step issued to different hosts. All failed, because the previous step of this thread was processed by a new version BOINC client (this host corrupted the result on upload), but this host is not on this list. Ah yes, I see now. Even though my 6.12 host isn't crashing tasks the results it uploads may be corrupt which will cause the next step to crash on 6 hosts in a row. Well, it's easy enough to roll back to 6.10.58. Can the validator be tuned to reject the corrupted upload thus causing a resend of the task? | |
ID: 22190 | Rating: 0 | rate: / Reply Quote | |
Did this problem arise subsequent to moving to a 5day return, without the early (3day) resend; did the early rescheduling mechanism avoid this issue? | |
ID: 22191 | Rating: 0 | rate: / Reply Quote | |
I did some statistics and possibly traced the problem to (unstable) BOINC 6.13.3 and 6.13.4. See this thread. | |
ID: 22195 | Rating: 0 | rate: / Reply Quote | |
Message boards : Graphics cards (GPUs) : Gigabyte GTS 450 OC2 crashes