After four hours the task is 2.1 per cent though, giving a run-time estimate of 189 hours or about 8 days.

Before mine quit (on my pipsqueak Windows 10), it predicted a little over 10 days to complete. It made it about 3 1/2 minutes.

Computer 1512658

CPU type 	GenuineIntel
11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz [Family 6 Model 140 Stepping 1]
Number of processors 	8
Operating System 	Microsoft Windows 10
Core x64 Edition, (10.00.19045.00)
BOINC version 	7.20.2
Memory 	15.64 GB
Cache 	256 KB

---

Messages back from Sarah at CPDN and the Researcher. There was an issue with uploading some of the files to the server and Sarah wonders if there is a single ancil file. I don't know what proportion of the batch that might effect. but both Donghyun, the researcher and Sarah will keep an eye on it. If that is the issue, the affected tasks may get resent but that is my extrapolating from their messages rather than a statement of fact.

If you have problems with tasks please do not send private messages to me or other moderators. If there is not a good reason for a private message rather than a post on the boards that everyone can see, I will just delete.

Another 3 east Asia task bit the dust after 2 minutes or less.
I'm running Win 11, I5 (6 core), with 8GB of memory of which more than 4GB is available.

Regards,
DadX

Lots of computation errors on my end. All 8-9 of them failed. One lasted about 10 hours, but the rest lasted just a few minutes. Oh well. This is what the moderators expected would happen. Hope things can get fixed up soon. Looks like a very worthwhile project.

I just noticed that the due date is a year from now. Yikes. It will take years to get these bad tasks flushed out of the system.

I tried to run three of these on my pipsqueak Windows 10 machine with 16 GBytes of RAM.
Computer 1512658

All mine failed at a little over 3 minutes wall-clock time; about 3 minutes of CPU time.

All mine died from segmentation violation. So did all the others with the same work units.

---