Video cards do one WU and then go to sleep.

[krisco65]

I have 3 different machines and 4 video cards folding right now through FAH GPU Tracker. They all will complete one WU and then they stop. Here is what the log says:

[17:16:37] + Processing work unit
[17:16:37] Core required: FahCore_15.exe
[17:16:37] Core found.
[17:16:37] Working on queue slot 01 [March 6 17:16:37 UTC]
[17:16:37] + Working ...
[17:16:37]
[17:16:37] *
*
[17:16:37] Folding@Home GPU Core
[17:16:37] Version 2.20 (Tue Aug 2 12:06:37 PDT 2011)
[17:16:37] Build host SimbiosNvdWin7
[17:16:37] Board Type NVIDIA/CUDA
[17:16:37] Core 15
[17:16:37]
[17:16:37] Window's signal control handler registered.
[17:16:37] Preparing to commence simulation
[17:16:37] - Ensuring status. Please wait.
[17:16:46] - Looking at optimizations...
[17:16:46] - Working with standard loops on this execution.
[17:16:46] Examination of work files indicates 8 consecutive improper terminations of core.
[17:16:46] sizeof(CORE_PACKET_HDR) = 512 file=<>
[17:16:46] - Expanded 124778 -> 567850 (decompressed 455.0 percent)
[17:16:46] Called DecompressByteArray: compressed_data_size=124778 data_size=567850, decompressed_data_size=567850 diff=0
[17:16:46] - Digital signature verified
[17:16:46]
[17:16:46] Project: 8033 (Run 7, Clone 85, Gen 22)
[17:16:46]
[17:16:46] Entering M.D.
[17:16:48] Tpr hash work/wudata_01.tpr: 2232989670 3956926956 753999559 1703742003 3206261193
[17:16:48] calling fah_main gpuDeviceId=0
[17:16:48] Working on Protein
[17:16:48] Client config found, loading data.
[17:16:51] CoreStatus = 63 (99)
[17:16:51] + Error starting Folding@home core.
[17:16:51] Folding@Home will go to sleep for 1 day as there have been 5 consecutive Cores executed which failed to complete a work unit.
[17:16:51] (To wake it up early, quit the application and restart it.)
[17:16:51] If problems persist, please visit our website at http://folding.stanford.edu for help.
[17:16:51] + Sleeping...

If I stop the GPUS and then restart them it works fine until it finishes that WU and then it does this again. Not really sure what is going on. For reference the video cards are:

Two GTX 460's
GTX 560 Ti
HD 7970

Thanks.

[Jesse_V]

Do you have your screen to turn off after a while for power savings? Might be problem with the latest GPU driver then: viewtopic.php?f=67&t=20891

[krisco65]

I dont. I have it set to load up a screen saver.

[7im]

Which driver version?

And the 63 99 error is usually a hardware not recognized issue, where the client fails to start up. Could be driver issue, or overclock issue.

[17:16:51] CoreStatus = 63 (99)

[PinHead]

[17:16:48] Client config found, loading data.
[17:16:51] CoreStatus = 63 (99)
[17:16:51] + Error starting Folding@home core.
[17:16:51] Folding@Home will go to sleep for 1 day as there have been 5 consecutive Cores executed which failed to complete a work unit.
[17:16:51] (To wake it up early, quit the application and restart it.)
[17:16:51] If problems persist, please visit our website at http://folding.stanford.edu for help.
[17:16:51] + Sleeping...

You have tripped a safety mechanism in the client by returning too many bad work units without completing a good WU.

If you are running O.C., then back off the clocks until you complete a good WU. If not running O.C., then a log showing the initial client startup thru the completion/upload/beginning of next WU would be helpfull.

[PinHead]

I dont. I have it set to load up a screen saver.

Once upon a time ( and now your making me 'age' myself back to the orginal depredicated cpu client ), screen savers would force the GPU out of the graphics mode or turbo clocks needed for folding. Trying setting it to "blank screen" instead of screen saver and see if that helps. I haven't tried a screen saver in quite some time because of earlier issues with folding. Try that until someone with experience with the new client and screen savers comes along to tell you it's ok or how to use screen savers with folding.

Just making a suggestion, someone with current screen saver / folding will be along any minute now.

[Ripper36]

There are now three or four threads about the same ENUM error problem - see viewtopic.php?f=61&t=20989&p=209931#p209931

Can moderators rationalise this please and work out a solution!

[bruce]

Can moderators rationalise this please and work out a solution!

My GTX460 is running without problems on Windows 7-64 using driver 258.96 which MS chooses to call 8.17.12.5896. I have my screen-saver set to "Black screen"

• There are many reports of problems with newer drivers, though I can't certify which ones will fail at the end of a WU and which will not. If I were trying to make FAH work, I'd start with drivers from 2010 and work my way forward until I get a failure and then revert to the previous version.
• There are many reports of problems with Power saving mode of "turn off monitor," particularly on 64-bit, and I've had problems with that setting, too. The power switch on the monitor works fine when I remember to use it.
• Many screensavers and MS Remote Desktop and Fast User Switching are all known to cause immediate failures. I don't use them.

[Urinophoria]

Not quite sure how exactly I got this effect...

Basically since I started playing around with nvidia 285 and up drivers, my gpu usage has been in the 85-90% usage range for the gpu3 client. I figured instead of sweeping changes involving all of the settings and gfx drivers and such I'd start small and control the variables; basically try one thing, if it doesn't help, try another and undo the first thing I tried till I get it isolated.

I've also been having the "one WU and go to sleep" issue posted in this thread, which is how I wound up here, trying this stuff in the first place.

So, to start, I just (30 seconds before I started typing this) turned off the screensaver, and turned selected "never" for turning the displays off. I figured that was the simplest place to start.

Started GPU3 clients...

Computer sounds like it's almost at takeoff speeds!? and less than 2 minutes after starting the clients they're at 100% use and holding. PPD in FahMon and FAH GPU Tracker V2 showed a jump from appx 7k to 10k...

I have no idea yet (a little over 8.5 hours till WU's are completed) if it fixed the "one WU and go to sleep" issue; but for some reason, ONLY turning off my screen saver (electricsheep) and setting power saving to "never turn off displays" seems to have gained me about a 30% increase in output.

Literally, all I did was come in, sit down, jiggle the mouse to turn the screens on, notice that my gpus AGAIN were not folding, and googled the error message by copying and pasting "Folding@Home will go to sleep for 1 day as there have been 5 consecutive Cores executed which failed to complete a work unit." Then I read this thread and killed the screensaver and display off.

I guess I'll report back in 8 hours... Man, NVidia cards have gotten wierd...

*edit*

Still running like a bat out of hell, looks like either turning off the screensaver or setting power saving to not turn the display off did it for me. Gonne try narrowing it further and turn my screensaver back on (I really like electric sheep)