Page 1 of 1

Project: 5769 (Run 7, Clone 112, Gen 2408)

Posted: Thu Aug 26, 2010 8:50 pm
by Stewart1
Here's an odd one. I don't normally report GPU WU failures here because I figure they may well be due to overclocking. But this one did not fail in any of the normal ways - it just hung. I noticed after about four hours, stopped and started the client, same effect.

So I tried to delete the contents of the Work directory and found that I couldn't because FahCore_11.exe*32 was still running. Killed the process using Task Manager and was able to start again.

Code: Select all

[16:37:31] *------------------------------*
[16:37:31] Folding@Home GPU Core
[16:37:31] Version 1.31 (Tue Sep 15 10:57:42 PDT 2009)
[16:37:31] 
[16:37:31] Compiler  : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86 
[16:37:31] Build host: amoeba
[16:37:31] Board Type: Nvidia
[16:37:31] Core      : 
[16:37:31] Preparing to commence simulation
[16:37:31] - Looking at optimizations...
[16:37:31] DeleteFrameFiles: successfully deleted file=work/wudata_08.ckp
[16:37:31] - Created dyn
[16:37:31] - Files status OK
[16:37:31] - Expanded 45401 -> 251112 (decompressed 553.0 percent)
[16:37:31] Called DecompressByteArray: compressed_data_size=45401 data_size=251112, decompressed_data_size=251112 diff=0
[16:37:31] - Digital signature verified
[16:37:31] 
[16:37:31] Project: 5769 (Run 7, Clone 112, Gen 2408)
[16:37:31] 
[16:37:31] Assembly optimizations on if available.
[16:37:31] Entering M.D.
[16:37:37] Tpr hash work/wudata_08.tpr:  622095353 2205105612 3132021938 2980234100 704245054
[16:37:37] 
[16:37:37] Calling fah_main args: 14 usage=100
[16:37:37] 
[16:37:38] Working on Protein
[16:37:38] Client config found, loading data.
[16:37:38] Starting GUI Server

Re: Project: 5769 (Run 7, Clone 112, Gen 2408)

Posted: Thu Aug 26, 2010 9:16 pm
by sortofageek
Another folder has successfully completed that WU and received full credit.

Re: Project: 5769 (Run 7, Clone 112, Gen 2408)

Posted: Thu Aug 26, 2010 9:44 pm
by Stewart1
Oh well, maybe something odd happening locally then. Hasn't happened to me before in a couple of thousand GPU WUs.