I've just noticed that WAH units are being sent out with deadlines that are already well past.

E.g.

Task 19776025

Name wah2_sas50_ighk_201412_13_414_010625478_0
Workunit 10625478
Created 22 Jun 2016 18:44:59 UTC
Sent 14 Jul 2016 8:38:41 UTC
Received 22 Jul 2016 8:52:52 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status 9 (0x9)
Computer ID 1131079
Report deadline 26 Jun 2017 13:58:41 UTC
Run time 379,197.56
CPU time 337,218.20
Validate state Invalid
Claimed credit 3,819.41
Granted credit 3,819.41
application version Weather At Home 2 (wah2) v8.12

No wonder I haven't been getting any credit. There have been a lot of WUs like this and they're still going out. I found one on my PC today (29th August) with a deadline of 8th August!

Please fix this.

---

France seems to be well ahead of the rest of the world in time.
It's still August 2016 in Australia, but well into 2017 in France. :)

Created 22 Jun 2016 18:44:59 UTC
Sent 14 Jul 2016 8:38:41 UTC
Received 22 Jul 2016 8:52:52 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status 9 (0x9)
Computer ID 1131079
Report deadline 26 Jun 2017 13:58:41 UTC

And the often pointed out fact, is that "deadlines" are just something that BOINC does. They're completely ignored in this project, like a lot of other BOINC code.

Of more interest is the error code:
Exit status 9 (0x9)
which is given as the reason your computer is crashing so many tasks.
I don't know what that means, but it may be related to you using a vm, which cpdn doesn't need or use.

LOL Of course, the first WU I get that doesn't have a passed deadline or other problem. Blame it on tiredness.

However, there have been a lot of problematic WUs

19838238 10400211 1131079 26 Jul 2016 7:33:17 UTC 23 Aug 2016 12:47:46 UTC Completed 808,553.82 742,117.50 9,898.90 9,898.90 Weather At Home 2 (wah2) v8.12
19776025 10625478 1131079 14 Jul 2016 8:38:41 UTC 22 Jul 2016 8:52:52 UTC Error while computing 379,197.56 337,218.20 3,819.41 3,819.41 Weather At Home 2 (wah2) v8.12
19728866 10566642 1131079 2 Jun 2016 3:43:02 UTC 2 Jun 2016 4:59:21 UTC Error while computing 414.18 398.81 0.00 --- Weather At Home 2 (wah2) v8.12
19725356 10567233 1131079 31 May 2016 5:39:35 UTC 31 May 2016 6:56:21 UTC Error while computing 446.10 433.77 0.00 --- Weather At Home 2 (wah2) v8.12
19719397 10419322 1131079 5 Jul 2016 2:51:33 UTC 14 Jul 2016 2:35:01 UTC Error while computing 478,062.65 455,612.00 3,059.47 3,059.47 Weather At Home 2 (wah2) v8.12
19709587 10605623 1131079 4 Jun 2016 4:45:00 UTC 26 Jun 2016 21:10:08 UTC Completed 931,562.63 888,822.60 18,258.20 18,258.20 Weather At Home 2 (wah2) v8.12
19625449 10541019 1131079 11 May 2016 22:38:14 UTC 28 May 2016 23:24:47 UTC Error while computing 654,318.01 622,314.00 3,819.41 3,819.41 Weather At Home 2 (wah2) v8.12
19541308 10499099 1131079 16 Apr 2016 23:25:08 UTC 9 May 2016 16:35:36 UTC Completed 824,036.48 769,570.40 9,898.90 9,898.90 Weather At Home 2 (wah2) v8.12
19511991 10481644 1131079 7 Apr 2016 3:06:14 UTC 12 Apr 2016 7:28:36 UTC Error while computing 224,026.55 210,971.70 779.66 779.66 Weather At Home 2 (wah2) v8.12
19397774 10398507 1131079 19 Mar 2016 3:13:28 UTC 6 Apr 2016 2:07:32 UTC Completed 819,100.92 762,053.80 9,898.90 9,898.90 Weather At Home 2 (wah2) v8.12
19383868 10387297 1131079 18 Mar 2016 5:38:28 UTC 18 Mar 2016 13:11:34 UTC Error while computing 430.88 298.33 0.00 --- Weather At Home 2 (wah2) v8.12
19379511 10383022 1131079 18 Mar 2016 4:26:33 UTC 18 Mar 2016 5:38:28 UTC Error while computing 284.67 246.59 0.00 --- Weather At Home 2 (wah2) v8.12
19371020 10377044 1131079 16 Mar 2016 20:51:33 UTC 16 Mar 2016 22:09:24 UTC Error while computing 435.86 423.94 0.00 --- Weather At Home 2 (wah2) v8.12
19337843 10345305 1131079 15 Mar 2016 12:09:02 UTC 15 Mar 2016 13:32:56 UTC Error while computing 514.30 416.30 0.00 --- Weather At Home 2 (wah2) v8.12
19322354 10304594 1131079 2 Mar 2016 12:22:10 UTC 2 Mar 2016 13:43:03 UTC Error while computing 396.12 362.86 0.00 --- Weather At Home 2 (wah2) v7.08
19309631 10329961 1131079 26 Feb 2016 13:56:50 UTC 1 Mar 2016 9:47:45 UTC Error while computing 154,027.16 133,150.40 1,539.60 1,539.60 Weather At Home 2 (wah2) v7.08

I don't use a VM to run BOINC, by the way. Windows 10, 64 bit, sadly. The BOINC VM is installed though, if that's what you meant. I could probably remove it, as vlhc@home has been crashing as well, so it got suspended.

---

anarchic teapot -

I looked at a few of your completed tasks (with errors) and I notice that most have them have tons of messages about being suspended. CPDN models do not like to be interrupted (suspended).

There are a couple of settings that you might want to look at. Make sure you have "Leave model in memory when interrupted" checked. Also, make sure BOINC can use the computer when you are using it for other activities (Boinc will not be suspended).

Do not shutdown BOINC, turn your computer off, re-boot, etc. unless absolutely necessary.

---

It may very well be that keeping the model in memory is the key.
I'm currently using VMWare Fusion on my Mac to run CPDN models. I often have to switch between different versions of OSX and so suspend the project every time I switch from the one where BOINC is installed. So far with no problems whatsoever.
As a side comment, I run Windows XP in Fusion.

Dave Roberts -

Off topic for the title of this thread -

I have several XP machines, some UBUNTU machines , and some Windows 10 machines.

I have found the Windows machines handle things quite well - re-boots, power failures, etc. The UBUNTU machines have an excellent chance of generating computational errors with re-boots, either manual or power failure related.

---