The new application will soon make it to production.
You need to have the latest drivers to use it, because it is compiled with cuda4.2.

Linux: 295.41 or greater
Windows: 301.32 or greater

Thanks. I'll upgrade the new driver as soon as possible.

---

Dreams do not always come true. But not because they are too big or impossible. Why did we stop believing.
(Martin Luther King)

Ready to test it here!!! ;)
http://www.gpugrid.net/show_host_detail.php?hostid=104446

The new application will soon make it to production.
You need to have the latest drivers to use it, because it is compiled with cuda4.2.

Linux: 295.41 or greater
Windows: 301.32 or greater

When exactly will it been in production (definition of "soon")? I am unable to upgrade my drivers immediately (traveling), so will my gpus be sitting completely idle once the switch is made?

I have one system with beta 301.24 (not new 301.42 WHQL drivers for Windows), and another with 295.73. I know the latter will not work, but I was under the impression the beta drivers included cuda4.2.


Obviously, I'd prefer a week's notice to manage the drivers, but just trying to understand if one or both of the rigs will be useless to GPUGrid until I can update to the latest WHQL driver.

Let's say around Thursday next week.

If you have the old driver, the old app will still be running, but later only the cuda4.2 application will be out for the long queue.

gdf

Let's say around Thursday next week.

If you have the old driver, the old app will still be running, but later only the cuda4.2 application will be out for the long queue.

gdf

OK. That sounds fine. I should be able to update them next Friday (1 week from today), so it sounds like I will still be able to contribute with both machines without interruption.

Good deal.

Sounds great gdf. Looking forward to bringing my gpus back over.

The new application will soon make it to production.
You need to have the latest drivers to use it, because it is compiled with cuda4.2.

Linux: 295.41 or greater
Windows: 301.32 or greater

Sorry, this is beyond my ken. I want to do the right thing; but i have absolutely no clue as to what you mean. 295.41 looks like an Nvidia driver number, yet we were advised not to use Nvidia 295.X.

If you could be more specific. You currently have 15,901 users on 29,559 hosts (BOINCStats). I would think that there are many many of us who need more specificity. I personally am on an i7 Win7 machine with GTX580's.

---

Please check out my blog
http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

Found 301.42 for the GTX580's. Installing. Hope the thing doesn't blow up.

---

Please check out my blog
http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

Only windows had the 295 and 296 driver issue. 301.42 will be just fine mitrichr.

Interesting - to me, at least - Maingear delivered my Shift Super Stock with 2.9 drivers, I had no problems.

I exited BOINC before I did the update, and then re-started it. I assumed that was good practice. Is there a FAQ for the project addressing issues like driver updates, proper procedures, etc.?

I assume that among your current 15,000+ users there are significant numbers of people like me, delighted to be helping on the subjects of this project, yet technically as illiterate as am I.

---

Please check out my blog
http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

I installed the new drivers whilst 2 existing tasks were running.
(Even though I had exited the BOINC Manager)
They immediately reported a 'computation error'.
Not charmingly good news.

Personally, I would recommend (on the basis of this costly experiment), that one selects "No new tasks", waits for the back log to clear, and only then install the new GPU drivers.

I meant to say 295.XX drivers.

Mr Gray, thanks for baring your tale of woe.

Judging from your 52 million credits, you have been around this project for a fair amount of time. Yet, you had a problem. This is a perfect example of why I am asking for greater detail on what we are to do.

---

Please check out my blog
http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

I installed the new drivers whilst 2 existing tasks were running.
(Even though I had exited the BOINC Manager)
They immediately reported a 'computation error'.
Not charmingly good news.

Personally, I would recommend (on the basis of this costly experiment), that one selects "No new tasks", waits for the back log to clear, and only then install the new GPU drivers.

What you have to make sure you do when you exit boinc is that you actually exit boinc. Hit control, alt, delete and go to task manager, and make sure the tasks aren't running. If they aren't, than upgrade the driver. You can finish the tasks with the updated driver no problem at all. I have several times, with no crashes what so ever.

Though, don't run defrag when running boinc on a windows 7 machine, I did, and I crashed 3 units. Live and learn!

Interesting side effect of upgrading to 301.42 - My GTX 460 which was previously clocked to 815MHz and was stable at that speed now won't run any higher than 797MHz.... :-(

Bedrich has excellent advice.
Quite why this was not screamed from the rooftops by BOINC or GPUGRID when advising the upgrade is beyond me.
And I am a professional computer programmer, but naïvely trusted the instructions to be complete.
As you suggest, one lives and learns. I trust that the admins will do the same.

Not everybody running this project reads the forums - perhaps it might be an idea to send out an email to all participants warning them they will need to update their drivers to continue participation.

Bedrich has excellent advice.
Quite why this was not screamed from the rooftops by BOINC or GPUGRID when advising the upgrade is beyond me.

Driver installation issues were discussed earlier on this forum, but this time a warning could have been useful. The search button looks for posts from the last 30 days, so you have to use the advanced search to find older posts about driver upgrade problems.
I did upgrade my drivers several times without stopping BOINC manager, but I have Windows XP, and this needs a restart to load the new driver. Windows 7 can do this without restart, but it works like unloading the old driver then loading the new one, and there is a short time in between while there is no display (and CUDA) driver on the system at all. The CUDA application does not receive any warning from the system about the old CUDA driver is going to be removed, and it should wait while the new driver will be available. So it still tries to call the old driver's libraries, which will obviously lead to a computation error while there is no CUDA driver on the system, or the new CUDA driver is there, but the CUDA application (not knowing about the driver change) tries to use the old one.
However last time when I was upgrading my drivers, my tasks failed just like yours, and I got frustrated just like you did.

A very important advice for everyone: always exit the BOINC manager before upgrading drivers, and don't forget to check the "exit scientific applications" checkbox on exiting.
After upgrading, you should restart your machine, or restart BOINC manager manually.

Interesting side effect of upgrading to 301.42 - My GTX 460 which was previously clocked to 815MHz and was stable at that speed now won't run any higher than 797MHz.... :-(

I've noticed that the GPU usage is higher with the new (290 and up) drivers. Maybe that's why you can overclock less.

I have updated the drivers to 301.42 and BOINC to 7.0.25 and am experiencing a large increase in failed units