Before the end of the month, we will try to see if cuda2.3 fixes some outstanding fft bug that people with gtx260 are experiencing.

Internal tests showed that it could be the case, but then everyone must run on 190.xx drivers.

No schedule for the change yet.

gdf

That would be great!
Can't crunch GPUGRID anymore on my GTX260 since you switched to CUDA 2.2...

---

pixelicious.at - my little photoblog

Before the end of the month, we will try to see if cuda2.3 fixes some outstanding fft bug that people with gtx260 are experiencing.

Internal tests showed that it could be the case, but then everyone must run on 190.xx drivers.

No schedule for the change yet.

gdf

HMM, SEEING HOW MY GTX 260 CRUNCHES FINE... With

System..

Vista 32-bit SP2
Dell Mb
BFG GTX 216 FOC 216 cores.


I've noticed lately that a lot of the evga cards have something bad in-relation to driver 190.38...

granted about a month or 2 ago, i had wu's erring out but i attribute that to Aqua Cuda wu's...

I'll wait for it! GTX260 from Gigabyte (192 cores) can't process gpugrid's Wus on x64 system.

But with this bug I have crunched few SETI cuda WUs and found a "Collatz Conjecture" project to make my gpu not be idle... :-)

---

From Siberia with love!

Always me with one GTX 260+ + 8800 GT on vista 64 and boinc 6.6.36

I try 190.38 driver. And I have always errors. The sames since driver superior than 182.5.
With 182.5 my two graphics cards works well.

Why why why....

My WUs don't complete in 24h anymore,
are the new WUs longer or is the app slower or is it my computer?

Always me with one GTX 260+ + 8800 GT on vista 64 and boinc 6.6.36

I try 190.38 driver. And I have always errors. The sames since driver superior than 182.5.
With 182.5 my two graphics cards works well.

Why why why....

Try using CUDA 2.3 and the 190.38 driver!

Hi,
for a couple of months i had no problems with boinc, Seti, Gpugrid and vista64. But when i came back from vacation a week ago, something strange happened. Windows did a lot of updates and the graphic-driver (?) reports, that a reset was necessary. A running gpugrid-wu reports an error. Most seti-wu work, but not all. This driver-reset happens 3 or 4 times a day.
I updated to the latest nvidia-drivers and BOINC and tried to understand, what other boinc-users report about ther problems. I've seen, that the GT260 seems to have a problem, but i do not understand all the other post about SDK, upcoming versions aso.
I would be really happy, if anyone could explain, what happend and which solutions are available in words, that are understandable for non-DSK users and people, who do not think, that running BOINC is the primary goal for a computer.
Kind regards,
Alexander

Surely I have cuda 2.3

And I have always the same errors like other drivers sup than 182.5 ---->

14/08/2009 21:59:47 GPUGRID Output file 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0_1 for task 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0 absent
14/08/2009 21:59:47 GPUGRID Output file 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0_2 for task 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0 absent
14/08/2009 21:59:47 GPUGRID Output file 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0_3 for task 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0 absent

the fact that you install the 2.3 toolkit is irrelevant.
You are still using the 2.2 runtime that we distribute.

gdf

And Why I have always this message ?


With 182.5 I crunch witout pb. with other driver it's catastrophe. all wus crash

Surely I have cuda 2.3

And I have always the same errors like other drivers sup than 182.5 ---->

14/08/2009 21:59:47 GPUGRID Output file 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0_1 for task 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0 absent
14/08/2009 21:59:47 GPUGRID Output file 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0_2 for task 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0 absent
14/08/2009 21:59:47 GPUGRID Output file 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0_3 for task 52-KASHIF_HIVPR_sub_so_ba1-15-100-RND7514_0 absent

Each project distributes the cuda runtime and FFT libraries. CUDART.DLL is the runtime and CUFFT.DLL is the FFT one. They put them into their BOINC project folder. This way its possible to have a different set of files for each project. Provided the driver you run can support the later DLL's it usually works.

The cuda toolkit has no bearing on any of this, unless you want to develop your own application. Its not needed. The project supply all the stuff need to run their science application.

The GPUgrid app seems to have particular problems with GTX260 cards. Driver 182.50 worked, but its only cuda 2.1 capable. GPUgrid have moved onto a cuda 2.2 app which means you'll need a minimum driver version of 185.x. The 190.38 driver supports cuda 2.3 as well as the older cuda versions, but as I said GPUgrid has particular problems with GTX260 cards. Why? Well if they knew that they would probably be able to work around it.

And before you think about putting the cuda 2.3 DLL's into the GPUgrid projects folder it won't work. BOINC keeps a signature of the file so it knows if its different to the one supplied by the project. There is a way around this using an app_info, but it takes a bit of expertise to create one.

---

BOINC blog

There is a lot of mess happening to my systems also...
1
winxp32
driver 190.
9600gt

2
winxp32
driver 190
9800gt

a lot of units fails now although (especially on the 9600gt) it worked flawless before. will got to nnw for gpugrid, try collatz

regards formulaman

Werkstatt / Alex,

sorry, currently there's not much you can do. Nevermind the talk about the toolit / SDK, it doesn't make a difference. You can try downgrading to drivers 185.xx or 186.18, but in many cases this has not helped.

Formulaman,

which errors do you get? Your computers are hidden, so we can't take a look.

MrS

---

Scanning for our furry friends since Jan 2002

My WUs don't complete in 24h anymore,
are the new WUs longer or is the app slower or is it my computer?

One thing I've seen is the card dropping to 2d clocks check your card clockspeed and if need be force 3d in riva

Well, is there any progress with cuda 2.3? When we will be able to start crunch again with our 260s? :-)

---

From Siberia with love!

We have now selectively assigning a cuda2.3 application to people with a 190 driver only. This is a test. We keep it on if it does not give problems.
It should be transparent to older driver users.

You need a recent BOINC version to receive the new application.
Only for Windows so far.

gdf

Recent as "6.6.x"?

MrS

---

Scanning for our furry friends since Jan 2002

I'll grab one and check it out.

vista 32-bit, gtx 260. 190.38

edit: it's running.....

The client needs to be able to report the driver version.
If in your host list you see the driver version, then you are probably fine, otherwise you would just receive the 2.2 application.

gdf