biodoc - it's on acemdbeta and short now. Please test it!

Matt

Ok, will do. Finishing up a windows cuda 6.5 long WU in about an hour.

Thanks!

There'll be a CUDA 6.5 app for linux later today.

Will it work for my 780Ti or is it exclusive for the 980/970?

I've revised the scheduling policy rules in the original post.

I havr a GTX460 which has not had work for over a day (long)

---

Radio Caroline, the world's most famous offshore pirate radio station.
Great music since April 1964. Support Radio Caroline Team -
Radio Caroline

Hi

no more WUs (Short and Long)

GtX 750ti - Linux - nv-343.22
GTX 780 - Linux - nv-343.22
GTX 780ti - Linux - nv-343.22
GTX 660ti - Linux - nv-343.22
GTX 760 - Linux - nv-343.22

Veneto,

Is your BOINC client new enough to be reporting the driver version number?

Matt

sabayonino, I see that you are getting work now.

Matt

sabayonino, I see that you are getting work now.

Matt

Now all my gpus are crunching :) (cuda65)

so my boinc client version is 7.2.42 for all hosts with gpu

maybe it was a temporary problem :)

tnx

I have more or less the same issues on this host http://www.gpugrid.net/results.php?hostid=178360

Boinc 7.2.42
Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-36-generic x86_64)

mar 07 ott 2014 11:53:33 CEST | | CUDA: NVIDIA GPU 0: GeForce GTX 780 Ti (driver version unknown, CUDA version 6.5, compute capability 3.5, 3072MB, 2987MB available, 6022 GFLOPS peak)
mar 07 ott 2014 11:53:33 CEST | | OpenCL: NVIDIA GPU 0: GeForce GTX 780 Ti (driver version 343.13, device version OpenCL 1.1 CUDA, 3072MB, 2987MB available, 6022 GFLOPS peak)

I'm able to get short workunits *only*, no matter what I try

Hi Valterc


as reported here

only shorts are available

The Linux cuda65 app is on long now.

Matt

Hello,

unfortunately I'm getting computation errors most of the time.
I've got two GTX 570 with 2.5 GB VRAM each, newest driver 344.11.
Doesn't matter if I'm in SLI or not.
Other GPU projects like SETI, Einstein or Asteroids run fine.
Is there anything I can do?

unfortunately I'm getting computation errors most of the time.

If you take a look into your tasks details, you could see the reason for those errors:

# The simulation has become unstable. Terminating to avoid lock-up (1)

This error is a sign of an unstable GPU. The root of this instability can be various:
- Too high GPU temperature (above 80°C - so this is not for you)
- Too low GPU voltage for the given GPU clock
- Too high GPU clock for the given GPU voltage (e.g. an aging GPU could not run even at factory settings)
- Too high GDDR5 frequency
- Insufficient, low quality or (nearly) broken PSU
- Too high transient resistance on the PCIe power connectors (usually caused by Molex->PCIe converters), or on the two 12V pins of the 24-pin MB power connector

I've got two GTX 570 with 2.5 GB VRAM each, newest driver 344.11.

This card has twice as much memory chips as a standard GTX570 has, so perhaps the GPU can't drive the memory data lanes that fast.

Doesn't matter if I'm in SLI or not.

SLI is usually a source of random errors.

Other GPU projects like SETI, Einstein or Asteroids run fine.

Other GPU projects has obsolete GPU applications built on older CUDA versions, while GPUGrid uses the latest (CUDA6.5 at the moment), therefore other projects couldn't stress the GPU as much as the GPUGrid client does.
The "GPU usage" measurement is misleading.

Is there anything I can do?

Check all power connectors in your PC for burnt ones.
Lower the GPU clock by 100MHz steps until it gets stable, if it doesn't work then try again by lowering the GDDR5 frequency by 100MHz steps.
If your GPU gets stable by lowering the GPU clock at some point, you can try to raise the GPU clock by 10-20MHz steps, while it doesn't cause these "simulation became unstable" messages, then increase the GPU voltage by 12.5mV, and repeat increasing the clock while the GPU doesn't get hot.
Beware of that different GPUGrid batches stressing the GPU differently, so if there's no stability headroom in your settings, some harder workunits could fail.

Thank you very much for the detailed information.
I checked the system and everything looks fine.
I lowered the clocks from 732 mhz to 650 mhz, but had 3 driver crashes while processing 2 short run WUs.
However, no computation errors, both completed successfully.

And the next WU crashed again at about 10% :-(