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

1760 point smp shutdown, ouch

Z

zackboll

Limp Gawd
Joined
Oct 28, 2004
Messages
470
folding on pentium d 2.8

[20:09:44] Completed 475000 out of 500000 steps (95 percent)
[20:38:28] Writing local files
[20:38:28] Completed 480000 out of 500000 steps (96 percent)
[21:07:08] Writing local files
[21:07:08] Completed 485000 out of 500000 steps (97 percent)
[21:36:03] Writing local files
[21:36:03] Completed 490000 out of 500000 steps (98 percent)
[22:04:49] Writing local files
[22:04:49] Completed 495000 out of 500000 steps (99 percent)
[22:33:32] Writing local files
[22:33:32] Completed 500000 out of 500000 steps (100 percent)
[22:33:33] Writing final coordinates.
[22:33:33] Past main M.D. loop
[22:33:37] CoreStatus = 0 (0)
[22:33:37] Client-core communications error: ERROR 0x0
[22:33:37] Deleting current work unit & continuing...
[22:37:41] - Preparing to get new work unit...
[22:37:41] + Attempting to get work packet
 
anyone else get one of these on the protein 2604?

post edited, it was the 2604
 
Just finished one of these badboys last night and another one last Wednesday. No issues here.
 
it was actually the 2604 that crashed.

Ive been getting 2605 on my opteron 175 and they have been going through fine

Zack
 
I've turned in 3 or 4 2605's in the past few days with no issues on x2 3800, 4600 and c2d 7200's...


 
Schro said:
I've turned in 3 or 4 2605's in the past few days with no issues on x2 3800, 4600 and c2d 7200's...


Click to expand...

Yeah, i edited my post. I have been turning in the 2605 fine also, it was the 2604 that shutdown.

Zack
 
zackboll said:
Yeah, i edited my post. I have been turning in the 2605 fine also, it was the 2604 that shutdown.

Zack
Click to expand...

THis worries me... I've got one or two of the buggers cooking right now...

37% done on this rig in the sig.. so a little under 2 days...
 
let me know how you make out. The pentium D that just crashed on a 2604 just got another one.

Zack
 
I returned a 2604 earlier today that was running on a C2D E6400@3.2Ghz. It took a while to get it done. For some reason, the client stopped one time which wasted about 4 hours of time but started from where it stopped. After that, my system froze up while I was at work and lost at least another four to six hours of time. I messed with RAM settings a bit in the BIOS and everything has been running fine since.

 
The pentium D is non-overclocked stock settings dell built computer. I dont know why the first one didnt go through, but the second one went fine. Maybe there is a stability issue with that core.

Zack
 
I successfully turned in a 2604 from both an x2 4600 and a c2d 2.0 ghz earlier today...
 
Sometimes any work unit can crash which is different then what the OP stated.

I too have had this happen, and happen on a few machines. The cure is actually pretty simple. About once a week try to catch the machine after it just up-loaded and stop the client. Delete the work folder, the core and the que.dat then restart the program.

Not sure why but the work folder seems to get filled with junk and won’t clean itself up. I download a new core just in case.

Once I started that practice I very rarely see any type of failure.

Luck


 
You must log in or register to reply here.
Back
Top