at 100% get error 77

[markfw]

OK, This box has been untouched in all respects (dedicated folding box) for over 30 days with no problems. It is a Intel 2600k@4.4 ghz, running 2 gtx460 video cards, and an smp client running bigadv. Now I have the 3rd client in a row that has finished sucessfully, but get the below (and no 70k points !)

[14:05:00] Completed 242500 out of 250000 steps (97%)
[14:38:40] Completed 245000 out of 250000 steps (98%)
[15:12:04] Completed 247500 out of 250000 steps (99%)
[15:45:38] Completed 250000 out of 250000 steps (100%)
[15:45:52] DynamicWrapper: Finished Work Unit: sleep=10000
[15:46:02]
[15:46:02] Finished Work Unit:
[15:46:02] Could not allocate memory for arcfile
[15:46:02]
[15:46:02] Folding@home Core Shutdown: UNKNOWN_ERROR
[15:46:05] CoreStatus = 77 (119)
[15:46:05] Client-core communications error: ERROR 0x77
[15:46:05] Deleting current work unit & continuing...
[15:46:34] - Preparing to get new work unit...
[15:46:34] Cleaning up work directory
[15:46:36] + Attempting to get work packet
[15:46:36] Passkey found
[15:46:36] - Connecting to assignment server
[15:46:37] - Successful: assigned to (130.237.232.141).
[15:46:37] + News From Folding@Home: Welcome to Folding@Home
[15:46:37] Loaded queue successfully.
[15:48:05] + Closed connections

This box runs WinXP32, and has 4 gig of memory, and it has 2 gig used (1.5 gig available physical and says 2048 or 4927 memory used, and 300 gig of hard disk free.

The main point, is that for a month running 24/7 it had no problems, and now this starts showing up. AND NO CHANGES OR REBOOTS AT ALL.

What is going on here ? How do I fix this ?

Also note, I am not new to this, number 11 in the world for F@H here > http://fah-web.stanford.edu/cgi-bin/mai ... F_Williams

[bruce]

http://fahwiki.net/index.php/CoreStatus_codes#77 isn't much help, but it's all the information that has been gathered.

"Could not allocate memory for arcfile" sounds like it falls under the same heading, but you'll have to figure out what kind of limitation is being exceeded.

[markfw]

I saw that, and asked at anantech forums. No useful advice. I declocked it 200 mhz, just in case.

[bruce]

Is your Paging File set to the "system managed" size? Did you put it on a drive that doesn't have room for it to expand?

[markfw]

Is your Paging File set to the "system managed" size? Did you put it on a drive that doesn't have room for it to expand?

I thought I answered that above. I have one hard drive. it has 300 gig free. As for memory, yes, system managed, 4 gig, 3.5 available to windows, 1.5 gig free. There is no reason for this error.

Also, with 1.5 gig free physical memory, why would I have to worry about about virtual ? Any why with no changes in the config, was it fine for 30 day, and then all of a sudden, this ?

[PantherX]

Can you please give us the PRCG of this WU?

[markfw]

Can you please give us the PRCG of this WU?

I have had 3 in a row, all 3 different units:

Project: 6900 (Run 22, Clone 11, Gen 22)

Project: 2684 (Run 7, Clone 17, Gen 57)

Project: 6900 (Run 46, Clone 21, Gen 6)

I can put the entire log here if you want.

[PantherX]

Project: 6900 (Run 22, Clone 11, Gen 22) -> 2 Donors completed it successfully.
Project: 2684 (Run 7, Clone 17, Gen 57) -> No results in the WU Database yet so I have marked it for a follow-up.
Project: 6900 (Run 46, Clone 21, Gen 6) -> 9 Donors completed it successfully.

Have you tried running only the SMP bigadv WUs while you exited the GPU3 Beta Client?

BTW, are you aware of the Sandy Bridge SATA2 (3 Gb/s) Port issue? Maybe it is the problem since your system runs 24/7 with 3 F@H Clients.

[markfw]

I have not tried just smp. Those 2 card units are doing fine, and I get 25k ppd from those. I hate to kill to those to fix 28k ppd.

And again, why after 30 days would it all of a sudden go south ?

And lastly, yes, since I am the CPU moderator for Anandtech.com, I know of the sata bug, but if thats it, why are the gpu clients fine ?

Just trying to find an explanation that makes sense.

[markfw]

I just noticed that the previous units (2 or 3) before those also had the same problem. Here is the last units this this box did successfully:

Code: Select all

[03:31:43] Working on queue slot 07 [January 27 03:31:43 UTC]
[03:31:43] + Working ...
[03:31:43] 
[03:31:43] *------------------------------*
[03:31:43] Folding@Home Gromacs SMP Core
[03:31:43] Version 2.22 (Mar 12, 2010)
[03:31:43] 
[03:31:43] Preparing to commence simulation
[03:31:43] - Looking at optimizations...
[03:31:43] - Created dyn
[03:31:43] - Files status OK
[03:31:47] - Expanded 24871100 -> 30796293 (decompressed 123.8 percent)
[03:31:47] Called DecompressByteArray: compressed_data_size=24871100 data_size=30796293, decompressed_data_size=30796293 diff=0
[03:31:47] - Digital signature verified
[03:31:47] 
[03:31:47] Project: 6900 (Run 19, Clone 20, Gen 15)



And after that came:========================


16:20:49] Completed 242500 out of 250000 steps  (97%)
[17:00:20] Completed 245000 out of 250000 steps  (98%)
[17:42:56] Completed 247500 out of 250000 steps  (99%)
[18:25:00] Completed 250000 out of 250000 steps  (100%)
[18:25:18] DynamicWrapper: Finished Work Unit: sleep=10000
[18:25:28] 
[18:25:28] Finished Work Unit:
[18:25:28] - Reading up to 52713120 from "work/wudata_07.trr": Read 52713120
[18:25:32] trr file hash check passed.
[18:25:32] - Reading up to 47029496 from "work/wudata_07.xtc": Read 47029496
[18:25:33] xtc file hash check passed.
[18:25:33] edr file hash check passed.
[18:25:33] logfile size: 210402
[18:25:33] Leaving Run
[18:25:34] - Writing 100120958 bytes of core data to disk...
[18:25:37]   ... Done.
[18:25:58] - Shutting down core
[18:25:58] 
[18:25:58] Folding@home Core Shutdown: FINISHED_UNIT
[18:26:03] CoreStatus = 64 (100)
[18:26:03] Sending work to server
[18:26:03] Project: 6900 (Run 19, Clone 20, Gen 15)


[18:26:03] + Attempting to send results [January 29 18:26:03 UTC]
[18:31:23] + Results successfully sent
[18:31:23] Thank you for your contribution to Folding@Home.
[18:31:23] + Number of Units Completed: 2

[18:31:31] - Preparing to get new work unit...
[18:31:31] Cleaning up work directory
[18:31:31] + Attempting to get work packet
[18:31:31] Passkey found
[18:31:31] - Connecting to assignment server
[18:31:31] - Successful: assigned to (130.237.232.141).
[18:31:31] + News From Folding@Home: Welcome to Folding@Home
[18:31:32] Loaded queue successfully.
[18:33:18] + Closed connections
[18:33:18] 
[18:33:18] + Processing work unit
[18:33:18] Core required: FahCore_a3.exe
[18:33:18] Core found.
[18:33:18] Working on queue slot 08 [January 29 18:33:18 UTC]
[18:33:18] + Working ...
[18:33:18] 
[18:33:18] *------------------------------*
[18:33:18] Folding@Home Gromacs SMP Core
[18:33:18] Version 2.22 (Mar 12, 2010)
[18:33:18] 
[18:33:18] Preparing to commence simulation
[18:33:18] - Looking at optimizations...
[18:33:18] - Created dyn
[18:33:18] - Files status OK
[18:33:21] - Expanded 24866141 -> 30796293 (decompressed 123.8 percent)
[18:33:21] Called DecompressByteArray: compressed_data_size=24866141 data_size=30796293, decompressed_data_size=30796293 diff=0
[18:33:22] - Digital signature verified
[18:33:22] 
[18:33:22] Project: 6900 (Run 22, Clone 11, Gen 22)
[18:33:22] 
[18:33:22] Assembly optimizations on if available.
[18:33:22] Entering M.D.
[18:33:31] Completed 0 out of 250000 steps  (0%)
[19:14:06] Completed 2500 out of 250000 steps  (1%)
[19:52:31] Completed 5000 out of 250000 steps  (2%)
[20:30:44] Completed 7500 out of 250000 steps  (3%)
[21:08:19] Completed 10000 out of 250000 steps  (4%)
[21:45:38] Completed 12500 out of 250000 steps  (5%)
[22:22:46] Completed 15000 out of 250000 steps  (6%)
[23:00:21] Completed 17500 out of 250000 steps  (7%)
[23:37:27] Completed 20000 out of 250000 steps  (8%)
[00:14:34] Completed 22500 out of 250000 steps  (9%)
[00:52:41] Completed 25000 out of 250000 steps  (10%)
[01:28:00] Completed 27500 out of 250000 steps  (11%)
[02:03:06] Completed 30000 out of 250000 steps  (12%)
[02:38:00] Completed 32500 out of 250000 steps  (13%)
[03:12:37] Completed 35000 out of 250000 steps  (14%)
[03:48:07] Completed 37500 out of 250000 steps  (15%)
[04:26:08] Completed 40000 out of 250000 steps  (16%)
[05:02:57] Completed 42500 out of 250000 steps  (17%)
[05:40:57] Completed 45000 out of 250000 steps  (18%)
[06:18:16] Completed 47500 out of 250000 steps  (19%)
[06:55:55] Completed 50000 out of 250000 steps  (20%)
[07:32:39] Completed 52500 out of 250000 steps  (21%)
[08:07:33] Completed 55000 out of 250000 steps  (22%)
[08:44:04] Completed 57500 out of 250000 steps  (23%)
[09:22:14] Completed 60000 out of 250000 steps  (24%)
[09:58:21] Completed 62500 out of 250000 steps  (25%)
[10:34:55] Completed 65000 out of 250000 steps  (26%)
[11:11:06] Completed 67500 out of 250000 steps  (27%)
[11:48:42] Completed 70000 out of 250000 steps  (28%)
[12:25:39] Completed 72500 out of 250000 steps  (29%)
[13:02:01] Completed 75000 out of 250000 steps  (30%)
[13:38:39] Completed 77500 out of 250000 steps  (31%)
[14:14:57] Completed 80000 out of 250000 steps  (32%)
[14:51:13] Completed 82500 out of 250000 steps  (33%)
[15:28:07] Completed 85000 out of 250000 steps  (34%)
[16:05:15] Completed 87500 out of 250000 steps  (35%)
[16:42:41] Completed 90000 out of 250000 steps  (36%)
[17:20:22] Completed 92500 out of 250000 steps  (37%)
[17:57:46] Completed 95000 out of 250000 steps  (38%)
[18:33:32] Completed 97500 out of 250000 steps  (39%)
[19:09:30] Completed 100000 out of 250000 steps  (40%)
[19:44:55] Completed 102500 out of 250000 steps  (41%)
[20:20:23] Completed 105000 out of 250000 steps  (42%)
[20:57:04] Completed 107500 out of 250000 steps  (43%)
[21:32:52] Completed 110000 out of 250000 steps  (44%)
[22:09:21] Completed 112500 out of 250000 steps  (45%)
[22:45:25] Completed 115000 out of 250000 steps  (46%)
[23:22:31] Completed 117500 out of 250000 steps  (47%)
[00:00:13] Completed 120000 out of 250000 steps  (48%)
[00:37:20] Completed 122500 out of 250000 steps  (49%)
[01:15:32] Completed 125000 out of 250000 steps  (50%)
[01:53:21] Completed 127500 out of 250000 steps  (51%)
[02:30:14] Completed 130000 out of 250000 steps  (52%)
[03:06:21] Completed 132500 out of 250000 steps  (53%)
[03:42:20] Completed 135000 out of 250000 steps  (54%)
[04:19:00] Completed 137500 out of 250000 steps  (55%)
[04:55:40] Completed 140000 out of 250000 steps  (56%)
[05:31:39] Completed 142500 out of 250000 steps  (57%)
[06:08:02] Completed 145000 out of 250000 steps  (58%)
[06:45:01] Completed 147500 out of 250000 steps  (59%)
[07:20:56] Completed 150000 out of 250000 steps  (60%)
[07:57:41] Completed 152500 out of 250000 steps  (61%)
[08:34:43] Completed 155000 out of 250000 steps  (62%)
[09:11:29] Completed 157500 out of 250000 steps  (63%)
[09:48:22] Completed 160000 out of 250000 steps  (64%)
[10:25:29] Completed 162500 out of 250000 steps  (65%)
[11:03:04] Completed 165000 out of 250000 steps  (66%)
[11:39:52] Completed 167500 out of 250000 steps  (67%)
[12:16:46] Completed 170000 out of 250000 steps  (68%)
[12:54:12] Completed 172500 out of 250000 steps  (69%)
[13:31:10] Completed 175000 out of 250000 steps  (70%)
[14:07:16] Completed 177500 out of 250000 steps  (71%)
[14:43:14] Completed 180000 out of 250000 steps  (72%)
[15:19:37] Completed 182500 out of 250000 steps  (73%)
[15:56:10] Completed 185000 out of 250000 steps  (74%)
[16:32:52] Completed 187500 out of 250000 steps  (75%)
[17:09:18] Completed 190000 out of 250000 steps  (76%)
[17:46:24] Completed 192500 out of 250000 steps  (77%)
[18:22:44] Completed 195000 out of 250000 steps  (78%)
[18:59:15] Completed 197500 out of 250000 steps  (79%)
[19:36:37] Completed 200000 out of 250000 steps  (80%)
[20:14:23] Completed 202500 out of 250000 steps  (81%)
[20:52:20] Completed 205000 out of 250000 steps  (82%)
[21:29:04] Completed 207500 out of 250000 steps  (83%)
[22:06:33] Completed 210000 out of 250000 steps  (84%)
[22:44:26] Completed 212500 out of 250000 steps  (85%)
[23:21:18] Completed 215000 out of 250000 steps  (86%)
[23:59:09] Completed 217500 out of 250000 steps  (87%)
[00:35:52] Completed 220000 out of 250000 steps  (88%)
[01:12:33] Completed 222500 out of 250000 steps  (89%)
[01:48:54] Completed 225000 out of 250000 steps  (90%)
[02:25:32] Completed 227500 out of 250000 steps  (91%)
[03:01:23] Completed 230000 out of 250000 steps  (92%)
[03:37:21] Completed 232500 out of 250000 steps  (93%)
[04:13:28] Completed 235000 out of 250000 steps  (94%)
[04:49:05] Completed 237500 out of 250000 steps  (95%)
[05:26:26] Completed 240000 out of 250000 steps  (96%)
[06:03:14] Completed 242500 out of 250000 steps  (97%)
[06:38:27] Completed 245000 out of 250000 steps  (98%)
[07:13:40] Completed 247500 out of 250000 steps  (99%)
[07:48:54] Completed 250000 out of 250000 steps  (100%)
[07:49:08] DynamicWrapper: Finished Work Unit: sleep=10000
[07:49:18] 
[07:49:18] Finished Work Unit:
[07:49:18] Could not allocate memory for arcfile
[07:49:18] 
[07:49:18] Folding@home Core Shutdown: UNKNOWN_ERROR
[07:49:21] CoreStatus = 77 (119)
[07:49:21] Client-core communications error: ERROR 0x77
[07:49:21] Deleting current work unit & continuing...
[07:49:45] - Preparing to get new work unit...
[07:49:45] Cleaning up work directory
[07:49:45] + Attempting to get work packet
[07:49:45] Passkey found
[07:49:45] - Connecting to assignment server
[07:49:45] - Successful: assigned to (130.237.232.141).
[07:49:45] + News From Folding@Home: Welcome to Folding@Home
[07:49:45] Loaded queue successfully.
[07:51:13] + Closed connections
[07:51:18]

Mod Edit: Added Code Tags - PantherX

[Nathan_P]

Project: 6900 (Run 22, Clone 11, Gen 22) -> 2 Donors completed it successfully.
Project: 2684 (Run 7, Clone 17, Gen 57) -> No results in the WU Database yet so I have marked it for a follow-up.
Project: 6900 (Run 46, Clone 21, Gen 6) -> 9 Donors completed it successfully.

Have you tried running only the SMP bigadv WUs while you exited the GPU3 Beta Client?

BTW, are you aware of the Sandy Bridge SATA2 (3 Gb/s) Port issue? Maybe it is the problem since your system runs 24/7 with 3 F@H Clients.

I know this is a different topic but I thought that each WU was only issued once, This is not the first time recently that i have seen multiple returns for a WU. Are there a large qty of bad WU out there or are PG intentionally sending each WU more than once??

[PantherX]

...I know this is a different topic but I thought that each WU was only issued once, This is not the first time recently that i have seen multiple returns for a WU. Are there a large qty of bad WU out there or are PG intentionally sending each WU more than once??

My guess is that since running bigadv requires OC (will vary according to system), many Donors OC and if it isn't stable enough, the WU fails and will be sent out again by the Servers (This can apply for any CPU/GPU that is OC and folding). The WU mentioned previously (Project: 6900 (Run 19, Clone 20, Gen 15)) has been completed only once by, I think, markfw (Can't confirm yet since I don't have the Donor Name). BTW, a Bad WU can't be successfully completed by the Donors.

[Grandpa_01]

I wonder if it could have anything to do with the Sandy Bridge chipset problem.

The Failure Manifested
I asked Intel how we’d know if we had a failure on our hands. The symptoms are pretty simple to check for. Intel says you’d see an increase in bit error rates on a SATA link over time. Transfers will retry if there is an error but eventually, if the error rate is high enough, you’ll see reduced performance as the controller spends more time retrying than it does sending actual data.

Ultimately you could see a full disconnect - your SATA drive(s) would not longer be visible at POST or you’d see a drive letter disappear in Windows.

It’s Limited to 3Gbps Ports Only
Interestingly enough the problem doesn’t affect ports 0 & 1 on the 6-series chipset. Remember that Intel has two 6Gbps ports and four 3Gbps ports on P67/H67, only the latter four are impacted by this problem. If you’re a current Sandy Bridge user and want to be sure you don’t have any problems until you can get replacement hardware, stick to using the 6Gbps ports on your board (which should be the first two ports).

[markfw]

...I know this is a different topic but I thought that each WU was only issued once, This is not the first time recently that i have seen multiple returns for a WU. Are there a large qty of bad WU out there or are PG intentionally sending each WU more than once??

My guess is that since running bigadv requires OC (will vary according to system), many Donors OC and if it isn't stable enough, the WU fails and will be sent out again by the Servers (This can apply for any CPU/GPU that is OC and folding). The WU mentioned previously (Project: 6900 (Run 19, Clone 20, Gen 15)) has been completed only once by, I think, markfw (Can't confirm yet since I don't have the Donor Name). BTW, a Bad WU can't be successfully completed by the Donors.

I have been folding for years...As attributed to my stats(number 11 in the world for F@H). I have never had a WU go all the way to 100%, and then fail due to an OC.

But I guess there is always a first. I always test my boxes for stability first before folding, but.....

And again, this box worked for 3 weeks stable before this started !!! And did units.

[HendricksSA]

You seniors please don't beat me up over this ... but didn't someone here say you couldn't run bigadv on 32 bit systems. There simply wasn't enough memory. What's the word?

Mark, you have completed many work units to get to an 11 ranking. Were they on 32 bit systems? I have problems keeping XP systems running reliably for long periods of time. I don't think any of them would run for a month. I don't have the same problems with Vista/7/Linux. Based on your title, all 3 failed units went to 100% and then got the error 77. True?