Folding Forum

I left --cpus at default (19) for a while and it caught a WU. 03:26:04:************************* Folding@home Client ************************* 03:26:04: Website: http://folding.stanford.edu/ 03:26:04: Copyright: (c) 2009-2014 Stanford University 03:26:04: Author: Joseph Coffland <joseph@cauldrondeve...

Try a CPU setting of 8 (cores) to see if any work comes down. If yes, run 2 CPU slots and until the larger projects get refilled. Thanks for the suggestion, but it didn't work for me. 03:25:46:************************* Folding@home Client ************************* 03:25:46: Website: http://folding....

It's ba-ack! I've had WUs rejected from 3 different machines today - all 3 to 171.64.65.124.

Sorry, by GPU crash I meant the GPU gets into a state where it no longer refreshes the screen properly. As soon as I try to move a window or do anything, the portion I am moving just pixellates and smears. The rest of the machine is still running fine, but it's difficult to use without a monitor! Mo...

@new08, Strangely Brett,on your query after a goodish run, I got just what I described from earlier.. This shows a 66xx unit going back instantly -and a 105xx coming in immediately. This is certainly better than a while back, when I could wait seeing 30 hours of non runners. Without knowing what the...

Log file below from my run with the new core. I had posted this in the thread for the new core but I'll repost here for convenience. I don't see any work files. If they were created, then they must have been deleted by the client. --- Opening Log file [October 27 16:48:23 UTC] # Windows GPU Systray ...

If NVidia says that a specific piece of hardware can perform certain types of calculations needed by a specific project, it's possible that Nvidia drivers are reporting the wrong information. It's also possible that your GPU is somehow "unique" and can't do what NVidia says it should be a...

OK, now I understand what you're thinking. The 171.64.65.61 Work Server has been serving up 105xx as well as 66xx WUs since before I started blocking IPs, though. I have them on a little notepad on my desk from a couple of months ago. Sorry you got your hopes up. :( I really don't think the changes ...

Hi new08, I'm confused by your post. What did the new client improve, aside from changing the species from 0 to 11? I see a crash on P6602 and a running P10513 in your log, which are the same results as before. Also, I was told in a different thread that the new client would not change the assigned ...

You might be able to run the GPU client. I and a few others are running low-performance 8400 GS or equivalent GPUs with the same number of shaders as yours. How much memory does your GPU have available to it? If it has at least 256MB you should be OK. Caveats: 1) Don't expect great performance. The ...

From what I can glean from the Internet, the NVIDIA 8800, 9600, 9800, and 250 cards also only go up to CUDA Compute Level 1.1, so this would not be the source of the issue with the 8400. According to NVIDIA, no hardware is even available with a Compute Level higher than 2.0. This would confirm that ...

Compute Capability: 1.1 Hmmm...Now that's interesting. Mine (Quadro NVS 295) says the same thing. I'm also using 258.96. If true, that would explain the species=0 (obviously). Good find new08! Sadly, according to info. on the NVIDIA website that I don't remember seeing before, CUDA 1.1 is the highe...

I block work server 171.64.65.61 using a static IP route on the individual PC, but using a firewall would be easier for most ppl. So far it has prevented me from getting any GPU WUs that crash. Sometimes it can take several hours to get a WU, but it's well worth not crashing the GPU. I'm not overclo...

Sorry to jump in on this late.... I'm running a Quadro NVS 295 which is still an active product and is marketed as CUDA-capable. It uses the same chipset as the 8400GS and has exactly the same problems with FAH. It is also identified as Species=0 by FAH. I don't think it is an age or lack of driver ...

I've never been assigned any FahCore_15 WUs, only FahCore_11 WUs, so I have no idea if FahCore_15 works better for this card. I suspect I probably won't see any FahCore_15 WUs as long as there are more powerful cards to consume them. I've been running the GPU3 client since it was made available.