Author Topic: Latest drivers (NVidia and ATI) (Read 480857 times)

popandbob · « **Reply #45 on:** 04 Aug 2009, 10:12:41 pm »

The ambient temp is not room temp its some other card temperature.

Try speeding up the fans with whichever OC'ing program you prefer.

figment · « **Reply #46 on:** 11 Aug 2009, 01:07:45 am »

I'm getting a ton of comp errors on my cuda's so I decided to uninstall everything (boinc & unified installer). After uninstall, I noticed I still had the \programData\BOINC\ folder, so I deleted that too. I'm ready to try this again, and want to make sure I'm doing this right.

Running Vista Ultimate x64, e6700, 2x MSI GTX260's. 4gb RAM

Currently:
- Nvidia driver 190.38 installed
- SLI disabled
- Downloaded & installed 2.3 Cuda Driver from nvidia.com for Vista x64
- Downloaded & installed BOINC 6.6.36 (all default options)

I'm running boinc currently on the default settings. At this point to get up and running on the unified installer, I believe I have to perform the following correct?

1. Download Lunatics_Win64v0.2_(SSE3+)_AP505r168_AKv8bx64_CudaV12.exe
2. Install it (I only want to run cuda units)
- Selecting only: Enable processing Multibeam tasks on nvidia cuda gpu (6.08) option
- Default destination folder
3. Download the 2.3 Cuda DLL's from this site (cudart.dll & cufft.dll) and place them in the C:\ProgramData\BOINC\projects\setiathome.berkeley.edu folder
4. Restart BOINC and done?

Raistmer · « **Reply #47 on:** 11 Aug 2009, 04:30:44 am »

Quote from: figment on 11 Aug 2009, 01:07:45 am

I'm running boinc currently on the default settings. At this point to get up and running on the unified installer, I believe I have to perform the following correct?

1. Download Lunatics_Win64v0.2_(SSE3+)_AP505r168_AKv8bx64_CudaV12.exe
2. Install it (I only want to run cuda units)
- Selecting only: Enable processing Multibeam tasks on nvidia cuda gpu (6.08) option
- Default destination folder
3. Download the 2.3 Cuda DLL's from this site (cudart.dll & cufft.dll) and place them in the C:\ProgramData\BOINC\projects\setiathome.berkeley.edu folder
4. Restart BOINC and done?

0. Make sure stock CUDA app running OK on your host, it's required step.
1. your 1.
2. your 2.
2a. check that boinc stopped.
3.your 3 (all downloads can be done before actually

, but DLLs should be replaced when BOINC is stopped)
4. start BOINC, not restart it (cause it should be stopped on prev stage).

k6xt · « **Reply #48 on:** 11 Aug 2009, 10:40:53 pm »

I have to say "Thanks" again. The latest KWSN mods and Nvidia drivers have had quite the effect on my RAC which was on the order 13,500 a week ago. Now its 19,000 with (so far) constant slope. No sign of leveling yet. Where it stops, nobody knows!
Thanks
Art

timiman · « **Reply #49 on:** 15 Oct 2009, 02:34:47 pm »

Thanks for me too.
Last week I realized that I was using CUDA 2.2 on my 8800GTS SLI setup.
Now RAC went 60%+ and time for every DU dropped to 4 mins for the quick dus and 22 mins for the big ones.

Claggy · « **Reply #50 on:** 31 Oct 2009, 06:02:13 am »

Nvidia driver 195.39 Beta has been released with Cuda 3.0 support, and Open Computing Language (OpenCL) 1.0 support.
just waiting for the Cuda 3.0 dll's to try.

Claggy

Jason G · « **Reply #51 on:** 31 Oct 2009, 09:14:43 am »

Quote from: Claggy on 31 Oct 2009, 06:02:13 am

... Cuda 3.0 dll's to try.

Could possibly be waiting 'till after GT300 release for those. Nothing in nVidia registered developer area for those so far.

msattler · « **Reply #52 on:** 31 Oct 2009, 04:28:07 pm »

Just tried the 195.39 drivers on the Frozen Nehi...........

Not good. Drivers loaded fine and everything was OK on reboot.

But when I restarted Boinc and it started to crunch Seti, the Cuda tasks were taking up lots of CPU time and running slowly.
Usually, the Cuda tasks take a full core for 30 seconds or less, and then fall back to 1-3% CPU usage while they run. With the new driver, I ran for just a few minutes, but there was never a fallback......high CPU usage continued, and I could tell from the Killawatt that the GTX295 was not drawing nearly the power it usually does when processing Cuda work.

Reinstalled 190.62 drivers and all is back to normal again.
This in on XP x64.

Anybody else wanna try and see if your results mirror mine?

Claggy · « **Reply #53 on:** 31 Oct 2009, 04:56:54 pm »

It's O.K on my 9800GTX+ with Vista 64bit,
Laptop's 128Mb 8400M GS O.K on Collatz with Vista 32bit.

Claggy

msattler · « **Reply #54 on:** 31 Oct 2009, 05:02:44 pm »

Hmmmmmmmm.....
Might try it again tomorrow and let it run a bit longer to see if anything changes.
Otherwise I'll wait until Jason gets the actual 3.0 dll's and see if it responds any differently with them than with the 2.3's.

Claggy · « **Reply #55 on:** 31 Oct 2009, 05:11:28 pm »

There's a host in the top 30 or so running it with 3 GPU's,
have a look at his run times,
i'm posting from a PSP, and it's somewhat difficult for me.

Claggy

Devaster · « **Reply #56 on:** 06 Nov 2009, 02:06:03 am »

released CUDA 3.0beta time to recompile

cristipurdel · « **Reply #57 on:** 06 Nov 2009, 02:16:12 am »

If CUDA 3.0 is not backwards compatible with 2.03. wouldn't be more easy to go for OpenCL?

MarkJ · « **Reply #58 on:** 06 Nov 2009, 02:51:24 am »

I tried the beta last week. It crapped out on GPUgrid work. Was using 195.39 with cuda 2.3 DLL's. Went back and installed 190.62 after that little episode.

Your can read about it here

Unfortunately being version 1.0 OpenCL isn't useful for most people. It doesn't have any FFT libraries, which means its useless to Seti and GPUgrid in its current version.

Devaster · « **Reply #59 on:** 06 Nov 2009, 03:42:29 am »

under win7 64-bit last drivers are running without problems - games, seti, collatz, gpugrid ....