• 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.

EARLY_UNIT_END?

C

CoW]8(0)

[H]ard|Gawd
Joined
Jul 25, 2005
Messages
1,427
[00:58:48] Warning: check for stray files
[00:58:48]
[00:58:48] Folding@home Core Shutdown: EARLY_UNIT_END
[00:58:48]
[00:58:48] Folding@home Core Shutdown: EARLY_UNIT_END
[00:58:53] CoreStatus = 7B (123)

Is this a sign of a bad overclock?
 
I think the error 0x7B are usually the sign of bad overclock and if you think yours ended due to an overclock then lower it slightly and make sure it's prime stable before running folding.
 
CoW]8(0);1031504711 said:
[00:58:48] Warning: check for stray files
[00:58:48]
[00:58:48] Folding@home Core Shutdown: EARLY_UNIT_END
[00:58:48]
[00:58:48] Folding@home Core Shutdown: EARLY_UNIT_END
[00:58:53] CoreStatus = 7B (123)

Is this a sign of a bad overclock?
Click to expand...

Knowing which work unit you were working on would help. If you have been folding a while and this is your first early end, don’t worry about it, Stanford has explained that some are intended to fail. Most of the time a legitimate early end will send results back to the servers and give you partial credit.

If you are seeing this more then once every couple of weeks then yes, there is a possibility you are pushing your CPU too hard.




 
Which protien was it and on which frame did it error out.

I've found that b7 errors don't send anything back to Stanford so you dont get any credit for it.
If you did not send anything back then you'll download the same work unit again because Stanford thinks you may have had a bad download and not a bad work unit.
If so keep an eye on your deadlines as it not reset for a repeat download.
If you do re-download and it errors out again without sending anything back then you'll download the same work unit a third time before you get a new work unit.

It has got better lately with these b7 but I still get 1 every couple of weeks.

Luck ............ :D
 
Work Unit: 2653
Which I've been told is a stable work unit.

The problem is prime isn't giving errors, only F@H.
 
How many proteins have you folded on that box ?
If only a few then it could be you just got unlucky and got a bad WU.
But if another one errors out in the near future then start retesting as SMP folding pushes a box harder than prime does.

If Prime still proves stable then one thing to look at is memory timings.
The SMP cores are very sensative when you've got the memory timings tight so slacking them off a little may improve your stability.

Ps. Is the box overclocked ?????? Specs would help.

Luck ............. :D
 
CoW]8(0);1031504797 said:
Work Unit: 2653
Which I've been told is a stable work unit.

The problem is prime isn't giving errors, only F@H.
Click to expand...

Folding is more strenuous than Prime. It might not heat the core up as much, but heat isn't everything.



 
I think you guys may be very right. I've decided to back off my OC from 3.2Ghz to 3.0Ghz.

If that proves to be stable, then I'll have to start playing around with voltage/clock combinations since stock voltage doesn't seem to be cutting it.

It might also be my RAM stability. I feel like I OCing my RAM makes my CPU OC less stable which is strange.
 
You must log in or register to reply here.
Back
Top