You guys really need to sort out your GTX 1080 crunching because all of these computational errors are screwing up my workflow for the 980ti that is also in the same system. Also my 1080 can't help your project at all and is stuck doing other projects.

Don't think they have one yet and I don't think you can expect them to adapt the App to new tech as soon as it hits the street.

Why not take the 1080 out for now?

You can edit your cc_config.xml file to "exclude GPU" by device number against a project to prevent it from receiving work here, but allow the 980Ti to run tasks here and still use the 1080 elsewhere.

https://boinc.berkeley.edu/wiki/Client_configuration

<exclude_gpu>
Don't use the given GPU for the given project. If <device_num> is not specified, exclude all GPUs of the given type. <type> is required if your computer has more than one type of GPU; otherwise it can be omitted. <app> specifies the short name of an application (i.e. the <name> element within the <app> element in client_state.xml). If specified, only tasks for that app are excluded. You may include multiple <exclude_gpu> elements. If you change GPU exclusions, you must restart the BOINC client for these changes to take effect.

<exclude_gpu>
<url>project_URL</url>
<device_num>N</device_num>
<type>NVIDIA|ATI|intel_gpu</type>
<app>appname</app>
</exclude_gpu>

For example, if your 1080 is device 1 (according to the Boinc log), then the following should prevent it's use at GPUGrid if you add it to your cc_config file and Save As all file types:

<exclude_gpu>
<url>http://www.gpugrid.net/</url>
<device_num>1</device_num>
</exclude_gpu>

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Or instead of masking the problem you could get all of the power of all of the thousands of 1080s out in the public

I can't recompile the ACEMD app using the CUDA 8 Toolkit for them, so this is just a help you work-around until the people who can, do.

Anyone in this 'mixed-GPU' situation can also exclude the long app and allow any Beta's that might turn up some time down the line to run on their Pascal's.

<exclude_gpu>
<url>http://www.gpugrid.net/</url>
<type>NVIDIA</type>
<device_num>1</device_num>
<app>acemdlong</app>
</exclude_gpu>

There is a short task queue too, but that's empty ATM. Perhaps the devs would want to use it for testing also? Note that I've had no advice that the devs are working on this or how long it might take them to get to Beta. Last I heard they didn't have a Pascal to even start to work with.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Or instead of masking the problem you could get all of the power of all of the thousands of 1080s out in the public

There isn't a problem as you put it.

GPUGrid has not and probably will not adapt an App for Pascal until they have a card to test for themselves and a reason for doing so that stretches beyond one or two users having one of these cards.

Or instead of masking the problem you could get all of the power of all of the thousands of 1080s out in the public

There isn't a problem as you put it.

GPUGrid has not and probably will not adapt an App for Pascal until they have a card to test for themselves and a reason for doing so that stretches beyond one or two users having one of these cards.

One or two users? They have sold 10s of thousands and they are never ever in stock in our local microcenter. They sell anywhere from 5-10 a day and that's just one store. They are 15-20% faster than a titan x. Why you would not try to get these cards running at all costs is beyond me.

One or two users? They have sold 10s of thousands and they are never ever in stock in our local microcenter.

That may well be the case but GPUGrid has only got around 1,000 active crunchers (if that) and won't be many with a 1080.

Of course I want them to take advantage of Pascal cards, and they will, just not yet.