Folding Forum

At the "Entering M.D." stage just after downloading, a Windows "Visual Fortran run-time error" box appeared with a short list of data as similarly reported in this Forum once before:

viewtopic.php?f=4&t=904&p=7514&hilit=visual+fortran+error#p7514

Closing the error box produced an F@H error:

Folding@home has run into a serious error running the core, and will shut down.

This was previously attributed to a malformed WU.

During the next hour, I repeatedly deleted the old files and tried to download a new WU but could only get another P4611 (R7, C173, G29) that immediately generated the same errors.

So I gave up, shut down the client and about eight hours later was finally able to download a new (and so far) problem-free WU.

Any clue as to what was going on?

Some installations generate errors and you need to fix something. Some WUs have inherent errors and there's nothing that you can do about it. WU's with errors should be rare whereas installation problems are usually quite frequent. A single WU that generates errors is probably a bad WU, but only a Moderator can tell you for sure.

Most people do not have Visual Fortran, so if they happen to get the same error, the messages would be different and we would have a better chance of explaining what the messages mean.

Thanks for the input, but I'm really curious about the difficulty of downloading a different WU.

That is caused by the PG AS software. Though they (did or tried to) update it just lately.
I don't think that issue has been fixed, or that they even care about it.

When I was running a normal cpu client, to test out the protomol core, I had that problem.
Along with get assigned continuously to a work service that was down.
Only thing that helped me, was removing my passkey, and restarting the client after deleting everything.

RAH wrote:Along with get assigned continuously to a work service that was down.
Only thing that helped me, was removing my passkey, and restarting the client after deleting everything.

Removing the passkey has absolutely nothing to do with being assigned to a different work server. Changing parameter settings or reinstalling sometimes works.

Yesterday there was a server that was being repeatedly assigned but no work was being downloaded. That problem has been fixed, so that's more likely the answer to your issue.

I've been running a GPU client and a CPU client on my PC without issue for many months. Now I can't get the CPU client to run. No overclocking, Windows 7 OS, uninstalled and reinstalled several times, waited overnight to run a new WU.
[13:09:50] Loaded queue successfully.
[13:09:50] Initialization complete
[13:09:50]
[13:09:50] + Processing work unit
[13:09:50] Core required: FahCore_82.exe
[13:09:50] Core found.
[13:09:50] Working on queue slot 00 [August 10 13:09:50 UTC]
[13:09:50] + Working ...
[13:09:50]
[13:09:50] *------------------------------*
[13:09:50] Folding@Home PMD Core
[13:09:50] Version 1.03 (September 7, 2005)
[13:09:50]
[13:09:50] Preparing to commence simulation
[13:09:50] - Ensuring status. Please wait.
[13:10:07] - Looking at optimizations...
[13:10:07] - Working with standard loops on this execution.
[13:10:07] Examination of work files indicates 8 consecutive improper terminations of core.
[13:10:07] - Expanded 12368 -> 75470 (decompressed 610.2 percent)
[13:10:07]
[13:10:07] Project: 4611 (Run 7, Clone 173, Gen 29)
[13:10:07]
[13:10:07] Entering M.D.
[13:11:38] CoreStatus = 40 (64)
[13:11:38] Client-core communications error: ERROR 0x40
[13:11:38] This is a sign of more serious problems, shutting down.

Caocao8888,

Try changing the -configonly options to "normal" for WU size, that should get you to a different project and this server. You could also add turn-on advmethods; either through the -advmethods flag or through the -configonly.

Problem solved. It turned out to be an OS compatibility issue, not a client, WU, or server issue. The OS wizard changed and saved settings automatically, and the CPU client is now up and running.

I got this WU earlier today and had the same issue. It was grabbed by a laptop that has been rock solid folding-wise until this one. Deleting the work folder and queue.dat allowed me to grab a different WU which is progressing normally.

Some people have been able to return partial results, but they are all immediate EUE.

I marked the WU as bad.

I got it again today. Unsurprisingly, it immediately failed with the same error.

Just had the same problem. deleted work folder & que dat file and got a good work unit .
Thanks for the tip Zagen30.

On which WU ? (if it's not the same as the one mentioned in the thread, it might be useful to report it so that we could remove it)

it is the same one. 4611( r7 c173 g29) Visual Fortran error.with all the people having problems with it I'm suprized it has not been removed or corrected yet.