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

P6023: Bad Work Units?

W

wickedld9

Gawd
Joined
Mar 11, 2004
Messages
661
Got one of these earlier in the day on my 2600K and it failed just a second or so after hitting 0%. Machine has been stable for every other work unit I've thrown at it for over a week including -bigadv. I went back and threw some benchmark WU's at the box and they ran fine. I transferred one of the P6023 to my new 2500K and it failed immediately also. It fails regardless if it's stock clock or overclocked on either system.
Anyone else getting these and having issues? Anyone on SB getting these and having issues? I have one that I could try to upload and see if someone else wants to try it out.


Update edit: According this thread they are bad work units. Now it would be great if we can stop getting them.
http://foldingforum.org/viewtopic.php?f=19&t=17285
 
Last edited:
weird, might just be a bad WU. ran fine on my x4 940

Code: 
Project ID: 6023
 Core: GRO-A3
 Credit: 475
 Frames: 100


 Name: smp
 Path: C:\Folding@home SMP\
 Number of Frames Observed: 300

 Min. Time / Frame : 00:05:43 - 6,740.8 PPD
 Avg. Time / Frame : 00:07:41 - 4,326.1 PPD
 
Last edited:
Every one of these is failing right before it reports 0% complete. I just got 6 in a row. Looks like I'm taking these two rigs offline until I/we can resolve whatever the issue is.

2600K stock as they come speeds with memory knocked back to 1333MHz. It chews through every other work unit without a hitch.
 
wickedld9, grab the two .dat files for this unit from the work directory before it fails and send them to me. I'll add them to the benchmark utility and try them on some of my hardware to see if they have the sme issue. Also, have you checked FF to see if these have been reported by others on SB? I don't think we have many folks running SB yet for comparison.

I'll PM you contact info.
 
wickedld9 said:
Every one of these is failing right before it reports 0% complete. I just got 6 in a row. Looks like I'm taking these two rigs offline until I/we can resolve whatever the issue is.

2600K stock as they come speeds with memory knocked back to 1333MHz. It chews through every other work unit without a hitch.
Click to expand...


it was probably just sending you the same work unit over and over. can usually solve the problem by deleting the queue file.
 
I looked around on the forums last night but didn't see anything. I just made a post on there with a good description of what happens. Of course now I'm at work and didn't think to bring the logs or dats. ;)

I was deleting the work folder, queue.dat, and work unit info file but it was still pulling them/it down.

Thanks for the help guys.
 
with the amount of bad WU's as of late i think the problem is in the script used to create the WU's.
 
oh i thought it was my client, So i deleted the entire folder and set it up again, "oh look it works" but it got a different WU :)

would be cool if you could set up the GPU tracker to "ban" WUs that have failed.
 
DeFex said:
oh i thought it was my client, So i deleted the entire folder and set it up again, "oh look it works" but it got a different WU :)

would be cool if you could set up the GPU tracker to "ban" WUs that have failed.
Click to expand...
Usually changing the Machine ID of the client should get you a WU with different RCG.
 
You must log in or register to reply here.
Back
Top