LHC@home

I just received two work units. When I clicked om the \"Show Graphics\" button, the job terminated at once with \"Computation error\". I (unfortunately) tried this button on bothe work units, with the same result.

---

When I clicked on the \"Show Graphics\" button, the job terminated at once with \"Computation error\".

Me too :-(

I just received two work units. When I clicked om the \\\\\\\"Show Graphics\\\\\\\" button, the job terminated at once with \\\\\\\"Computation error\\\\\\\". I (unfortunately) tried this button on bothe work units, with the same result.

I did exactly the same, clicking on \\\"show graphics\\\", after more than 3 hours ruuning of a LHC WU.
So got one WU finaly and now killed it myself...by a simple click.

---

Greetings from,
TJ

Me too :-( [damn buttons -:)]

And here is the explanation:

The BOINC FAQ Service

---

Me too :-( [damn buttons -:)]

And here is the explanation:

The BOINC FAQ Service

Me too, this newbie coding had the following effects:

- killed the WU
- killed the boinc client
- killed the boinc manager

Not even a system restart could fix it and make BOINC run again.

I received the following messages when forcing boinc.exe to load:



I had to delete the whole LHC directory to make it work again...

Thank you very much!

It looks like - SCREEN SAVER IS KILLING THE TASKS!
No matter, is Show Graphics clicked or not.
6 of 7 tasks crushed, sad.

---Update---
SOS!!!
Unfortunately...
If Windows screen saver is set to BOINC, all the tasks are dying.
This effect appears at least on all machines with ATI video cards. No matter, which model. New or, for example, 3+ years old.

---

New rule for LHC@home - avoid Show Graphics.

---

Warped

funny you say that and then see your sig beneath it

---

funny you say that and then see your sig beneath it

We are referring to (Show graphics) in the tasks list while the task is running, not posts on the message board ;-)

By the way, your account name means (What next).

In fact, whats the point of a graphic other than complicating the code? Feel free to leave it out. It takes away from the crunching anyways.

I just got my first 2 WU’s 10 months to the day from the last LHC WU’s that I completed. The first one got a computational error 3 minutes into it. It may be just a coincidence, but the error occurred at the exact moment that the screen saver kicked in. The next WU started up immediately after and it ran to completion in about 10 minutes. This time I was actively using the computer the whole time so the screen saver never kicked in. So it seems that the screen saver is causing problems.

---

Happened to me too. Signed up in August and they were the first projects I got - and like within a minute of completing. It\'s a brand new computer (my old one died last week) so the video card shouldn\'t need updating. There are 4 more WU\'s lined up luckilly and they only take about 45 minutes.

This happened to me too. Too bad I liked the screensaver. :(

Like others, I recommend they just tear it out until they get a chance to fix it. The screensaver is nice, but like this there\'s no point in it.

I hope, this bug is not difficult to find and to fix.
And I hope, the project team is reading our messages.

---

Seen it, knew the graphics would bite us in the ass eventually. They were way too pretty.

We have been considering killing the graphics as they are a stumbling block when compiling. I'll pester bigmac and Alex.

Personally, I have no intention to shut down the screen saver for all the other projects whose screensavers play together just fine just because LHC’s doesn’t. So unless the goal of this project is to see how many errored out WU’s a participant can tolerate before dumping the project, I think this problem should get fixed.

Me too, I\'m a victim of the \"show graphics\" button. :-(

---

Two workunits received today but were not completed due to error reported by file upload server: nbytes missing or negative.

Me too.

---