Is there something particularly different about the IBUCH_TRYP WU's? I have had a 100% error rate on these WU's over the past several days, while have had very few issues with other types of WU's.

Seems odd that it seems to affect the one type of WU more than others. I do generally have one error every now and then historically, but the past week has been terrible. I removed all overclocking, but that hasn't helped the IBUCH_TRYP WU's. Any ideas? I'd prefer not to have to just abort all these as they do not appear to work on my system (2x 8800GT, 1x 9500GT).

Checking the WU's, it appears others have had issues with a lot of those same WU's as well. Some have been successfully finished, but there are errors on 8800/9800 GT's and GTX2xx cards (though the GTX2xx seem to fair a little better on these WU's).

Now you come to mention it, four of the seven errors currently visible across my three cards are iBUCH_TRYP, though all are different sub-types (kickout, kickout1, kickin and reverse). reverse was particularly irritating - it ran for 52,500 seconds before erroring: most of the others have been relatively quick and painless.

On the other hand, I can see three successful runs too (repro, kickin and 169).

All my cards are 9800GT variants from the same manufacturer: two have both successes and failures, so no obvious explanation there.

Earlier this afternoon I had all WU's error out (at least those running on the 9500GT). No change in my system, no new drivers, new new BOINC, no OC'ing. Temps lower than normal given we're getting into fall. Not sure what happened, but I rebooted. Now I have 3 WU's in process and no errors after about an hour (all the errors today were after a few seconds). Two IBUCH_TRYP WU's in the queue, so we'll see if it was just some weird thing with my system that gave much higher than normal error rates. Hopefully that is the case, though I don't have an explanation.

Looking at a fuller log, six out of my last 13 errors have been IBUCH_TRYP, but OTTO_HERG are almost as bad: 4 out of 13. I've had errors with OTTO_HERG4, 5, 7 and 8.

It's particularly annoying when it happens almost 80% of the way through a long task: compare the last two tasks for host 43404.

The IBUCH_TRYP WUs are failing on lesser cards and succeeding on the GTX 260 and above.
Here's 5 that failed on multiple "below 260" cards and then succeeded on GTX 260 or higher:

http://www.gpugrid.net/workunit.php?wuid=947203
http://www.gpugrid.net/workunit.php?wuid=939689
http://www.gpugrid.net/workunit.php?wuid=936708
http://www.gpugrid.net/workunit.php?wuid=939220
http://www.gpugrid.net/workunit.php?wuid=941652

It also happens on some other WU types but not as often:

http://www.gpugrid.net/workunit.php?wuid=934230
http://www.gpugrid.net/workunit.php?wuid=939398

In general there seems to be more and more a trend toward WUs not running on sub GTX 260 GPUs. A very bad trend IMO.

Another WU that's failed on 4 machines, including a GTX 295:

http://www.gpugrid.net/workunit.php?wuid=956237

Another WU that's failed on 4 machines, including a GTX 295:

http://www.gpugrid.net/workunit.php?wuid=956237

Cheers for this thread guys.

I just looked at my previous 5 failures which failed mysteriously with no OC - they failed either on HERG or TRYP tasks. Each of these tasks had another 8800gt/9800gt fail on them, before being successfully completed by a GT260.

Is there a way for the server to detect the graphics card model and send different types of task? I don't want to be wasting resources on tasks which are going to fail.

Is there a way for the server to detect the graphics card model and send different types of task? I don't want to be wasting resources on tasks which are going to fail.

Is there a way for the server to detect the graphics card model and send different types of task? I don't want to be wasting resources on tasks which are going to fail.

That would be nice.

Is there a way for the server to detect the graphics card model and send different types of task? I don't want to be wasting resources on tasks which are going to fail.

That would be nice.

Now the new TONI_HERG WUs are failing on the sub GTX 260 cards :-(

They are suggesting a G200-based card as the minimum these days for here, so its quite likely that none of them will run properly unless you have GTX2xx card.

Graphics card:

* (one or more)Recommended: Geforce GTX 250-275-280-285-295, Tesla10

The Home page has a mistake, and they have been told about it.
The same mistake has been made many times by many people, including me.

There is a GTX260 and a GTS250, but no GTX250!

The GTX260 cards can either have 196 or 216 shaders. Usually a card with 216 shaders will have 216sp on the box.

The GTS250 does not use a G200 core.

The GTX260 216sp is on My List!
My one works Perfectly - 100% success during last 2 weeks running 24/7.

Its a Palit GTX260 216sp, with 2 fans, and it sits at about 62 degrees C.
They have GT200 55nm cores.

People should note that the GTS 250 uses a G92 core which is 65nm.
The one I have is struggling at the minute. 25% fail time. But I will keep it attached for now.

I had to stop trying to support the project with my 8800 GTS 512, which was not far off the performance of the GTS 250 - until recently that is, when most tasks started to fail.

It might go towards the deposit for a G300 card, if they ever turn up!

Just finished an IBUCH .... erev
http://www.gpugrid.net/result.php?resultid=1707999
on a 250
http://www.gpugrid.net/show_host_detail.php?hostid=26091 .
looks like you found a way around the bug. Congrats
Now Tony_Herg
Ciao
____________