Is the problem whit GTX 260, OK now?? And if that the case, what drivers and boinc version is recomanded??

Is the problem whit GTX 260, OK now?? And if that the case, what drivers and boinc version is recomanded??

In a word - No. Your best bet for the GTX260's is use them on another project until nVidia can fix things or the project comes up with a work around. If you do want to use them for GPUgrid expect around a 50% (or worse) error rate, depending on the mix of work units that you get.

The last working set of drivers (for the GTX260) was the 182.50, but they only support cuda 2.1. The current app needs at least cuda 2.2 so that means the 185.xx drivers, or later are required.

The project is currently recommending BOINC 6.10.3, however I have found 6.10.7 .11 and now .13 seems to be stable from my testing.

---

BOINC blog

We are implementing a workaround, which is quite drastic. We will make an application just for 260 which does not use PME. Clearly only some workunits can run there, but at least we move on without waiting.
When in place, it will be advertised from the news.

gdf

Please have it as an option not as default. Not all is affected by this bug.

---

Please have it as an option not as default. Not all is affected by this bug.

Agreed, I have been running my GTX260s for months and I don't think I have seen this problem at all, or at most once or twice in all that time. Though I am now running another project in parallel so my GPU Grid run time on those cards is reduced, I am still not that avid to lose more compute time if it is not needed...

Of course, given no choice I can always select other projects for the GTX260 cards and move on ... though I would rather not ...

Options are a good thing ... :)

It would not matter if you GTX260 works, then it will also work with the second application. It is just more work for us, that we need to maintain two queues.

gdf

Yes, I would also prefer that my working gtx260 gets the "normal" work. You could just add an option to the preferences that says: "if your gtx260 doesn't work, check this!"

Like you can check/uncheck astropulse or gpuwork at seti.

I really would want to have such an option available!!

Yes, I would also prefer that my working gtx260 gets the "normal" work. You could just add an option to the preferences that says: "if your gtx260 doesn't work, check this!"

Like you can check/uncheck astropulse or gpuwork at seti.

I really would want to have such an option available!!

For me at least, such an option would need to be machine specific as I have 1 260 that runs without error and 1 that errors almost every WU.

Of course, if there's no performance hit with the new 260 app, there'll be no need for the option.

But, option or not, I'd be happy just to have both my 260s running again.

and then there's my gtx295 with its GPU1 problems :(

It would not matter if you GTX260 works, then it will also work with the second application. It is just more work for us, that we need to maintain two queues.

But aren't we having 2 queues based on what you said?

Clearly only some workunits can run there, but at least we move on without waiting.

---

We are implementing a workaround, which is quite drastic. We will make an application just for 260 which does not use PME. Clearly only some workunits can run there, but at least we move on without waiting.
When in place, it will be advertised from the news.

gdf

Thanx for your work on this problem! I am waiting for this application for buggy 260s.

---

From Siberia with love!

I keep seeing references to this problem, but have never seen is on my own MSI 260. There's other people I know that are also running MSI without a problem. So does this bug only affect certain brands? Is it a problem with EVGA or are other brands affected?

We are implementing a workaround, which is quite drastic. We will make an application just for 260 which does not use PME. Clearly only some workunits can run there, but at least we move on without waiting.
When in place, it will be advertised from the news.

gdf

Have you done a poll or run a query on the database to see how many 260s do not run correctly on the stock WU? Which mfg makes the 260s that do not run?

If the erroring 260 are few, it doesn't make sense to me to make extraordinary effort to support them. Maybe those cards need a firmware upgrade.

My MSI 260s run just fine.

I have 2 EVGA GTX 260 216 that are 55nm and run flawless.
I had 1 EVGA GTX 260 192 65nm that would not, RMA'd.
The 1 EVGA GTX 260 192 65 that I got from RMA also does not run without error.

Is it the older 260's with problems? My newer ones are great.

This could happens, I have similar experience. Was trying several times to add 4th card to perfect working trinity of ASUS GTX 260's (216C, 55 nm). 4th card was reference Nvidia (192's , 65nm).
Windows was seeing it, GPU-Z was seeing it (4th card added). Starting GPUGRID resulting of immediate crash with BSOD, with routines of memory dumps & system restart. System records say's that the reason was graphic driver. Pulling out old style reference card from the system & restarting it returns it to the normal functionality. Thinking, that the problem is flying somewhere around old 192's Core reference design card.

---

I have 2 x GTX260 (Palit brand, 216 sp). They worked fine using 182.50 drivers. After upgrading drivers they don't. 185.xx, 186.xx and 190.xx drivers don't work with GPUgrid.

The newer drivers and cuda 2.3 works fine with the Einstein cuda app (in beta testing) and the Seti cuda app, so thats what its been doing since the driver upgrades.

I see Palit dropped the GTX260 a while back, they only have the OC'ed version available and that has probably been killed off in the last week or so.

---

BOINC blog

I have a GTX260/216 (55nm) (MSI) that runs GPUGrid with no problems and a GTX260/216 (65nm)(EVGA) that will not run either GPUGrid or Collative without an error. Both run 190.38 drivers.

6 BFG 260 216 and 2 EVGA 260 216 without any issues.

---

Looks like most 260 216s mentioned in this thread work, but not the 192s.

Does anyone have a 260 192 that works on GPUGrid?

Has anyone had success running a 192 core 260 on Linux? Mine were on Vista64, thinking about trying Linux.

Looks like most 260 216s mentioned in this thread work, but not the 192s.

Does anyone have a 260 192 that works on GPUGrid?

I have a 260 216 and it does not work under vistea 64 and win7 64. So I changed as many others to collatz.

sorry.