On my QuadroFX 570M (256MB) system the Lunatics x32f application does not work properly with new 270.61 drivers.

It is very likely to be system specific (card/amount of RAM) but:

Please check you are still getting valid results after upgrading!

---

Carola
-------
I'm multilingual - I can misunderstand people in several languages!

One of my GTX 460 768 MB GPUs constantly drops its frequency to 405 MHz after some time, generating an erroneous WU. I'm using stock application for Fermi, not Lunatics.
I moved back to older drivers. There wasn't noticeable increase in crunching speed with 270.61 at all.

---

I tried using the Beta version 270.51, which did cause my 480's to down clock to 405 MHz. So far my experience with the 270.61 released drivers has been fine. I have seen no performance increase, but there has been no down clocking either. My GPU voltage is at max, as they are running at 865 MHz, which may have something to do with it. As Miep said, this may be due to the individual system.

The biggest reason, at the moment, for using the Lunatics CUDA apps is that you will get a large decrease in the -12 errors. I used to get 6 or so a day using the stock apps, but now may get one every couple of weeks using the Lunatics apps.

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

On my QuadroFX 570M (256MB) system the Lunatics x32f application does not work properly with new 270.61 drivers.

....

What's the reason you think you have a driver Problem?

I can only see one error result on your Rig and that's a global Exit status 1 error.

Helli

I can confirm this issue also. I have a 1 GB GTX 460 which will successfully clock down the GPU when I exit BOINC, but will not clock back up when I re-start BOINC. This also happens if I just decide to snooze GPU crunching and then resume. This happened with both 270.51 and 270.61.

Perhaps it could be that with these driver updates, there was CUDA 4.0 functionality added, and that is for now causing some problems. It is just a guess of mine. The PhysX driver remains .0514

I thought my card was having issues, but I will just have to test out and see iff 266.58 is also displaying this same problem. Can anyone else report to that?

---

I installed 267.24, never tried them before. Used to be 266.35.
Those 267.24 seem to utilize GPU better with ~2%(96.1->97.9%) and no frequency drop so far, 3 hours since I booted the system with them on.

---

I went back to 266.58 as I had the same downclocking experience with the first beta of 270.xx, it would even do it in the middle of crunching.

---

On my QuadroFX 570M (256MB) system the Lunatics x32f application does not work properly with new 270.61 drivers.

....

What's the reason you think you have a driver Problem?

I can only see one error result on your Rig and that's a global Exit status 1 error.

Helli

I alpha test and I test offline if necessary - I didn't let the dodgy result go up in the first place.

---

Carola
-------
I'm multilingual - I can misunderstand people in several languages!

I updated my GTS 450 yesterday evening to the 270.61. Woke up this morning and found work units that should have been around 45 minutes taking around three hours to complete. So far the work is validating okay but I got back to the old 266.58 as fast as I could. My DCF is still high at 2.133 but it's falling and to completion times are coming back down.

---

PROUD MEMBER OF Team Starfire World BOINC

One of my GTX 460 768 MB GPUs constantly drops its frequency to 405 MHz after some time, generating an erroneous WU. I'm using stock application for Fermi, not Lunatics.
I moved back to older drivers. There wasn't noticeable increase in crunching speed with 270.61 at all.

My 460 cards do not run but crashes with the new drivers but works well with the supplied driver

4/19/2011 9:50:19 PM NVIDIA GPU 0: GeForce GTX 460 (driver version 25896, CUDA version 3010, compute capability 2.1, 738MB, 363 GFLOPS peak)

---

Driver 266.58 has a good track record. If the newer 270 series drivers don't work, I would suggest the 266.58 version. I am beginning to think that my over voltage is what is keeping my speed up. Without that, my 480's might down clock as well. They have been running at full speed with this driver for about 23 hours. I know there were some power limitations for the 590 series that were driver controlled, and would prevent you from upping the voltage too much, and destroying the cards. That may have had an effect on the other cards as well. As my voltage is maxed, and my GPU's can handle it, perhaps that is why I'm still stable. The 270.51 beta certainly did down clock my GPU's even with the higher voltage. It forced me to revert to 266.58.

Steve

Edit: Also, normally I wouldn't need to reboot when I upgrade a driver, but this time I did just to be sure. I didn't do that when I used the 270.51 driver. This is most likely not affecting anyone else, and may not have anything to do with why mine is working, but it is information.

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

Driver 266.58 definitely seems the one to use. I had never experienced this downclocking issue before either. with 270.51 and 270.61 the card will run at the clocks I set it too fine, but if I exit/snooze BOINC and re-start BOINC it will stay downclocked at 405/810. Only way to go back to my clocks of 900/1800 is to restart the machine.

I for one will be reverting to the 266.58 drivers. It is however curious as to why the card doesn't clock back up like it should.

PS: I should mention that my 460 also has a slight overvolt of +10mv. It had gone through some 7000 WU's before showing throwing out it's first error and it was when I was running 270.51 luckily the next day 270.61 came out and I haven't had anymore errors since. Just now I reported 141 tasks, and all were completed successfully and validated.

---