Folding Forum

On client "local" 127.0.0.1:*****: Option 'gpu-index' has no default and is not set.

The Folding@home software on your computer has most likely stopped.

Please first restart it, then reload this page.

Client gets hung at "Updating Inactive"

This has been 3 weeks and it still keeps hanging...

System Specs

i7-5960x
4x Titan X
W10

I really want to help fold considering I have a multi million PPD system but I don't know what I'm doing wrong.

Can you share more info like log file with the upper part of system info and config ?

Make sure to have driver from nV installed.

Could it be that you installed the cards after the software ? In that case just try and reinstall. That will leave the card detection and sorting with the FAH software stack. It does a good job when get fresh installed.

I can't do a log file if the system is stuck

You can find the log file also in file system

C:/Users/<your username in W10>/AppData/FAHClient/
Then log.txt or in folder logs

See this thread. Does it fit your symptoms?
This seems to be a spreading problem, still with no definitive cause or solution.

There's a open ticket saying that FAFClient has problems if a log file contains "non-English" characters. (That's a pretty poor term, since it does handle many non-English characters. I probably would have said "unprintable")

Anyway, my current (unproven!) theory is that one or more FAHCores is putting inprintable characters in it's log but can only be proven if somebody can find them. I don't know if they have to be in (fah datafile)/log.txt or in (fah-datafile)/work/NN/logfile_01.txt and I don't know if the problem is the same for Linux and WIndows.

I'll donate the points from one WU to the first person that documents the problem in a reproducible way.
(...whether my theory connecting it with unprintable characters is correct or not.)

ChristianVirtual wrote:You can find the log file also in file system

C:/Users/<your username in W10>/AppData/FAHClient/
Then log.txt or in folder logs

I got everything working by reinstalling the client... BUT, it went through 9 hours without counting points. Considering I have a 3 million PPD machine, that really sucks. It's counting now. Don't know what changed but it's a mute point. I'm doing this for Cancer as that is what my father Passed of last year so Points are not that important. Would have been nice to have though.

When you reinstalled, did you enter your key? Bonus points are not awarded without the key.

Ricky wrote:When you reinstalled, did you enter your key? Bonus points are not awarded without the key.

Yes, entered key immediately after it started. Still not sure what happened.

Did the spelling of the key or the user name change in any way?

FYI

If you used copy/paste I have seen the double-click copy add a space to the end of my passkey and unless I catch and remove it I would have to qualify that key again.

bollix47 wrote:FYI

If you used copy/paste I have seen the double-click copy add a space to the end of my passkey and unless I catch and remove it I would have to qualify that key again.

If that were the case I would have never gained points. I did gain a few million points yesterday. It got stuck at 14.9 though and has stayed there for 12 hours. I have 18 active units including this one. So, again. No points counted. If my points are not getting counted I'm assuming the machines are not sending the finished work. If that's the case I think I've had it wit FAH. I have nothing but problems anymore.

It would appear the stats system stopped working properly last night and that will be fixed today when the staff arrives on the west coast:

viewtopic.php?f=18&t=28836

Yes, the Stats system was down and then was fixed. It's possible that your missing points were queued and have now been entered, but it's also possible that they still need to be added. I 'd like to help you but cannot. Since you've refused to post your log.txt file, I can't look up those WUs that you completed which may or may not have been credited.

The current log file is in the FAH data directory as log.txt but if you've restarted FAH, it probably does not contain information from the applicable period of time. Copies of previous logs are found in the "logs" subdirectory with names containing the date and time, such as log-20160212-213103.txt.

I had this problem stop FAH 7.4.15 beta after doing Windows updates and updating another program on a couple of my PCs. I tried in vain to uninstall FAH and data several times but it did not correct the problem. I finally got it to work after uninstalling FAH I deleted the C:\Users\Aurum\AppData\Roaming\FAHClient folder and then reinstalling 7.4.15.