LHC@home

the latest batch contained a lot of very small WU's.... for many of them I received 0.00 credits while others got at least some 0.0X... is there any perticular reason for that? I have the problem on both hosts

for example results 8138978, 8138962, 8138831, 8136794, 8136756, 8136712

although the WU's were finished succesfull, the validate state says invalid :(

---

BOINC.BE: The team for Belgians who love the smell of glowing red cpu's in the morning

You partly answered yourself.

The answer to why they are invalid, prolly is that there is something wrong with your rig, either too much overclock or too much dust and proc or RAM or mobo became unstable due to overheat.

TigerWing --

I'd do like what Colt suggested. Recheck your machine(s) to make sure they are free of dust/dirt that might be causing them to run hot. Also, check your memory sticks carefully, and make sure they are capable of running at the speeds required for your CPUs. Finally, if you are overclocking, back off a bit on the speed, and see if the problems go away ... Good Luck

---

If I've lived this long, I've gotta be that old

the latest batch contained a lot of very small WU's.... for many of them I received 0.00 credits while others got at least some 0.0X... is there any perticular reason for that? I have the problem on both hosts

for example results 8138978, 8138962, 8138831, 8136794, 8136756, 8136712

although the WU's were finished succesfull, the validate state says invalid :(

http://lhcathome.cern.ch/result.php?resultid=8138978

If you look at the debug info, there is no Sixtrack.exe mentioned, rather there is
a bunch of seti stuff in the debug.
I think it's more likely that the boinc client has gotten confused rather than an overheating issue.

---

I'm not the LHC Alex. Just a number cruncher like everyone else here.

http://lhcathome.cern.ch/result.php?resultid=8138978
If you look at the debug info, there is no Sixtrack.exe mentioned, rather there is a bunch of seti stuff in the debug.
I think it's more likely that the boinc client has gotten confused rather than an overheating issue.

Similar problem in thread http://lhcathome.cern.ch/forum_thread.php?id=2387

---

I am Homer of Borg. Prepare to be ...ooooh donuts!

Looking at the debug, I see that this is ver. 5.5.0 of the BOINC core-client. I thought that version was pretty stable, but maybe a reload of a more recent version of the core-client might fix the issue ...

---

If I've lived this long, I've gotta be that old

In this result set there is a machine that has crunched a wu in an unreasonably short time, but is flagged as valid.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

In this result set there is a machine that has crunched a wu in an unreasonably short time, but is flagged as valid.

All results of that machine seem very unlikely to be correct.

---

I am Homer of Borg. Prepare to be ...ooooh donuts!

Looks like another machine that has confused SETI@home and LHC. When that happens, I guess the only thing to do is stop all processes, get a fresh BOINC load, then reattach to the various programs. Lots of work units get aborted, but at least the machine will start processing properly.

Don't ya just hate it when that happens .... ??

---

If I've lived this long, I've gotta be that old

thx for the replies people

I think I'm gonna leave everything like it was (just read all the possible answers) I didn't OC my machines and with the current batch of WU's, I don't have any problems (yet)...
but I keep it in mind!!

---

BOINC.BE: The team for Belgians who love the smell of glowing red cpu's in the morning

I just noticed : I still have a lot of very small WU's that are still pending? other user do have gotten credits for them??

---

BOINC.BE: The team for Belgians who love the smell of glowing red cpu's in the morning