• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

WTF $#@!!$%#@!$ loosing credits

Markfw

Moderator Emeritus, Elite Member
This is the second unit in a row for this.

[04:38:12] Completed 232500 out of 250000 steps (93%)
[05:20:45] Completed 235000 out of 250000 steps (94%)
[06:02:42] Completed 237500 out of 250000 steps (95%)
[06:45:10] Completed 240000 out of 250000 steps (96%)
[07:27:34] Completed 242500 out of 250000 steps (97%)
[08:09:51] Completed 245000 out of 250000 steps (98%)
[08:52:01] Completed 247500 out of 250000 steps (99%)
[09:33:54] Completed 250000 out of 250000 steps (100%)
[09:34:08] DynamicWrapper: Finished Work Unit: sleep=10000
[09:34:18]
[09:34:18] Finished Work Unit:
[09:34:18] Could not allocate memory for arcfile
[09:34:18]
[09:34:18] Folding@home Core Shutdown: UNKNOWN_ERROR
[09:34:21] CoreStatus = 77 (119)
[09:34:21] Client-core communications error: ERROR 0x77
[09:34:21] Deleting current work unit & continuing...
[09:34:43] - Preparing to get new work unit...
[09:34:43] Cleaning up work directory
[09:34:47] + Attempting to get work packet
[09:34:47] Passkey found
[09:34:47] - Connecting to assignment server
[09:34:48] - Successful: assigned to (130.237.232.141).
[09:34:48] + News From Folding@Home: Welcome to Folding@Home
[09:34:48] Loaded queue successfully.

The box is very stable, and has been tested with OCCT, and has been running 24/7 and working fine and returning units since Jan 14th. (until now)

Ideas ??
 
Maybe trying deleting all the files in your FAH directory except for the fah.exe and your config file.
 
Markfw900, just an inquiry or 3... -
- which box is this running on?
- recent updates (including M/S)?
- recent DC switching?

Just shooting blanks in the dark...

Next thing to do is head to your fav local tavern and regale the regulars with one of your woppers - this should ease you back from blowing a gasket!
 
Hmm...

I'll look at the log for my 2600k box when I get off work in a few hrs which is running under win 7 and also 24/7 w/Zotac 470 gpu card. System is running Giga's O/C @ 4.1 with a Crucial SSD 128Gb drive. It has been working like a metronome - every 2nd day I get a 70k-80k point pulse in the tally.

I have been procrastinating in raising the o/c to at least 4.4-4.5 using some recent o/c articles here on Anand and other sites...just too passive these days...
 
Possibly not enough memory based on the " Could not allocate memory for arcfile " ?

I Googled that message and found this:

http://foldingforum.org/viewtopic.php?f=55&t=17213

I don't have the below in my logfile.
Disk full?!
Ran out of Virtual memory. (Increase the size of the paging file.)

Also, I have 4 gig of memory, and only 2 gig of it is being used. Not even using any virtual memory.

I don't suppose this is somehow related to the SATA error ????I think I am on those ports.
 
Last edited:
Your logfile:
CoreStatus = 77 (119)
Client-core communications error: ERROR 0x77
Deleting current work unit & continuing...



If you will look at the context of the link I posted it states:

Explanation for CoreSatus = 77

http://fahwiki.net/index.php/CoreStatus_codes

Disk full?!
Ran out of Virtual memory. (Increase the size of the paging file.)



It is a misconception that the page file is only used when all RAM is being used .
 
Last edited:
No but you do have the corestatus = 77 (119) in the log and that is what it is refered to. Well, as per the cheat sheet on wiki.🙂
 
I have the 77, but I do NOT have the message about disk full or virtual memory....

I think something else can cause 77 errors.
 
Second unit in a row: was the first unit the same number as the second?

If, as I suspect, it is, then it is the WU.
 
Good point ! But I checked. They are all different. And the two GPU units are working just fine ! And the smp cleint was fine for a month. This is a dedicated folding box, so nothing changes except the WU's. It doesn't even reboot. But I might try that if the 3rd one dies tomorrow morning.
 
Well, in light of no useful advice on how to fix this, I have turned down my OC to 4.2, after loosing the 3rd unit in a row.
 
I read some people say to try fixing page file size (don't put it on automatic) or even try disabling page files altogether: http://www.evga.com/forums/tm.aspx?h...mpage=1#840768

Is this a 32 bit machine?

Yes, but it worked for a month with no problem, and has at least 1.25 gig physical free ! 2 gig used,and xp 32 sees at least 3.25.

Note also, I have 5 I7 rigs, all XP32, all 4 gig of ram, and none have ever had this problem, even this box for its first month was OK.

I am reading that link though..Disable virtual is only for Win7 64 and like 8-12 gig of ram.
 
Last edited:
Let's hope the reboot helps!!

Nope....But I posted on the folding forums. Lets see if they have any advice thats useful.

Edit: I am really getting annoyed. I keep answering the same question on the folding forum again, and again. Nobody has a clue. This is really bad. 200k so far lost.
 
Last edited:
[09:34:18] Could not allocate memory for arcfile

first thing I would do is run memtest.

If no errors, then maybe XP has recently changed the size of your pagefile. Others have suggested using a fixed pagefile size. The recommended size is 1.5X your RAM. Since you have 4 GB, use 6141 MB.

http://www.microsoft.com/resources/...vancd_perform_change_vmpagefile.mspx?mfr=true

set "custom"

initial size (MB) = 6141
max size (MB) =6141

Next thing to check is the windows event log to see if there are any clues there.

http://support.microsoft.com/kb/308427

Maybe the first WU failure created a temp file that is causing the problem. Get CCleaner and clean out all temp and cached files. You can also use CCleaner to fix registry errors.

Run diskcheck. Corrupted pagefile or ?
 
Did you have a Windows update just before this started happening? Sometimes, permissions get changed.

Check your folding folders's permissions.
 
Back
Top