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

Anyone else having problems with 6013?

H

HossWTC

n00b
Joined
Mar 20, 2004
Messages
52
Fellow DC'ers,

I'm having an issue when I receive project 6013 work units. It appears to download the WU, then gets into M.D, then it fails before the first checkpoint with a MS Visual C++ runtime error.

My machine runs all other project work units without issue, so I'm confused why this project is presenting a problem.

Here's a snip of the log showing the error:


[02:13:15]
[02:13:15] *------------------------------*
[02:13:15] Folding@Home Gromacs SMP Core
[02:13:15] Version 2.19 (Mar 12, 2010)
[02:13:15]
[02:13:15] Preparing to commence simulation
[02:13:15] - Looking at optimizations...
[02:13:15] - Created dyn
[02:13:15] - Files status OK
[02:13:15] - Expanded 979419 -> 10427873 (decompressed 1064.6 percent)
[02:13:15] Called DecompressByteArray: compressed_data_size=979419 data_size=10427873, decompressed_data_size=10427873 diff=0
[02:13:15] - Digital signature verified
[02:13:15]
[02:13:15] Project: 6013 (Run 0, Clone 95, Gen 85)
[02:13:15]
[02:13:15] Assembly optimizations on if available.
[02:13:15] Entering M.D.
[02:15:48] Completed 0 out of 250000 steps (0%)
[02:46:11] CoreStatus = 3 (3)
[02:46:11] Client-core communications error: ERROR 0x3
[02:46:11] Deleting current work unit & continuing...
[02:46:23] Trying to send all finished work units
[02:46:23] + No unsent completed units remaining.
[02:46:23] - Preparing to get new work unit...
[02:46:23] Cleaning up work directory


My new rig consists of the following:
EVGA P55 FTW
I7 860, o/c to 3.5 (160x22)
4GB Corsair DDR3
Win7 x64 pro

I am overclocking a bit, but since the other projects run properly, I don't think it's the o/c.

Any help resolving this problem would be welcome.
 
Last edited:
yep. a couple weeks ago my machine kept crashing with MS Visual C++ errors with the same symptoms... 0% when the error popped up. at first i thought my RAM was going bad or maybe my O/C was unstable again.
last time it happened i noted the WU and it was 6013. i just delete my queue.dat & work folder and let it download a different WU. every now and then it pops up and crashes my SMP client again but i just delete queue.dat/work, rinse & repeat
 
Well, at least this is somewhat good news... I'm glad it's not just my system.
:)
 
I've had a couple of them. I posted one on FF and they eventually killed it.

 
of course they finally kill it 2 days before i plan to move.. oh well.. but this is why i stopped folding 2 weeks ago when these things popped up..
 
georgexi said:
yep. a couple weeks ago my machine kept crashing with MS Visual C++ errors with the same symptoms... 0% when the error popped up. at first i thought my RAM was going bad or maybe my O/C was unstable again.
last time it happened i noted the WU and it was 6013. i just delete my queue.dat & work folder and let it download a different WU. every now and then it pops up and crashes my SMP client again but i just delete queue.dat/work, rinse & repeat
Click to expand...

I had one the other day that kept getting re-downloaded. I'd delete it, then restart the client and it would grab the same exact broken WU again. It did this around 4-5 times in a row until I just stopped it, deleted the WU, and waited like 10 minutes before restarting the client.
 
OK, got one of these bad 6013 WUs myself. The client has been trying to work on it most of the evening and of course it crashes followed by a redownload of the same unit. The system is also very unresponsive when these WUs are being processed. It's not looking good for A3 if this sort of thing continues... /shakes head
 
I got 4 in a row about a week ago that all failed. I just shut the sucker down for a few hours, tried again and got something else. I haven't seen a 6013 myself since though my SMP has been on and off during that time.
 
I keep getting the damn things on one of my machines. Since I wasn't home for 24 hours, that machine ended up spending at least 12 hours trying to process the damn thing. The estimated time to completion was more than five days. I end up deleting the work folder and the queue.dat file each time I notice one and restart the client. This will usually get me another work unit although they always end up being 6701s. While those things suck ass for points, at least they only take about 24 hours to process and garner me more than 300PPD on a 3.4Ghz quad.

 
It's good they're suspending it. I only had a minor brush with the 6013 but other people had tons of issues with them.
 
You must log in or register to reply here.
Back
Top