• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

I Can't Fold Anymore!! GPU Problem.

osrk

[H]ard|Gawd
2FA
Joined
Jan 10, 2003
Messages
2,039
I can't fold on my gtx 260. It will load the console, download the core, and the WU but then it will sit on starting GUI server! I have no clue what's wrong. I came home last night and it said "Client_Died". It;s been folding fine for almost a month what happened?
 
Have you tried downloading a newer version of the folding client?

perhaps update video card drivers
 
Ok I can *fold* but at a mind numbly slow pace my log:

[23:37:23] *------------------------------*
[23:37:23] Folding@Home GPU Core - Beta
[23:37:23] Version 1.19 (Mon Nov 3 09:34:13 PST 2008)
[23:37:23]
[23:37:23] Compiler : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86
[23:37:23] Build host: amoeba
[23:37:23] Board Type: Nvidia
[23:37:23] Core :
[23:37:23] Preparing to commence simulation
[23:37:23] - Looking at optimizations...
[23:37:23] - Created dyn
[23:37:23] - Files status OK
[23:37:23] - Expanded 66381 -> 348500 (decompressed 524.9 percent)
[23:37:23] Called DecompressByteArray: compressed_data_size=66381 data_size=348500, decompressed_data_size=348500 diff=0
[23:37:23] - Digital signature verified
[23:37:23]
[23:37:23] Project: 5777 (Run 12, Clone 33, Gen 4)
[23:37:23]
[23:37:23] Assembly optimizations on if available.
[23:37:23] Entering M.D.
[23:37:30] Working on Protein
[23:37:34] Client config found, loading data.
[23:37:36] Starting GUI Server
[00:40:03] Completed 1%
[01:17:33] Completed 2%
[01:59:09] Completed 3%
[02:36:22] Completed 4%
[03:22:35] Completed 5%
 
did you delete the dir and reinstall?

what does gpuz say your core and shaders are running at?
 
did you delete the dir and reinstall?

what does gpuz say your core and shaders are running at?

I didn't install it to begin with. I used the console version, no install just drag and drop. My shaders according to riva tuner are at 1512mhz which they've been at for a while now. I tried deleting everything and having it redownload everything but that didn't work.
 
Check to see if there is any process eating up all your cpu time, its what my issue almost always is when my GPU client isnt working as fast as it should.

Do you have any other DC clients running?
 
Check to see if there is any process eating up all your cpu time, its what my issue almost always is when my GPU client isnt working as fast as it should.

Do you have any other DC clients running?


yeah that would make sense with an ATI card.. but nvidia cards with the gpu client use 0-1% cpu usage..
 
Thats pretty sweet, I did not know that. But I do only fold on ATI.


yeah hopefully ATI fixes it soon.. id like to use my 4870 512mb card.. right now its just collecting dust on my desk because i have no reason to use it.. since all of my machines run BOINC..
 
ok for some reason I don't think fah is using 3d mode or something is lying. Using the fah viewer it goes at a much faster rate then just the console but only when i'm viewing it, once i close the viewer and it goes into the system icon tray it goes back to folding like crap.
 
hmm odd.. would make sense though.. i just dont see why..

which drivers are you running?
 
bah I blame my roommate. For some reason the FAH core set itself to use core #3 of my computer (4th core) and only that core. Currently though core 3 and core 2 are reserved for a vmware machine running a simulation and are at full load. So it was folding like crap because it wasn't getting any cpu time.

Any idea how to not let it set core affinity to 3? It did this automatically.
 
nah thats the default.. always sets it to the 2nd (dual) 3rd (triple) or 4th core (quad).. as far as i know you cant change it in the program..
 
I never lock my cores when I setup GPUs. This way it just defaults to the core that has the least load.
 
I never lock my cores when I setup GPUs. This way it just defaults to the core that has the least load.


you dont have to lock the cores with gpu f@h.. it automaticly selects the last core on your processor weather you like it or not..
 
you dont have to lock the cores with gpu f@h.. it automaticly selects the last core on your processor weather you like it or not..
That's not true. The OS will handle the CPU affinity if you don't lock it, so it will bounce around the different cores if the OS tells it to.
 
bah I blame my roommate. For some reason the FAH core set itself to use core #3 of my computer (4th core) and only that core. Currently though core 3 and core 2 are reserved for a vmware machine running a simulation and are at full load. So it was folding like crap because it wasn't getting any cpu time.

Any idea how to not let it set core affinity to 3? It did this automatically.

Is this what you are looking for?

from the GPU guides:

"If you disable the affinity lock, the client will pick any free CPU core. Leave to no if you want the client to be locked to a CPU core. If you run a NVIDIA card, you can adjust the affinity by using the NV_FAH_CPU_AFFINITY environment variable (check the NVIDIA FAQ for more details). For this to work, you need to enter no or it will ignore the affinity you configured."

more info here
 
Is this what you are looking for?

from the GPU guides:

"If you disable the affinity lock, the client will pick any free CPU core. Leave to no if you want the client to be locked to a CPU core. If you run a NVIDIA card, you can adjust the affinity by using the NV_FAH_CPU_AFFINITY environment variable (check the NVIDIA FAQ for more details). For this to work, you need to enter no or it will ignore the affinity you configured."

more info here

Thanks! I'll look into it. For a quick fix i moved the vmware machine to cores 1 and 2. The reason I had to change the affinity for the vmware machines is because i'd get horrible thermal loading on my heatsink with my core 0 running around 60 C while all the other cores were in the low 50's C high 40's.
 
Back
Top