Over a 1/3 of the tasks get this error in Win7.

https://boinc.tbrada.eu/result.php?resultid=38595

<core_client_version>7.8.3</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -1073741819 (0xc0000005)</message>
<stderr_txt>
PADLS Experiment. 8 1 4 6 9 7 2 5
ASS_DLK10A: 12496 in 0.625 s
PSEVDOASS_DLK_NEW: 0 in 3.405 s
KF DLK: 10304
Split 1/9 Offset 0 size 1144 t 0


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x000000000040edff read attempt to address 0xFFFFFFFF

Engaging BOINC Windows Runtime Debugger...

Over a 1/3 of the tasks get this error in Win7.

https://boinc.tbrada.eu/result.php?resultid=38595

[code]7.8.3

(unknown error) - exit code -1073741819 (0xc0000005)

PADLS Experiment. 8 1 4 6 9 7 2 5
ASS_DLK10A: 12496 in 0.625 s
PSEVDOASS_DLK_NEW: 0 in 3.405 s
KF DLK: 10304
Split 1/9 Offset 0 size 1144 t 0

That's my mistake!
Thanks.

Tomas Brada
you must remove from the file Rows_part2_8321.txt all rows starting with the number 8.
also
you must remove from the file Rows_part2_8321.txt all rows starting with the number 7.

See
https://boinc.progger.info/odlk/forum_thread.php?id=104&postid=3126

Hello,

as I read about "cancelling WUs with 8 or 7 as first Digit in start row - is it OK for me to cancel WUs which are named "padls2_7..." as they have a leading 7 in start row?
They seem to be killing themselves in seconds or running for Hours (6+ Hours Right now)

Or are the non-self-destruction WUs ok and they run that long?

Greetings,

=Lupus=

*EDIT* nevermind, just saw all WUs went into Status "not needed anymore" - but my Client does not update because BOINC Scheduler sends me http error 413.

Just hit update and the scheduler will abort any tasks that are not needed. It should not be necessary, because it is set to update every twice a hour. If the task is not aborted after you update, that means the tasks are still needed. Check your account for the task status.
Regarding the Scheduler http error 413, it should be transient. Try again and if the problem persist, open new thread. But you contacted scheduler 20 minutes ago, so I assume it is solved already.

HTTP error 413 still there.
So I dont really get the updated info from server side.

Manually aborted the tasks as all of them were of the 7.... batch which got cancelled.

Seems error 413 means "answer too big" - either my or your side cant handle the size of the request.
Something the BOINC makers should know about.
Will open new thread.

Some workunits with first number 7 were resurrected. And they are already gone. Amazing power.
I also increased replication on still tasks from first batch (10). Gone too.

Exit status -1073741819 (0xC0000005) STATUS_ACCESS_VIOLATION 100% error still this morning on my Win 7 Box's

Still being issued.
https://boinc.tbrada.eu/workunit.php?wuid=28994

It took 30 secs all together to crash the tasks. Not worth the hassle to cancel them. We will catch the failures at post processing.
If they crash immediately, let the tasks crash.
If they take more than 2 minutes to crash, Please report.

It took 30 secs all together to crash the tasks. Not worth the hassle to cancel them. We will catch the failures at post processing.
If they crash immediately, let the tasks crash.
If they take more than 2 minutes to crash, Please report.

Maybe its not worth it for us to run your project then.

lol

Maybe its not worth it for us to run your project then.

Let me note that the project is in test mode.

Errors are always when starting a new project or a new experiment in an existing project.

For my part, I apologize for my mistake (wrong WUs starting at 7 and 8).

It took 30 secs all together to crash the tasks. Not worth the hassle to cancel them. We will catch the failures at post processing.
If they crash immediately, let the tasks crash.
If they take more than 2 minutes to crash, Please report.

Maybe its not worth it for us to run your project then.

Sorry. The erroring tasks take only few seconds to finish, right? So very little cpu is wasted. It is not easy to gather wu ids to cancel. Even the failure is a result. Maybe we will grant some credit for the failed tasks if that is what you want.

We identified the reason why they fail so now it is OK to let the errored tasks crash since they use very little cpu.

I cancelled tasks with 7 and 8 at start as soon as the problem was found. Then I received a list of tasks to resurrect, but it seems I made a mistake, or the list was wrong and resurrected tasks that still crash. We will let this batch (12) finish and then figure out which rows are missing and re-issue good tasks.
The batch 10 is finished and most likely we will have more tasks to send after it is analysed by miss Makarova.

We will let this batch (12) finish and then figure out which rows are missing and re-issue good tasks.
The batch 10 is finished and most likely we will have more tasks to send after it is analysed by miss Makarova.

+1 ... waiting for more

+1 ... waiting for more

Задания обрабатываются 4540

https://boinc.tbrada.eu/server_status.php

When there will be 0 :)

There are no running 8-begin results, because all have been cancelled.
7-begin results were cancelled, but then some of them were resurrected, because miss Natalia sent me new version of batch 12.
There are, however, no successful 7-begin results from batch 12.

When there will be 0 :)

I thought you are going to analyse and issue new batch after, possibly the generator is fixed.

I do not want to launch a new branch of the experiment with the current branch.

I can send you sources of generators 1 and 2 to prepare them for a new branch.
This is a minor modification due to a change in the DLS diagonal.

Then I will send you an array of rows.

PS. All WUs in the second installment, starting with 7 and 8, must be canceled.
We misunderstood each other.
At first, I only saw rows starting with 8.
I deleted these rows and sent you a new list.
But! Then I saw incorrect rows starting with 7.
I asked you to remove these rows from the list.

Tomas Brada
you must remove from the file Rows_part2_8321.txt all rows starting with the number 8.
also
you must remove from the file Rows_part2_8321.txt all rows starting with the number 7.

But you did not understand me. I did not send you the third list yet, I thought that you yourself delete the rows beginning with 7.

We hurried. No need to hurry!

About the new branch of the experiment PADLS here
https://boinc.progger.info/odlk/forum_thread.php?id=107

Unfortunately, in Russian.

I can send you sources of generators 1 and 2 to prepare them for a new branch. This is a minor modification due to a change in the DLS diagonal. Then I will send you an array of rows.

Good. You can send anytime.

PS. All WUs in the second installment, starting with 7 and 8, must be cancelled.

Done! Sorry for misunderstanding.