Last couple of days I have received work. A good number of the jobs fail quickly with:

STATUS_ACCESS_VIOLATION

---

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

The founder of my Team has had 18 of these in 89 work units.
A rather high failure rate.

---

The founder of my Team has had 18 of these in 89 work units.

The founder of your team hasn't done any Rosetta work since the end of April 2016.

---

Grant
Darwin NT

The founder of my Team has had 18 of these in 89 work units.

The founder of your team hasn't done any Rosetta work since the end of April 2016.

Grant just so you know

The founders name is Spider, he has a number of ids as he just sets a new computer often with a new id (unfortunately mostly due to Windows crashes, failed backups, a few e-mail issues and setting up a "new" user after a crash instead of an "existing user"), so the founder Spider and the active user Spider are one and the same.

Keep the shiny side up

Conan

---

The founders name is Spider, he has a number of ids as he just sets a new computer often with a new id (unfortunately mostly due to Windows crashes, failed backups, a few e-mail issues and setting up a "new" user after a crash instead of an "existing user"), so the founder Spider and the active user Spider are one and the same.

OK, only showing one error there (all the others have probably been cleared by now), but plenty of other Tasks have completed & Validated OK, so there's a good chance that there was a group of faulty Tasks in that batch.

---

Grant
Darwin NT

>>> mostly due to Windows crashes

I'm curious, what does he do to make Windows crash? My machines run Windows, (8.1 x64), and I don't recall EVER having a Windows crash for example.

And on topic, I've received 6 more of these crashing units this morning. They are still sending them out.

---

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