I recommend to use driver 285 for 2xx cards

---

XtremeSystems.org - #1 Team in GPUGrid

Thanks guys, rolling back to 295.73 for my GTX 260 was surprising easy! (just a few clicks, no reboot) and GPUGrid is happily warming my toes once again.

The monitor-power bug in 295/296 shouldn't affect me.

Certainly thinking about a GTX 660! Although I hear it's not so good at heating... :-|

I have fixed the problem. HCC and GPUGRD can't work together.
I had removed the project HCC(Help Conquer Cancer) under WCG(World Community Grid), and finished a long rungs task in 30 hours..http://www.gpugrid.net/workunit.php?wuid=3841543

By the way, I also update my nvidia drivers version to 306.97WHQL(CUDA version 5.0). It works.

I got a big problem. I can't complete any task on my computer.
I use asus GTS 450 with NVIDIA DRIVERS 301.42WHQL 、 intel E5200 、 4G DDRII (PC3200)、Windows 7 Enterprise (x64) and BOINC 7.0.28(x64).

but...
It's seems too bad >.<

http://www.gpugrid.net/results.php?hostid=138448

Is there a possibility to switch earlier? ^^ or are there more changes needed before that needs time?

---

DSKAG Austria Research Team: http://www.research.dskag.at

we want to wait as long as possible such many people will be already using the new drivers.

gdf

From my experience, 3.1 apps tend to take substantially more time to run than the same type of WU running with the 4.2 app.

Take, for instance, this 3.1 WU - a Nathan respawn http://www.gpugrid.net/workunit.php?wuid=3863083
and this 4.2 WU - also a Nathan respawn http://www.gpugrid.net/workunit.php?wuid=3846597

Note that both were on my 580 machine, granted the same amount of credit, and that the 3.1 WU took almost twice as long as the 4.2 WU. Personally, I find situations like this particularly frustrating since it seems extremely inefficient to run 3.1 apps on machines that support the 4.2 app.

I have no direct experience in what it would take to program a project server to behave in this manner, however, projects like Einstein, Milkyway, and now Help Conquer Cancer at World Community Grid are able to figure out what type of WU to send, if any, based on the configuration of the computer requesting the work unit. While it would be more maintenance, perhaps it is within the realm of possibility to keep both and send only 4.2 apps to computers to that support it?

Aside from that, I am highly in favor of making the long queue 4.2 only if limitations exist that require that each queue is one app or the other - should both apps be kept, of course.

---

In theory the BOINC server looks at the driver and decide what to send you.
Rarely, it sends it the wrong way though.

Even more important to switch to the new app. As I said the new app will also reduce by 1/3 the upload size reducing strain on your broadband and our server.

We might anticipate it to mid december if nobody is against it.

gdf

From my experience, 3.1 apps tend to take substantially more time to run than the same type of WU running with the 4.2 app.

Take, for instance, this 3.1 WU - a Nathan respawn http://www.gpugrid.net/workunit.php?wuid=3863083
and this 4.2 WU - also a Nathan respawn http://www.gpugrid.net/workunit.php?wuid=3846597

Note that both were on my 580 machine, granted the same amount of credit, and that the 3.1 WU took almost twice as long as the 4.2 WU. Personally, I find situations like this particularly frustrating since it seems extremely inefficient to run 3.1 apps on machines that support the 4.2 app.

You can use my workaround to fix this problem on your side.

From my experience, 3.1 apps tend to take substantially more time to run than the same type of WU running with the 4.2 app.

Take, for instance, this 3.1 WU - a Nathan respawn http://www.gpugrid.net/workunit.php?wuid=3863083
and this 4.2 WU - also a Nathan respawn http://www.gpugrid.net/workunit.php?wuid=3846597

Note that both were on my 580 machine, granted the same amount of credit, and that the 3.1 WU took almost twice as long as the 4.2 WU. Personally, I find situations like this particularly frustrating since it seems extremely inefficient to run 3.1 apps on machines that support the 4.2 app.

You can use my workaround to fix this problem on your side.

Thanks.

I had not checked this thread in a while, however, if I get another 3.1 app on my machine, I will try this. 3.1 apps are especially slow for my 460. Most often, it is unable to crunch a 3.1 WU within 24 hours. However, my 460 is able to complete most 4.2 WUs in something like 12 hours. 3.1 v 4.2 on the 460 makes a substantial difference. It is almost as if I had bought another card. :)

---

In theory the BOINC server looks at the driver and decide what to send you.
Rarely, it sends it the wrong way though.

Even more important to switch to the new app. As I said the new app will also reduce by 1/3 the upload size reducing strain on your broadband and our server.

We might anticipate it to mid december if nobody is against it.

gdf

The last few days, 15% of tasks sent to me have been 3.1. Not what I'd call rarely. Any update on bringing the new app into production.

We can remove already 3.1 apps on the long queue, but we will not upgrade the application until new year.

gdf

+1

---

DSKAG Austria Research Team: http://www.research.dskag.at

I tried the suggestion above, and it seemed to work once. However, the same machine just got another Cuda31 job, and by estimating the time that it will take from the current progress, it looks like it is again running Cuda31 rather than Cuda42. According to progress vs run time, this will finish in roughly 48 hours on my machine. After applying the work-around, is this supposed to run all subsequent 31 tasks as 42 tasks? Noeilla's usually run in about 23 hours on my 460 with 42 rather than what looks like 48 for this 31 job.

---