Someone tested already the new nVIDIA driver 285.x WHQL?

How it's (related to S@h CUDA speed) compared to the older (on which system (OS & hardware))?


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

---

I've loaded three different versions (XP_32b, V/7_32b, NB_V/7_64b) so far, and all are running OK. I'll leave the speed comparisons to those who worry about such things - I'm more concerned about reliability.

On my laptop it's 285.62 and it runs fine, as fast as 280.26, maybe a little bit faster but without doing any testing.

I have been running it now for 24hrs on my machine and it works great (2X GTX480). No down clocking or any other issues in games or Seti.

---

about to upgrade myself, will let the masses know how that goes

Someone tested already the new nVIDIA driver 285.x WHQL?

How it's (related to S@h CUDA speed) compared to the older (on which system (OS & hardware))?


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

Also ok here, to all my machines with XP, WIN7, 32 and 64 bit.

Not faster but it is stable.

Note that the same driver is 285.58 for win Xp, and 285.62,for other OS.

---

Someone tested already the new nVIDIA driver 285.x WHQL?

How it's (related to S@h CUDA speed) compared to the older (on which system (OS & hardware))?


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

Also ok here, to all my machines with XP, WIN7, 32 and 64 bit.

Not faster but it is stable.

Note that the same driver is 285.58 for win Xp, and 285.62,for other OS.

I have downloaded 285.62, but I'm in no hurry to upgrade as I'm running 285.38 on Win7 Pro x64.

---

Savoir-Faire is everywhere!
The T1 Trust, T1 Class 4-4-4-4 #5550, America's First HST

Just upgraded on my GTX560 machine.

Also attempted to try 6.13.9, but there is a bug that causes it to not be able to read the client state file and it reinitialized all projects on every restart of the client.

---

I upgraded last night. It downclocked one of my 480's, but that may have been due to other things I was doing. It ran fine over night.

The 480 it downclocked, has had problems. The other day I had to reduce the memory speed from 2065 MHz to 2055 MHz to keep it from downclocking every few days. The other 480 has been stable at 2075 MHz for months. Both GPU's have the core speed set at 871 MHz.

Steve

---

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

Tim wrote:

(...)
Note that the same driver is 285.58 for win Xp, and 285.62,for other OS.

Yes, because of this I wrote 285.x WHQL .. ;-)

-------------------------

Later (maybe weekend) I will make again a bench test.

To now 275.33 was the best for my system (E7600 & GTX260 OC, WinXP 32Bit) and S@h CUDA. 280.26 use more CPU time.


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

---

I upgraded last night. It downclocked one of my 480's, but that may have been due to other things I was doing. It ran fine over night.

The 480 it downclocked, has had problems. The other day I had to reduce the memory speed from 2065 MHz to 2055 MHz to keep it from downclocking every few days. The other 480 has been stable at 2075 MHz for months. Both GPU's have the core speed set at 871 MHz.

Steve

Might suggest a thorough dust bunny removal from the problematic 480...
It has taken care of some GPU downclocking problems that have arisen over time with a couple of my cards. Or it could just be aging, and will no longer support the previous OC speeds. Have seen that happen too.

---

"Time is simply the mechanism that keeps everything from happening all at once."

I upgraded last night. It downclocked one of my 480's, but that may have been due to other things I was doing. It ran fine over night.

The 480 it downclocked, has had problems. The other day I had to reduce the memory speed from 2065 MHz to 2055 MHz to keep it from downclocking every few days. The other 480 has been stable at 2075 MHz for months. Both GPU's have the core speed set at 871 MHz.

Steve

Might suggest a thorough dust bunny removal from the problematic 480...
It has taken care of some GPU downclocking problems that have arisen over time with a couple of my cards. Or it could just be aging, and will no longer support the previous OC speeds. Have seen that happen too.

No dust. Water cooled. It might be time to redo the water blocks, but that is a big job. Temps are 55°C, 57°C Max.

Steve

---

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

I upgraded last night. It downclocked one of my 480's, but that may have been due to other things I was doing. It ran fine over night.

The 480 it downclocked, has had problems. The other day I had to reduce the memory speed from 2065 MHz to 2055 MHz to keep it from downclocking every few days. The other 480 has been stable at 2075 MHz for months. Both GPU's have the core speed set at 871 MHz.

Steve

Might suggest a thorough dust bunny removal from the problematic 480...
It has taken care of some GPU downclocking problems that have arisen over time with a couple of my cards. Or it could just be aging, and will no longer support the previous OC speeds. Have seen that happen too.

No dust. Water cooled. It might be time to redo the water blocks, but that is a big job. Temps are 55°C, 57°C Max.

Steve

Ahh....forgot you are doing the water cooling thingy. Temps look just fine. Could just be the component aging bit then.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Just adding my two cents worth here. I upgraded last night in my little E5400 dual and GTS 450. Has been running about 24 hours with no problem. Seems to be about as fast as the driver I was using before and hasn't downclocked yet.

---

PROUD MEMBER OF Team Starfire World BOINC

Just to chime in here

I have noticed a down clock once last night.
temps went from 45 to 27 and I noticed the down clock to 405 from 850

I upgraded to 285.62 two days ago and it has been no problem until last night.
I was running 280.26 and had resolved down clock problem from earlier versions
I will keep running just to see if it persists.

Nothing I did solved the problem until I rebooted.


Michael Miles
Phenom 2 1100T @ 4.2
Zotac 460 GTX 768meg running at 850 core 1700 shader 1800 mem clock
MSI Afterburner beta 8
Win 7 ultimate x64

Boinc 6.12.34 x64

Just to chime in here

I have noticed a down clock once last night.
temps went from 45 to 27 and I noticed the down clock to 405 from 850

I upgraded to 285.62 two days ago and it has been no problem until last night.
I was running 280.26 and had resolved down clock problem from earlier versions
I will keep running just to see if it persists.

Nothing I did solved the problem until I rebooted.


Michael Miles
Phenom 2 1100T @ 4.2
Zotac 460 GTX 768meg running at 850 core 1700 shader 1800 mem clock
MSI Afterburner beta 8
Win 7 ultimate x64

Boinc 6.12.34 x64

Which CUDA application(s) - from this or any other project, or from outside the BOINC framework entirely - are you running on the card?

Just to chime in here

I have noticed a down clock once last night.
temps went from 45 to 27 and I noticed the down clock to 405 from 850

I upgraded to 285.62 two days ago and it has been no problem until last night.
I was running 280.26 and had resolved down clock problem from earlier versions
I will keep running just to see if it persists.

Nothing I did solved the problem until I rebooted.


Michael Miles
Phenom 2 1100T @ 4.2
Zotac 460 GTX 768meg running at 850 core 1700 shader 1800 mem clock
MSI Afterburner beta 8
Win 7 ultimate x64

Boinc 6.12.34 x64

Which CUDA application(s) - from this or any other project, or from outside the BOINC framework entirely - are you running on the card?

He's running Multibeam x38g Preview, Cuda 3.20

Haven't noticed this on the 470, running driver 280.22, 480 driver 275.33.
What I do notice, all newer NVidia cards are running a higher colck speed,
compaired to most FERMIs, 560TI runs (factory) 1800MHz.
Also seen a GPU with 1 CUDA core (320?)

---

He's running Multibeam x38g Preview, Cuda 3.20

Haven't noticed this on the 470, running driver 280.22, 480 driver 275.33.
What I do notice, all newer NVidia cards are running a higher clock speed,
compaired to most FERMIs, 560TI runs (factory) 1800MHz.
Also seen a GPU with 1 CUDA core (320?)

It is x38g but it is now cuda 4010 with the new driver.

285.62

I noticed this a lot with 275 series that it would downclock when I would start Boinc then quit then restart boinc.
It would not come back up to speed .
Stayed at 405 core. Until I rebooted, then all was good until I shut down Boinc then restarted. Then it would not come back until reboot.
I tried to apply the speed setting again in Afterburner but it would not go up
266.58 was the most stable with this card and I have been using 280.26 was stable no problems with down clocking.
I went to the 280 series and it was cuda 4.0
I tried the experimental Lunatics_x40_Win32_Cuda40 with 280.26 but time increased because of debugging code still in.
So I went back to the official release x38g and everything was good.
This has only happened once in the two days I have been using 285.62

The new MSI afterburner beta 9 should not be long before it's released so it may solve out there.

Otherwise I am very impressed with the overclocking of this Zotac 460GTX 768 meg.
It cuts out at 925 core speed so I settle for 850, 1700,1800 with full 70 fan I never get above 50C temp
Of course I do not run this computer with the side panel on the case and I have a desk fan blowing on it. I also use the Cool master Hyper 212 Plus cooler on CPU and I see temps around 40 max @ 4.2 and Voltage at 1.50 in Bios but under 100% load the actual voltage is 1.42-1.44 100%load
When I stop crunching voltage goes to 1.47 so all in all this is a great chip

I seem to be having a problem with the new 285.62 driver. I started to notice down clocks and I seem to have messed up a bunch of AP work on my GPU. I may have a few MBs messed up too. I have gone back to the 267.59 driver I was using before and will see if that works better.

I can't swear it's the driver because I started using the 2.6 rescheduler around the same time. I will let you know what happens with the driver rollback.

---

PROUD MEMBER OF Team Starfire World BOINC