AMD Athlon 64 X2 3.2GHz (Stock) 54-57 C
WinVista Ultimate x86

No BSOD... Fresh install (today).

-.-"

---

We cannot do a thing for you or offer suggestions when your computers are hidden.

You can look at mine to see what information is available when you unhide them ... but, if you want advice, well, we need to look at the tasks and we cannot do it with hidden computers.

We cannot do a thing for you or offer suggestions when your computers are hidden.

You can look at mine to see what information is available when you unhide them ... but, if you want advice, well, we need to look at the tasks and we cannot do it with hidden computers.

I doubt it's a computer error.
Almost all the failed WU failed right at the start.

I think I just got a bad batch of WUs... right?

---

Given the wide variety of task names, and the fact that noone else jumped in to report the same problem, I would not describe it as "a bad batch of tasks".

On the other hand, it seems only your Mini tasks failed. So, it seems something occurred to cause Mini a problem.

If you'd prefer not to show all of your machines, you could just let us know the host ID of the one that had the errors.

---

Rosetta Moderator: Mod.Sense

We cannot do a thing for you or offer suggestions when your computers are hidden.

You can look at mine to see what information is available when you unhide them ... but, if you want advice, well, we need to look at the tasks and we cannot do it with hidden computers.

I doubt it's a computer error.
Almost all the failed WU failed right at the start.

I think I just got a bad batch of WUs... right?

It almost looks like access violations based on run times.
If you really want help, then you need to post links to the tasks and unhide your computers. We can only guess as to what went wrong based on the screen shot.

There is one question though I would like to ask, Are you OC'd at all?
Rosie is very specific about how much OC you can put on a cpu before the task goes up in flames. If you are not OC'd, then again we need to be able to see your computers and the tasks that you show below.

This is the PC: https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=1009549


Tech info on the PC:



CPU is not OC'ed (6400+ are very crappy OC-ers...)

---

Chilean, I took a quick look and you have a common error of:

<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
app_version download error: couldn't get input files:
<file_xfer_error>
<file_name>minirosetta_database_rev26003.zip</file_name>
<error_code>-120</error_code>
<error_message>signature verification failed</error_message>
</file_xfer_error>

</message>
]]>

The task groups you downloaded was: cc_0_8_natcst_b2.0_hb_t303__IGNORE_THE_REST_1FEZA_10_xxxx
and
loopbuild_chunk_3_5_B_hb_t328__IGNORE_THE_REST_2GVKA_11_7557_xxxx
and
ss-neg-1je9__7365_5712_xxxx

and probably some others which are to many to put here.

I think it was some sort of file transfer error, not everything got transferred to your system for these tasks to start or complete properly.

Other users that got some of your tasks completed them ok.

Maybe someone else can elaborate on this further or correct my statement.

Chilean, I took a quick look and you have a common error of:

<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
app_version download error: couldn't get input files:
<file_xfer_error>
<file_name>minirosetta_database_rev26003.zip</file_name>
<error_code>-120</error_code>
<error_message>signature verification failed</error_message>
</file_xfer_error>

</message>
]]>

I think it was some sort of file transfer error...

Very likely seeing as it says <file_xfer_error> above!

I notice the tell-tale Norton icon in Chilean's notification area going by the screenshot and recall some reports of mini files getting quarantined by Norton Internet Security (but not Norton 360).

Could you take a look inside Norton and see if the file has been quarantined and manually restore it? It may be a quick and easy solution.

Also report it as a false positive through Norton if you can find the option when you restore.

Just a quick guess.

Your results files show a signature verification error on one of the key files that Mini uses. These generally occur when the file download doesn't go properly. Could also be the file is modified (corrupted) by antivirus. Anyway, Mini will not be able to run properly until a good copy of the file is downloaded.

One way to achieve this might be to delete it before those Mini tasks run. The file having problems is minirosetta_database_rev26003.zip By deleting it, BOINC will either see that it's not downloaded and try to get it, or it will fail (which it was doing anyway). And the next scheduler request should bring it down again. ...otherwise, you'll have to reset the project, which loses all the work in your queue, so you have to babysit and report it in if you don't want to lose it.

---

Rosetta Moderator: Mod.Sense

Well, I'm currently crunching two Mini's... no problems.

---

This means you got the all the files needed this time around.
Keep an eye on your firewall and antivirus if you see this happen again.
Be sure to allow the mini and the beta to be added as ok files/processes in the firewall and antivirus.

Well, I'm currently crunching two Mini's... no problems.

Well, I'm currently crunching two Mini's... no problems.

This post seems to be relevant here. Seems like the file can be downloaded successfully even after getting rejected initially, so when you restore it's found to be already there. Maybe that's why you get past 0 seconds now?

Is it NIS you're running?

---

Well, I'm currently crunching two Mini's... no problems.

This post seems to be relevant here. Seems like the file can be downloaded successfully even after getting rejected initially, so when you restore it's found to be already there. Maybe that's why you get past 0 seconds now?

Is it NIS you're running?

Yeah, '09.

I have it on my laptop as well, but never had this problem before. Seems to be fixed now though.

---

Is it NIS you're running?

Yeah, '09.

I have it on my laptop as well, but never had this problem before. Seems to be fixed now though.

It seems to be a peculiarity of that programme - not of N360 which includes the same firewall. It does sort itself out but shouldn't happen in the first place. Reports of false positives should help prevent it from affecting others.

Glad it sorted itself out anyway.

---