Getting too much calculation errors. This morning downloaded 10 wus and first 4 of them (when looked to check, I saw that for 2 of the wus the other crunchers' computers did the same) gave calculation error after seconds from calculation start. Is there a problem?

Yes there is.

I posted this on April 4 already in the thread: Compute error.
Lots of crunchers have this issue.

Looks like you are probably trying to run 4 tasks at a time in 2GB of memory. That isn't a lot of room, and the latest Rosetta version seems to have an issue which is using more memory then usual at the moment.

So much of your hard disk activity, especially if you are running other applications, is probably due to page faults and memory swaps. These are controlled by the operating system, not by BOINC. And that is why it probably seems as though BOINC is ignoring your preference not to use the disk so much ...because it isn't using the disk very often, the operating system is, as a side-effect of running the BOINC tasks along with the other applications you are running.

In a nutshell, your goal seems to be to have a more responsive PC. The way to achieve this is to get BOINC to use less memory. You can do this by running fewer tasks at a time (by limiting the number of CPUs BOINC is allowed to use), or by limiting the amount of memory BOINC is allowed to use when the machine is in use (which will eventually force at least one of the tasks into a waiting for memory state). Either of these approaches should improve the usability of your machine, although they will likely reduce the overall amount of BOINC work you complete each day.

Another approach would be to attach to a second BOINC project, one with work units that require less memory. Set up the resource shares so that at least 25% goes to the other project, and BOINC will generally be running at least one of those low-memory tasks along with 3 from Rosetta. If you attach to another project, then I'd suggest using the preference for the amount of memory BOINC is allowed to use. If the Rosetta tasks you are running consume a lot of memory, BOINC will begin running other tasks until it finds some that can run within the amount of memory BOINC is allowed to use. These will tend to be from the other project. So, you could still be crunching with all 4 CPUs and have a more responsive machine.

...is it possible to be corrupted while downloading.

It is possible for corruption to occur to any data that passes over a network. However, BOINC has signatures that double check the integrity of the files you receive. When a signature mismatch is found, the error is reported differently and the task is not run.

Generally the error about gzipping is due to the output file not being produced. So it isn't there to zip. And this is because the error occurred before any output was produced.

Levent TERLEMEZ
Looks like their task reported back with this:

ERROR: rsd_type_list.size()
ERROR:: Exit from: ....srccorefragmentFrame.cc line: 62
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

The task was restarted five times. If the task was unable to reach a checkpoint in that time, then the task is aborted for you. But I would expect a message about too many restarts with no progress rather then the one you got.

It's working for me, at the time of this post. Are you still having a problem?

I only see 2 validation errors out of about 30 completed tasks. No messages in them to indicate any specific problem, and they were returned before the deadline. ...were there any messages produced in the messages tab when these tasks completed? How much of your machine's memory is BOINC allowed to use?

I see you have several active machines. It sounds like they are having some problems with the graphics display. The following details might be helpful in tracking the problem:

Which WU is having trouble displaying?
Which Rosetta application version is that WU running?
Which operating system has the problem?
Do you have the same problem on more than one machine?
You've been crunching for some time, so is it safe to assume you just noticed the problem recently?
Can you further explain what is not shown? Is there an empty box out of the three? Or the whole screen is blank?
Does the protein display correctly when you first bring up the graphic?
Are you viewing the "screensaver"? Or the "graphics"?