A lot of tasks have started failing immediately with this error. For example, WU ps_200312_input_1772_33 currently has 4 failures (one each of avx, cuda55, sse2 and sse3).

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

I'm getting this same error over all of my hosts.

<core_client_version>7.9.3</core_client_version>
<![CDATA[
<message>
process exited with code 2 (0x2, -254)</message>
<stderr_txt>

Error: Number of lc points is greater than POINTS_MAX = 1000

</stderr_txt>
]]>

Last year, I had a long spate of error messages in Asteroids.

Recently, in the month of March, I've had seven, five in the past two days.

Now there are no tasks.

What's happening? Is this related to the fact that I reset the project?

See below.

Thanks for your advice.

Steven G
Oldsmar, Florida

Show names Work unit
click for details Computer Sent Time reported
or deadline
explain Status Run time
(sec) CPU time
(sec) Credit Application
286820747 122919444 468676 25 Mar 2020, 18:19:00 UTC 25 Mar 2020, 20:20:12 UTC Error while computing 0.00 0.00 --- Period Search Application v102.10 (sse2)
286820786 123598320 468676 25 Mar 2020, 18:19:00 UTC 25 Mar 2020, 20:20:12 UTC Error while computing 0.00 0.00 --- Period Search Application v102.10 (sse2)
286820702 123575949 468676 25 Mar 2020, 18:18:17 UTC 25 Mar 2020, 18:19:00 UTC Error while computing 1.22 0.36 --- Period Search Application v102.10 (sse2)
286820725 123575948 468676 25 Mar 2020, 18:18:17 UTC 25 Mar 2020, 18:19:00 UTC Error while computing 0.00 0.00 --- Period Search Application v102.10 (sse2)
286701290 123274452 468676 24 Mar 2020, 9:12:34 UTC 24 Mar 2020, 9:30:23 UTC Error while computing 0.00 0.00 --- Period Search Application v102.10 (sse2)
286699549 122936814 468676 24 Mar 2020, 8:11:26 UTC 24 Mar 2020, 9:12:34 UTC Error while computing 0.00 0.00 --- Period Search Application v102.10 (sse2)
282702657 122059322 468676 6 Mar 2020, 18:16:39 UTC 8 Mar 2020, 7:55:00 UTC Error while computing 15,284.16 12,129.09 --- Period Search Application v102.10 (sse2)

Steven G
Oldsmar, Florida

Hi Steve,

There were few issues that we've been working recently. Some of them was related to the errors you've seen as a result of some of WUs you've reported.

In first case, where WU have been reported with the following error:
* Error: Number of lc points is greater than POINTS_MAX = 1000
This is due to slightly different structure inside the newly generated WUs after new sources of data were added in the last months. We already started procedure of applying a bugfix for it. SSE2 applications are next in the list.

Next one, happened to be fount on set of WUs on various platforms:
* Unhandled Exception Detected...
This is another known issue and we'll need more time to investigate and fix.

As to your question about lack of tasks observed from time to time. Preparing WUs process can be heavy task and very time expensive. That's why in most of the time it is behind the capabilities and computation power that has been provided by all of you, our contributors.

Thank you for your patience.
Georgi

Same here Most jobs failed with

<core_client_version>7.16.3</core_client_version>
<![CDATA[
<message>
process exited with code 2 (0x2, -254)</message>
<stderr_txt>

Error: Number of lc points is greater than POINTS_MAX = 1000

</stderr_txt>

Hi all,

As of yesterday almost all CPU related Windows x64 Period search applications has been updated with applied bugfix about the 'MAX_POINTS' issue, except the 'sse2' application.

If today your client still receives tasks with application version less than 102.12 you may need to reset your project through BOINC manager.

Georgi

Georgi:

Thanks for the explanation.

I'm gratified that it was not my ineptitude that caused those mishaps and that I am not alone in experiencing them (although it is unfortunate that they happened at all).

Still no tasks, but I will continue to be patient.

Steve G.
Oldsmar, Florida

7.5% of my tasks error out these days. Many instantly with the lc points. Especially when the server runs dry they all end up bad as they get cycled to a bunch of users.