Hi! I have same problem since 20 March.
3-5 WUs fails, one work. I am using overclocked mac, so i thought that problem in overclocking. Yesterday i turned overclocking off, but have same problem today . My mac works stable with overclocking half year, and i see no problems in other applications.
Problem project for me is 6012. It reports early unit end and unstable machine errors. Most of time it fails immediately after start:
[20:46:35] Project: 6012 (Run 0, Clone 442, Gen 81)
[20:46:35]
[20:46:35] Assembly optimizations on if available.
[20:46:35] Entering M.D.
[20:46:41] Completed 0 out of 500000 steps (0%)
[20:47:00] mdrun returned 255
[20:47:00] Going to send back what have done -- stepsTotalG=500000
[20:47:00] Work fraction=0.0005 steps=500000.
[20:47:04] logfile size=11829 infoLength=11829 edr=0 trr=25
[20:47:04] logfile size: 11829 info=11829 bed=0 hdr=25
[20:47:04] - Writing 12367 bytes of core data to disk...
[20:47:04] ... Done.
[20:47:04]
[20:47:04] Folding@home Core Shutdown: EARLY_UNIT_END
[20:47:05] CoreStatus = 72 (114)
And sometimes it fails after 2-4%.
Project: 6012 (Run 0, Clone 442, Gen 81)
Moderators: Site Moderators, FAHC Science Team
Re: Project: 6012 (Run 0, Clone 442, Gen 81)
Welcome to the foldingforum.org, Gred.
I've split your post off from a topic that was about a different WU. At least when we're talking about specific WUs, we expect new topics on each one.
So far nobody else has returned that WU yet. It will have been reassigned when you returned it with an error, so we should see another report before long. If they complete it successfully, the assumption will be that there's a problem in your hardware. If they return a similar error, we'll report it as a bad WU and have it suspended.
I've split your post off from a topic that was about a different WU. At least when we're talking about specific WUs, we expect new topics on each one.
So far nobody else has returned that WU yet. It will have been reassigned when you returned it with an error, so we should see another report before long. If they complete it successfully, the assumption will be that there's a problem in your hardware. If they return a similar error, we'll report it as a bad WU and have it suspended.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: Project: 6012 (Run 0, Clone 442, Gen 81)
@bruce;
Is it necessary to start a new forum thread for each and every WU that fails?? I itemized a number of WUs in a post I added to the Project 6014 thread that is a companion to this thread. In my posting there were multiple 6012 WUs reported, but with different RCG than R0C442G81. Do you know whether there has been a check of those WUs against the "DATABASE"?
These WUs are failing at the 1% to 7 % folding stage and that means a lot of new threads.
Is it necessary to start a new forum thread for each and every WU that fails?? I itemized a number of WUs in a post I added to the Project 6014 thread that is a companion to this thread. In my posting there were multiple 6012 WUs reported, but with different RCG than R0C442G81. Do you know whether there has been a check of those WUs against the "DATABASE"?
These WUs are failing at the 1% to 7 % folding stage and that means a lot of new threads.
What is past is prologue!
Re: Project: 6012 (Run 0, Clone 442, Gen 81)
Each WU is unique. If you're having trouble with Project: 6012 (Run 0, Clone 442, Gen 81) and somebody else has already posted that they had a problem with it, we would like them to find each other. A general statement saying I've had problems with a number of WUs from project xxxx doesn't move us any closer to identifying a bad WU. If the problem is in your machine, somebody reading your post might suggest you reduce the overclock or you run memtestg80 -- so how you post depends on what you THINK the problem might be and somebody will either confirm that or demonstrate that it's not that.Aardvark wrote:@bruce;
Is it necessary to start a new forum thread for each and every WU that fails?? I itemized a number of WUs in a post I added to the Project 6014 thread that is a companion to this thread. In my posting there were multiple 6012 WUs reported, but with different RCG than R0C442G81. Do you know whether there has been a check of those WUs against the "DATABASE"?
These WUs are failing at the 1% to 7 % folding stage and that means a lot of new threads.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.
Re: Project: 6012 (Run 0, Clone 442, Gen 81)
@bruce,
I appreciate the logic of your system and I also appreciate your moving the guts of my post to a new thread. Your conclusions after reviewing the Database are too limited IMHO. I do not think we can assign the cause to "hardware" exclusively. I would include System Software and Client/Core Software in the list of "ususal suspects"....
I appreciate the logic of your system and I also appreciate your moving the guts of my post to a new thread. Your conclusions after reviewing the Database are too limited IMHO. I do not think we can assign the cause to "hardware" exclusively. I would include System Software and Client/Core Software in the list of "ususal suspects"....
What is past is prologue!
Re: Project: 6012 (Run 0, Clone 442, Gen 81)
Right. The "usual suspects" it is then.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.