Folding Forum

It looks like a widespread problem - same issue here

Posting Log in case it is of some use to solve the problem

[20:33:15] Preparing to commence simulation
[20:33:15] - Looking at optimizations...
[20:33:15] - Not checking prior termination.
[20:33:15] - Expanded 201910 -> 412320 (decompressed 204.2 percent)
[20:33:15] Called DecompressByteArray: compressed_data_size=201910 data_size=412320, decompressed_data_size=412320 diff=0
[20:33:15] - Digital signature verified
[20:33:15]
[20:33:15] Project: 10412 (Run 11938, Clone 2, Gen 0)
[20:33:15]
[20:33:15] Assembly optimizations on if available.
[20:33:15] Entering M.D.
[20:41:43] CoreStatus = C0000417 (-1073740777)
[20:41:43] Client-core communications error: ERROR 0xc0000417
[20:41:43] This is a sign of more serious problems, shutting down.

Welcome to the foldingforum, hogann

No, I doesn't look like the same problem to me. The previous error was 0x79 and yours is 0xc0000417. The previous problem was with project 11270 and yours is with project 10412. That doesn't prove it has a different cause, but there's a pretty good chance it's different. I'm going to separate your post into a new topic.

Didn't see this forum - thanks for the assist.

Just in case it helps it was at the 30% mark

[20:31:21] Completed 2000001 out of 6666667 steps (30%)
[20:33:11] mdrun returned 3
[20:33:11] Gromacs detected an invalid checkpoint. Restarting...
[20:33:12] Folding@home Core Shutdown: UNKNOWN_ERROR
[20:33:14] CoreStatus = 62 (98)
[20:33:14] + Restarting core (settings changed)

hogann wrote:[20:33:11] Gromacs detected an invalid checkpoint. Restarting...

This message can mean any one of several things.
A) You've been browsing around in FAH's work files and inadvertently changed something
B) Your antivirus software has decided that one of FAH's work files was dangerous and it changed something
C) You have a hardware problem that has corrupted one of FAH's files.

FAH's normal response to finding something changed is to abort the processing. (Corrupted scientific data is bad for research.)

You'd probably know if it was A or C.

B can happen without your knowledge although you can probably find a record of it in the AV program's log if you look for it. The simplest way to avoid this problem is to exclude the FAH work directory from virus scans.