Latest drivers (NVidia and ATI)

[SciManStev]

I ran bothe the 266.58 and 270.61 drivers for several days each, with no advantage one way or the other. My RAC stayed within the same total range. I did not suffer from the down clocking others had reported, nor the invalid wu's. Strictly from my point of view, there was no difference. I don't know about gaming though. I didn't bother to stop crunching in order tp play a game.

Steve

[Jason G]

I do get downclocking with the 480 here with driver 270.61, but only when I snooze or exit Boinc, and then only sometimes.  No driver crashes or invalid tasks, though the downclocking is annoying enough when I need to do development bench-runs that I may have to go back to 266.58

Jason

[Pepi]

I noticed down-clock only in this state: after I put three WU in parallel work, first three will have OK time, but after that crunching will be very slow. Restart solve this thing. If I use only 2 parallel WU , there is no such issue. Since I change from GTX 460 to GTX 560,  I will try it again.
Down-clock on 560 also, drivers downgrade to 270.51 ( beta)
On short ones

1 WU - 2:30  -    150 sec per WU
2 WU  parallel  - 4:13  -    126,5 sec per WU
3 WU  parallel  - 5:45  -    115 sec per WU

[Claggy]

275.27 Beta has been released today,

Claggy

[Pepi]

Updated
Now we will see rest: just sit and wait

[arkayn]

275.27 Beta has been released today,

Claggy

Installed just the driver and HD audio driver on my GTX 460. Now to see if they got the down clocking bug fixed.

[arkayn]

It took a bit, but it downclocked once again. Back to 266.58

[Pizzadude]

Yep, same observation here. Version 266.58 seems to be rock solid

It took a bit, but it downclocked once again. Back to 266.58

[Pepi]

Yep, same observation here. Version 266.58 seems to be rock solid

It took a bit, but it downclocked once again. Back to 266.58

Hm, I don't have downclock with this drivers. Works without problems at least 12 hours.

[arkayn]

It took about 36 hours or so. I also changed the working CUDA app on my machine. When I restarted BOINC, the GPU did not spin back up to full power.

[Fredericx51]

I still have ocasionell system-freeze, still use 266.58 and run LUNATICs, used the v0.37 installer,
host is an Q6600, stock(+),
this host.

Also run Einstein and a few CPU only, Projects. Since at 'hangs' i.s.o. BSOD, no useble 'log' or other
message.
Happens, once or twice a week, maybe heavy outside-temps, could be a reason, which I doubt.
I use cold air, atleast at night, which changes from 2-4C to 20C in 2 till 6 hours?!
I've seen the Q6600 with a 104C temp reading, but a sysinfo which reported 94C, still too high.
Time to reseat the Cooler. (A push/pull Coolermaster.)

[Pepi]

New drivers are out: 275.33!
Initial benchmark show at least 20% increase in speed on my 560Ti!
It is very good news!

[Jason G]

Looking good, with minor speedups & improved 'feel' during full crunch with test builds here too, on two different systems:
-> Win7x64 Pro/sp1 , GTX 480
-> WinXPx86 Pro/sp3 , GTX 260

I'm unclear as to whether nVidia may have robustified the new drivers to abuse from applications yet (might have to try break them  ) .  Here's hoping those problems slip quietly into history, even though our test app avoids triggering the issues, it would be a lot less painful for those who crunch other Cuda-enabled Boinc projects, or prefer to run stock.

Jason

[Richard Haselgrove]

Message from your messenger pidgeon: is there any way we can help to work out if the new drivers do help with the down-clock problem? If that can be established, I can start doing the rounds again....

[Jason G]

Message from your messenger pidgeon: is there any way we can help to work out if the new drivers do help with the down-clock problem? If that can be established, I can start doing the rounds again....

Hmm, running stock 6.10 or x32f in bench runs, repeatedly killing the processes via task manager should trigger it on effected systems if the driver remains sensitive to the bodgy cuda app exits.  I'm reasonably satisfied that x38b is viable for Beta soon to prove the V7 code, so I'll try a round of knabench abuse here with that & earlier known more abusive  variants. 

Feel free  to try likewise if your 470 ever was sensitive (repeatably).  Snoozing/unsnoozing Boinc with any pre-x37 series app, or another  project Cuda app should also trigger 'sticky downclock' if still susceptible to it under the new drivers.  x37-x38 series are somewhat hardened against it, though should still be possible through task manager abuse ( not recommended for live Boinc installations of course)

[Edit:] x32f still triggers sticky downclock on killing with task manager here... So don't do that unless you really want.

Rebooting & abandoning hope that drivers can make up for evil code

Jason