What Nvidia drivers are you using

shadowscotland

shadowscotland

shadowscotland

Soldato
Joined
31 May 2006
Posts
7,564
Location
West London
Just noticed via MS update that nvidia current drivers are 185.xx
Still on 182.08 myself but noticed that the newer ones has CUDA2.2 is this helpfull?
Or if it an't broken don't go trying to fix it :D
 
shadowscotland said:
What card do you have Pilgrim? as it's 8xxx and above only for F@H
Click to expand...

Its a 8800GT 256MB, which in theory should work but I only been able to do 1 or 2 units then it craps out & goes to standard processing. An error message says something about memory. So I'm sticking with the optimised client as at least that works ok.
 
256MB is too little for Seti I think. Why not do folding on the GPU and seti on the CPU? :)
 
Vista Ultimate x64 with the 185.85 WHQL drivers here. Would like to be running Windows 7 but my network card refuses to work and a PC for folding without an internet connection is highly pointless.
 
Biffa said:
256MB is too little for Seti I think. Why not do folding on the GPU and seti on the CPU? :)
Click to expand...

According to the BOINC site it meets the minimum requirements:confused:
I'm doing what you suggest, Biffa, but loads of EUE's with FAH for the past 2 weeks. Some get to 10-12% & die - nans detected
 
running the 185.xx whqls here.

Read somewhere they'd have to recompile the clients and cores to take advantage of CUDA 2.2, or write a new core, neither of which has been done as of yet.

The cudart.dll v2.2 is available from NV's CUDA website in one of the source code packages, and in driver updates, but the clients use their own copy of cudart.dll in their working directory.

***Stanford have said under no circumstances should you copy this updated 2.2 version into the FAH gpu folder, as the cores and clients will just spew out rubbish!***

As and when they compile a updated client/ new core to ttke advantage of the update, it will come in the Client install package, until then leave well alone!
 
Last edited:
I don't copy any dlls around anymore since the latest versions of the client handle the linking of dlls
 
shadowscotland said:
Try the 182.08 drivers at stock speeds and report back - as the lower memory cards like your and my GS has more issue that most.
Click to expand...

Thanks for the suggestion. I have tried most of the drivers which make no use to FAH, except to run a bit slower. TBH I reckon I did something to the card when it was o/ced. For general use & FAH it is ok but not for SETI so I'll wait for an upgrade until I try SETI on the card again.
 
181.20 here on XP64 no issues with it despite some hefty overclocks so I'm sticking with it for now.
 
You must log in or register to reply here.
Back
Top Bottom