Finished 9, several valid, most PVal, started few more by hand and lost 3 on a test system, so will sit waiting for 10 days before No Reply is called (Upgraded from Windows 10 build 10240 to 10586 which zoothingly ** said "all your files will be left alone". What they did not say was that ProgramData does not fall in that class... fully erased. . The new BOINC install places the data dir in a private place.

** Zoot Allures

I got a resend from BETA_ HST1_ 004003_ 000065_ KC0014_ T325_ F00089_ S00005_ 0-- that errored after 3.95 hours run time.

[15:34:49] INFO: Completed step 36000 of initial simulation
Writing checkpoint at step 36330.

-------------------------------------------------------
Program projects/www.worldcommunitygrid.org/wcgrid_beta22_gromacs_7, VERSION 4.6.1
Source code file: .\src\mdlib\nsgrid.c, line: 641

Range checking error:
Explanation: During neighborsearching, we assign each particle to a grid
based on its coordinates. If your system contains collisions or parameter
errors that give particles very high velocities you might end up with some
coordinates being +-Infinity or NaN (not-a-number). Obviously, we cannot
put these on a grid, so this is usually where we detect those errors.
Make sure your system is properly energy-minimized and that the potential
energy seems reasonable before trying again.
Variable ind has value 33036. It should have been within [ 0 .. 33019 ]

Hypothesis #1 coming up. This was after I also realised that another of my machines successfully downloaded 2 of batch 3901 and didn't suffer the RSA key check fail, but 2 wingmen did for one of them (mine is _2, Valid):

BETA_ HST1_ 003901_ 000093_ AC0011_ T000_ F00078_ S00006_ 3-- Microsoft x64 Edition, (06.02.9200.00) 720 Valid 14/06/16 18:48:42 15/06/16 03:52:03 3.54 97.8 / 91.9
BETA_ HST1_ 003901_ 000093_ AC0011_ T000_ F00078_ S00006_ 2-- Microsoft Windows 10 Professional x64 Edition, (10.00.10586.00) 720 Valid 14/06/16 17:48:08 14/06/16 21:45:14 2.13 86.0 / 91.9
BETA_ HST1_ 003901_ 000093_ AC0011_ T000_ F00078_ S00006_ 1-- Microsoft Windows 10 Core x64 Edition, (10.00.10586.00) 720 Error 14/06/16 17:47:50 14/06/16 18:48:39 0.00 296.9 / 0.0
BETA_ HST1_ 003901_ 000093_ AC0011_ T000_ F00078_ S00006_ 0-- Microsoft Windows 10 Professional x64 Edition, (10.00.10586.00) 720 Error 14/06/16 17:47:39 14/06/16 17:48:01 0.00 296.9 / 0.0

Mine ran on an i5-750, Win 10 Pro, BOINC 7.6.22, but otherwise fairly similarly configured to the 4770K that had the RSA key check fail. So what differences exist that might affect BOINC? Avast Free Antivirus is running on both of them, but I wondered whether I had exactly the same configuration. No, I didn't. The i5-750 had an exclusion on the BOINC program data folder, the 4770K didn't. Hmmm.

My Avast program version is 11.2.2262 (up to date). Exclusions are entered thusly: from its home screen, Settings (gear icon), General tab, Exclusions, File paths, enter something like "C:\ProgramData\BOINC\*" without the "" (wherever your BOINC program data folder is), Enter, OK.

I've no idea whether or how a virus check on download could cause the RSA key check fail, and why only for some workunits, so this is grabbing at straws. So what about you others that have suffered the RSA key check fail? Do those machines have a scan exclusion on the BOINC program data folder? Are they running Avast? For completeness, I also ought to ask if anyone running Avast without an exclusion succeeded in downloading batch 3901?

Error after 13.7 hours

Writing checkpoint at step 83090.
SIGSEGV: segmentation violation
Stack trace (12 frames):
[0x2094e4d]
[0x20876a0]
[0x97b7ed]
[0x75a1cf]
[0x4db05b]
[0x55c684]
[0x4115ec]
[0x420770]
[0x4141a6]
[0x47ed1b]
[0x211b1cb]
[0x400469]

Exiting...

Although the host has enough available RAM.
At this time, the computation of the 5 other WUs (on the same host) is still in progress, after 15+ hours for a duration forecast or 10.21 hours.
The duration forecast is still meaningless.
Cheers,
Yves

Tonyh205 and I both have a machine with <error_code>-120 (RSA key check failed for file) and that same machine then later successfully ran other Betas. Nice to see that isn't only me.

And Tonyh205 also mentioned:
which I then rechecked the ones that errored with <error_code>-120 and found the same thing: other computers were able to run it successfully.