GPU client "Sleeping..." after each completed WU

[jsanthara]

I recently acquired a GTX 560 Ti, and decided to start folding with it. It seemed to work fine for a day or two, but one day when I returned from work I noticed the computer had lost its internet connection, and as a result the folding client was unable to send the results once it completed the WU. As soon as I got the connection back up I reloaded the folding client and it sent the results and prepared to start a new 803x WU, so I minimized it and went about my business. After about 8 hours, after checking on it, I noticed that it never actually got started on another WU and was "+ Sleeping...". The log indicated that the client tried a bunch of times and then started sleeping. I thought this was strange, something I have never seen before, so I exited and restarted the client and this time it successfully started a WU. I have seen a few odd things in the past, so I thought this was the end of it, but now whenever it completes a WU it can't seem to start another without me exiting and restarting the client.

I have done a little research, and my problem seems to happen to a lot of people when they use the wrong client. I tried other clients, and I get the same results.

I am currently using the GPU3 6.41 console client. I tried using the Systray client, but the same thing happens. I can't get v7 to work on any GPU/CPU or computer, must be something I am doing wrong.

Does anyone know how I can stop this issue with my lazy GPU that wants to sleep all day? Below is an excerpt from the log.

Code: Select all

[08:14:29] + Processing work unit
[08:14:29] Core required: FahCore_15.exe
[08:14:29] Core found.
[08:14:29] Working on queue slot 06 [April 13 08:14:29 UTC]
[08:14:29] + Working ...
[08:14:29] 
[08:14:29] *------------------------------*
[08:14:29] Folding@Home GPU Core
[08:14:29] Version                2.22 (Thu Dec 8 17:08:05 PST 2011)
[08:14:29] Build host             SimbiosNvdWin7
[08:14:29] Board Type             NVIDIA/CUDA
[08:14:29] Core                   15
[08:14:29] 
[08:14:29] Window's signal control handler registered.
[08:14:29] Preparing to commence simulation
[08:14:29] - Ensuring status. Please wait.
[08:14:38] - Looking at optimizations...
[08:14:38] - Working with standard loops on this execution.
[08:14:38] Examination of work files indicates 8 consecutive improper terminations of core.
[08:14:38] sizeof(CORE_PACKET_HDR) = 512 file=<>
[08:14:38] - Expanded 119871 -> 544418 (decompressed 454.1 percent)
[08:14:38] Called DecompressByteArray: compressed_data_size=119871 data_size=544418, decompressed_data_size=544418 diff=0
[08:14:38] - Digital signature verified
[08:14:38] 
[08:14:38] Project: 8031 (Run 11, Clone 343, Gen 70)
[08:14:38] 
[08:14:38] Entering M.D.
[08:14:40] Tpr hash work/wudata_06.tpr:  48301727 893127563 3165715009 2189615540 1049596661
[08:14:40] GPU device info: vendor=0 device=0 name=<NA> match=0
[08:14:41] Working on Protein
[08:14:41] Client config found, loading data.
[08:14:43] CoreStatus = 63 (99)
[08:14:43] + Error starting Folding@home core.
[08:14:43] 
Folding@Home will go to sleep for 1 day as there have been 5 consecutive Cores executed which failed to complete a work unit.
[08:14:43] (To wake it up early, quit the application and restart it.)
[08:14:43] If problems persist, please visit our website at http://folding.stanford.edu for help.
[08:14:43] + Sleeping... 

[bruce]

Welcome to foldingforum.org, jsanthara.

I suspect the client is unable to get work because the HD 560ti was not available when V6's list of supported devices was created. You didn't post the beginning of the log so I'm not sure what parameters/flags you have set, but it will be more productive if we work on why you were not able to install V7.1.52 than if we try to fix V6.xx. Open a topic in the V7 installation forum reporting whatever errors you're getting and we'll go from there.

[jsanthara]

Having the same problem with v7 client. I set it to fold, go to work, and when I come home it isn't working on a unit. I have to restart, then after "connecting" (orange) and "updating" (yellow), it acquires a new unit and begins again.

Any help?

[Jesse_V]

Sorry, I replied to your similar thread here: viewtopic.php?f=78&t=21312