any idea why all tasks downloaded within the last few hours fail immediately?

No idea, but it's the same for others.

yes, I had checked that before I wrote my posting above.

I wonder whether the GPUGRID team has realized this problem yet.

same here all WU's with the same Error Code

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -44 (0xffffffd4)</message>
]]>

it seems that the licence for Windows 10 (and maybe for Windows 7/8, too) has expired.

Why do I think so? My Windows XP host downloaded a new tasks a few minutes ago, and it works well.

any idea why all tasks downloaded within the last few hours fail immediately?

No idea, but it's the same for others.

yes, I had checked that before I wrote my posting above.

I wonder whether the GPUGRID team has realized this problem yet.

Things left to themselves tend to go from bad to worse.

Several more tasks with computation errors, but nothing definite about just what kind of error.

At least they didn't use much CPU or GPU time.

http://www.gpugrid.net/result.php?resultid=21242466

http://www.gpugrid.net/result.php?resultid=21242065

http://www.gpugrid.net/result.php?resultid=21241863

http://www.gpugrid.net/result.php?resultid=21233480

And so on.

Could more diagnostics be added to v9.22 (cuda80) to show what caused this error, if you can't fix it instead? This appears for both short and long runs.

Same here...

I actually got one to finish successfully:

http://www.gpugrid.net/workunit.php?wuid=16709219


I changed the date to before the license expired, right after the WU started crunching and before it crashes, and then change it back. It's actually tricky to do, because boinc acts strangely when the date is moved back. My two other attempts failed, so I had enough of this.

BTW, the video card that I used was a gtx 980 ti, not the rtx 2080 ti.

I actually got one to finish successfully:

http://www.gpugrid.net/workunit.php?wuid=16709219

I changed the date to before the license expired, right after the WU started crunching and before it crashes, and then change it back. It's actually tricky to do, because boinc acts strangely when the date is moved back.

so it's clear that the license has expired.

Changing the date of the host can indeed be tricky, even more if also other BOINC projects are running which could be totally confused by doing this. Happened to me last time when the license expired, it all ended up in a total mess.

Let's hope that it won't take too long until there is a new acemd with a valid license.

I actually got one to finish successfully:

http://www.gpugrid.net/workunit.php?wuid=16709219

I changed the date to before the license expired, right after the WU started crunching and before it crashes, and then change it back. It's actually tricky to do, because boinc acts strangely when the date is moved back.

so it's clear that the license has expired.

Changing the date of the host can indeed be tricky, even more if also other BOINC projects are running which could be totally confused by doing this. Happened to me last time when the license expired, it all ended up in a total mess.

Let's hope that it won't take too long until there is a new acemd with a valid license.

I thought one of the reasons for the new app was to not need the license that keeps expiring. Plus Turing support in a BOINC wrapper to separate the science part from the BOINC part.

They are not using the new app yet, the reason the app expired is because it's still the old app.

They are not using the new app yet, the reason the app expired is because it's still the old app.

And?

I was replying to this part
"new acemd with a valid license."

The new app won't need a license from what I recall.

I've seen some mentions of tasks still completing properly on some rather old versions of Windows, such as Windows XP. Could some people with at least one computer with such a version give more details?

Perhaps the older versions don't include an expiration check, and therefore have to assume that it is not expired.

the "older versions" also include an expiration check.

However, for XP, a differnt acemd.exe is used (running with CUDA 65), the license for which seems to expire at a later date. No idea at what date exactly, it could be tomorrow, or in a week, or next month ...

I´m using Win XP 64 and havind just errors aswell.

No, you are using Windows 7 x64.

Stderr output
<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -44 (0xffffffd4)</message>
]]>

name e18s22_e7s95p0f111-PABLO_V4_UCB_p27_sj403_no_salt_IDP-0-2-RND0646
application Long runs (8-12 hours on fastest card)
created 8 Aug 2019 | 21:02:41 UTC
minimum quorum 1
initial replication 1
max # of error/total/success tasks 7, 10, 6
errors Too many errors (may have bug)

100% failure rate for the last three days.

Hello everyone,
Please read the post in "news" about "expired licence".
It is not at our side, but at server side.

Admin know it already two days.

No, you are using Windows 7 x64.

You are right, my bad. But I was having errors with the new drivers. Then I rolled back to 378.94 driver and it´s running fine now.

http://www.gpugrid.net/show_host_detail.php?hostid=413063

http://www.gpugrid.net/workunit.php?wuid=16717273

Hello everyone,
Please read the post in "news" about "expired licence".
It is not at our side, but at server side.

Admin know it already two days.

That's fixed now. But the errors continue, 2 seconds into a Pablo unit and poof they error out. I turned off the long run units and it seems there aren't any short run units to do for the gpu's.

But the errors continue, 2 seconds into a Pablo unit and poof they error out

mikey, the tasks with errors were run on a Turing based card (GTX1660ti). These GPUs are not currently supported by the ACEMD2 app.
Admins are working on ACEMD3 app which will support Turing based GPUs. Hopefully this will be released soon.
There is currently no short tasks in the queue.