• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

600 pointers crapping out

M

Mayhem33

[H]ard|Gawd
Joined
Oct 12, 2004
Messages
1,204
Just want to know how many of you have had those 600 pointers quit on you.
Post the WU/project/run/clone/generation.
Curios if the same ones keep doing this.

Protein: p1141_RIBO_FSpeptide_HEL_nospring
Project: 1141 (Run 106, Clone 38, Gen 0)

Quit on me at the start of the 18th step.

I haven't had any trouble from this rig before, so i think it was just the WU that quit.


 
I've got this bugger at frame 28 so far -ok-, different run/clone/gen

On a side note I've been chewing on alot of these 600 pointers if anyone feels like poking around in a bunch on log files.

[01:07:03] Project: 1141 (Run 9, Clone 23, Gen 1)
[01:07:03]
[01:07:03] Assembly optimizations on if available.
[01:07:03] Entering M.D.
[01:07:13] Protein: p1141_RIBO_FSpeptide_HEL_nospring
 
i'm on my second 600 pointer...step 39 on this second one...project 1141

interesting that only my p4 gets them....my Athlon64 is getting 48 and 204 pointers.

dave
 
my 1.3 celeron is getting 600 pointers and my AMD 2800 is getting tinkers
u_DR_K13
 
My Athlon 64 3000 is picking up a few 600 pointers. The only bad part is is that it could crunch a bunch of little cores in the time it takes to crunch a 600 pointer. My P4 machine doesn't pick up 600 pointers, but that is because I don't have big packets turned on even though it has 512mb RAM.
 
Mayhem33 said:
Just want to know how many of you have had those 600 pointers quit on you.
Post the WU/project/run/clone/generation.
Curios if the same ones keep doing this.

Protein: p1141_RIBO_FSpeptide_HEL_nospring
Project: 1141 (Run 106, Clone 38, Gen 0)

Quit on me at the start of the 18th step.

I haven't had any trouble from this rig before, so i think it was just the WU that quit.


Click to expand...

I am looking for WU that end early, quit before completion. Shown like this. ;)

Protein: p1141_RIBO_FSpeptide_HEL_nospring
Project: 1141 (Run 106, Clone 38, Gen 0)

Thanks for your help! :D


 
Mayhem33 said:
I am looking for WU that end early, quit before completion. Shown like this. ;)

Protein: p1141_RIBO_FSpeptide_HEL_nospring
Project: 1141 (Run 106, Clone 38, Gen 0)

Thanks for your help! :D


Click to expand...

I have done 4 of the units in question and all have completed fine so far (Knock on wood) and i have one in the oven ;)

Protein: p1141_RIBO_FSpeptide_HEL_nospring
Projects as follows:
(1141) 114/1/1 [156]
(1141) 107/4/2 [156]
(1141) 62/8/0 [156]
(1141) 0/7/0 [156]

In all i have done 14 600 pointers to date. they pound out nicely. to bad not all my rigs have enough ram for them :(

If you need any other info let me know and i hope i helped you some.

Buck
 
Buckshot said:
I have done 4 of the units in question and all have completed fine so far (Knock on wood) and i have one in the oven ;)

Protein: p1141_RIBO_FSpeptide_HEL_nospring
Projects as follows:
(1141) 114/1/1 [156]
(1141) 107/4/2 [156]
(1141) 62/8/0 [156]
(1141) 0/7/0 [156]

In all i have done 14 600 pointers to date. they pound out nicely. to bad not all my rigs have enough ram for them :(

If you need any other info let me know and i hope i helped you some.

Buck
Click to expand...

Hey thats great Buck!
If you look closely you can see that the (run/clone/gen) are different. The info that you gave is exactly what I am looking for.
If you or anyone else has one that quits post it here so others can see if they have the same protien quitting on them. :rolleyes:

Thanks all!


 
dave_graham said:
i'm on my second 600 pointer...step 39 on this second one...project 1141

interesting that only my p4 gets them....my Athlon64 is getting 48 and 204 pointers.

dave
Click to expand...

took me a while for my amd boxes to get 600 pointers.. Now its all they get.. i wonder how FAH determines what they assign to which cpus..
 
Mauli said:
took me a while for my amd boxes to get 600 pointers.. Now its all they get.. i wonder how FAH determines what they assign to which cpus..
Click to expand...

I think its based off a couple of things.
1) the benchmark/ performance fraction.
2) how much ram is available to use.
I had 1 of my 3 boxes with only 256 megs of ram in it while the other 2 had 512 megs.
As soon I installed another 256 megs in box 1 the very next WU was a 600 pointer!
While the other 2 had been getting those large WU already. One of those CPU's is an Athlon from the older generations. (not an XP)
Hope that helps!


 
One of my rigs that got a 600 pointer has 256MB in it. It is a dedicated folder, though. It got a second one directly after the first one finished, so it must have something right!
 
NoXPert said:
One of my rigs that got a 600 pointer has 256MB in it. It is a dedicated folder, though. It got a second one directly after the first one finished, so it must have something right!
Click to expand...

Are you running Windows? Well maybe I am wrong, maybe it was just my rig that was not getting those large WU's. I haven't been able to get any specs on what is required to meet
the minimum specs. Do you know what they are? Anyway thanks for the info!!! :D


 
No, I don't know what the specs are to get them; I'm interested to know myself. The rig in question is running WinXP Pro on an ECS MB with an Athlon XP 1700+ OC'd to 1650 MHz with 256 MB of Crucial PC2100. It picked up the second one as did one of the Sempron boxes which are running 512 MB, so I can't establish a direct correlation there. I think it was mostly timing. I watched the threads about these 600s and then BAM, I got one, then two. I know that neither of the boxes had big packets turned on. Best of luck to you!
 
I just had a second 600 pointer crap out on me, about step 130 ish out of 250. Now I have the next work unit claiming it has 132 of 125 (estimate) and 2 of 125 completed. This has happened once on each of the systems in my signature. i believe both were 1141's, but as the thing just disappeared, i'm not positive - one sec lemme pull up log file -

[03:50:36] Project: 1135 (Run 37, Clone 18, Gen 1)
[03:51:08] (Starting from checkpoint)
[03:51:09] Protein: p1135_RIBO_FSpeptide_HEL
[21:33:40] Folding@home Core Shutdown: EARLY_UNIT_END
[21:33:43] CoreStatus = 72 (114)
[21:33:43] Sending work to server

my laptop completed one of those bad boys, right after failing the first one. sucks, in a sense, because that's wasted points. lol if these failures aren't cpu faults necessarily, then partial credit would be nice, as they get sent back to server to be evaluated anyway.
 
r00k said:
I just had a second 600 pointer crap out on me, about step 130 ish out of 250. Now I have the next work unit claiming it has 132 of 125 (estimate) and 2 of 125 completed. This has happened once on each of the systems in my signature. i believe both were 1141's, but as the thing just disappeared, i'm not positive - one sec lemme pull up log file -

[03:50:36] Project: 1135 (Run 37, Clone 18, Gen 1)
[03:51:08] (Starting from checkpoint)
[03:51:09] Protein: p1135_RIBO_FSpeptide_HEL
[21:33:40] Folding@home Core Shutdown: EARLY_UNIT_END
[21:33:43] CoreStatus = 72 (114)
[21:33:43] Sending work to server

my laptop completed one of those bad boys, right after failing the first one. sucks, in a sense, because that's wasted points. lol if these failures aren't cpu faults necessarily, then partial credit would be nice, as they get sent back to server to be evaluated anyway.
Click to expand...

If it quit on you I believe you will get some credit for it, the futher along you were the more it is worth.
I have a few of the one that quit on me running along just fine, but they are a different (run/clone/gen) than the one I lost.


 
NoXPert said:
No, I don't know what the specs are to get them; I'm interested to know myself.
I know that neither of the boxes had big packets turned on. Best of luck to you!
Click to expand...

I have 2 boxen set to big packets=YES and niether machince has gotten anything other than 600 pointers since I set them that way in the console.

machine specs:
Box 1
amd xp2400@2100mhz
512ram
Winxp

Box 2
amd M2500@2525mhz
1gig ram
Winxp

those 2 boxes are responsible for doubling my weekly production now that they are pounding out 600 pointers

So to answer how to get them. Set bigpackets=YES and fold, fold, fold!!
best of luck!

Buck
 
r00k said:
I just had a second 600 pointer crap out on me, about step 130 ish out of 250. Now I have the next work unit claiming it has 132 of 125 (estimate) and 2 of 125 completed. This has happened once on each of the systems in my signature. i believe both were 1141's, but as the thing just disappeared, i'm not positive - one sec lemme pull up log file -

[03:50:36] Project: 1135 (Run 37, Clone 18, Gen 1)
[03:51:08] (Starting from checkpoint)
[03:51:09] Protein: p1135_RIBO_FSpeptide_HEL
[21:33:40] Folding@home Core Shutdown: EARLY_UNIT_END
[21:33:43] CoreStatus = 72 (114)
[21:33:43] Sending work to server

my laptop completed one of those bad boys, right after failing the first one. sucks, in a sense, because that's wasted points. lol if these failures aren't cpu faults necessarily, then partial credit would be nice, as they get sent back to server to be evaluated anyway.
Click to expand...
I had the same problem when I was overclocking. I throttled back the OC a little bit and have not seen a WU crap out on me since. AFAIK, when it does the EARLY_UNIT_END you do get partial credit.
 
The only trouble I have with 600 pointers is that F@H crashes when it finishes. I still get credit for the WU but it crashes when it goes to get a new WU after finishing a 600 pointer.
 
You must log in or register to reply here.
Back
Top