Hello. I'm getting "computation error" after each task runs for about 1 second. I'm running Windows with the latest BOINC client. Don't have a problem with any other projects. Is there somewhere I can check a more specific error, or anything that has worked for others to prevent this issue? I see a lot of past postings about "out of memory" but the only error I get is the "computation error" on the task status after about 1 second of running.

same problem here, but only on 1 box.

Win 7 x64. has been running fine for months, now it messes up.
other projects on same machine work just fine.

all other machines Win and Linux are running fine.

Try the instructions from user Snow Crash in this link:

http://vdwnumbers.org/forum_thread.php?id=60&postid=320#320

It worked for me on Win10 x64.

Any chance of a resolution that doesn't involve any intervention? I don't intend to micro-manage tasks.

Well, I also tried the advice at the top just to see if it would work, and unfortunately even with all other tasks suspended and a fresh restart it still fails after 1-3 seconds. Are there other possible reasons?

Try the instructions from user Snow Crash in this link:

http://vdwnumbers.org/forum_thread.php?id=60&postid=320#320

It worked for me on Win10 x64.

I've seen this happen on one of my PCs if I happen to already be running WUs for another memory intensive project. If I suspend all tasks, reboot the PC (yes the reboot is necessary when I've seen this) and then let VDW start first I can then reactivate the WU from the other project also and everything runs fine after that.

It's almost like the prioritization gets wonky with the internal processes and VDW gets locked out - or maybe it's that VDW requires some level / amount of memory to be locked (as opposed to dynamically available) and if that's not immediately available crashes :shrug:

Try the instructions from user Snow Crash in this link:

http://vdwnumbers.org/forum_thread.php?id=60&postid=320#320

It worked for me on Win10 x64.

From Snow Crash/other thread:

I've seen this happen on one of my PCs if I happen to already be running WUs for another memory intensive project. If I suspend all tasks, reboot the PC (yes the reboot is necessary when I've seen this) and then let VDW start first I can then reactivate the WU from the other project also and everything runs fine after that.

It's almost like the prioritization gets wonky with the internal processes and VDW gets locked out - or maybe it's that VDW requires some level / amount of memory to be locked (as opposed to dynamically available) and if that's not immediately available crashes :shrug:

(not sure why I can't post on that thread... it shows me as not logged in, even though it's the next tab .. Internet Explorer 11 and FireFox!)

I'm also on Windows 10 x64 and rebooting didn't help.. I haven't had a good result since July. (although, I haven't been running it in a while.)

I just tried a suspend all, reboot, start this project first and am only getting errors now.

After all the bad WU's were uploaded now I am being told I can only download 1 WU per day. Was running ok for awhile.
____________

I'm also on Windows 10 x64 and rebooting didn't help.. I haven't had a good result since July. (although, I haven't been running it in a while.)

Brian, I can't post to that thread either and it seems that everyone that said the SN fix worked (on that thread) have now left the project. I'm on Win7-64 and previously the WUs have been working. Now they're also almost all failing even on a machine with large memory and disk resources (and limits checked and rechecked). PC above (who your reply is to) also seems to have dropped the project. Trying a couple new things and will report back if they work.

Hi Beyond,

I have done some troubleshooting here as well, including ETW (event tracing for windows) which shows that the 1.8 Gig or so of memory is reserved/allocated just fine. Then milliseconds later, without any other attempts to allocate memory, the app crashes with an "out of memory" error...Linux works fine btw.

Looks like a programming error to me (several docs on the web showing how to debug/fix this, but of course only admin can do that). Is the admin testing/troubleshooting/debugging this at all?