The vast majority of the units my computer completes have been reported as 'Error While Computing'. This has been going on for a few months. For a while a few weeks ago, the units seemed to be much smaller and only take a few hours to complete. These seemed to be validated much more often than the large units that take a couple days of crunching.

Is there a larger reason for this or is it a problem with my machine?

The acemd4 and python tasks are still being debugged by the admin developers.

So lots of errors still and nothing wrong with your host.

The acemd3 tasks have been stable for over a year. So they should validate on everyone's hardware.

Only investigate your hardware if the errors are with this type of task.

I think the only tasks I've gotten have been ACEMD3. Some validate, many show an error while computing. What could cause this on my end??

What could cause this on my end??

The acemd3 tasks have been stable for over a year.

Just to piggyback on this thread with something else,,,,

The run time vs cpu time, over the course of working ACMED 3 (2 days plus run time, still far away from deadline) I am seeing a 2 hour time difference between the two. I have never seen that on my other projects. Everything is running ok, but is this normal? The two hours?

Just to piggyback on this thread with something else,,,,

The run time vs cpu time, over the course of working ACMED 3 (2 days plus run time, still far away from deadline) I am seeing a 2 hour time difference between the two. I have never seen that on my other projects. Everything is running ok, but is this normal? The two hours?

I think the only tasks I've gotten have been ACEMD3. Some validate, many show an error while computing. What could cause this on my end??

I think the only tasks I've gotten have been ACEMD3. Some validate, many show an error while computing. What could cause this on my end??

Looking at your error:

08:26:39 (15796): wrapper: running bin/acemd3.exe (--boinc --device 0)
Detected memory leaks!

You are having issues with either a hot gpu, hot cpu or flaky memory.

These are the typical issues that cause memory errors.

01:56:42 (4340): wrapper: running bin/acemd3.exe (--boinc --device 0)
ERROR: C:\Users\admin\miniconda3\conda-bld\acemd3_1632736748005\work\src\mdsim\trajectory.cpp line 103: Cannot open XTC file

Thanks for the correction. I wasn't aware that memory leaks are a common problem on Windows hosts.

Ok, since Keith Myers quoted me, are you saying I have a different problem on my end or there is no problem on my end?

You had a problem with the task configuration. Server issue.

Not your hardware issue after all.

Thanks. Incidentally, I'm getting 'error while computing' issues on Rosetta@Home units, also. . .

Then something wrong with your Python environment I guess. Rosetta is doing Python tasks also I believe.

But still nothing wrong on your end. Up to the project to package all the Python bits necessary to crunch the task and send it to you properly.

ERROR: C:\Users\admin\miniconda3\conda-bld\acemd3_1632736748005\work\src\mdsim\context.cpp line 318: Cannot use a restart file on a different device!

http://www.gpugrid.net/result.php?resultid=32884878

ACMED 3 task
195 (0xc3) EXIT_CHILD_FAILED

ERROR: C:\Users\admin\miniconda3\conda-bld\acemd3_1632736748005\work\src\mdsim\context.cpp line 318: Cannot use a restart file on a different device!

http://www.gpugrid.net/result.php?resultid=32884878

ACMED 3 task
195 (0xc3) EXIT_CHILD_FAILED

ERROR: C:\Users\admin\miniconda3\conda-bld\acemd3_1632736748005\work\src\mdsim\context.cpp line 318: Cannot use a restart file on a different device!

http://www.gpugrid.net/result.php?resultid=32884878

ACMED 3 task
195 (0xc3) EXIT_CHILD_FAILED

This is a well known issue. You can’t restart the task on a different GPU. Basically can’t interrupt a running task at all.

ERROR: C:\Users\admin\miniconda3\conda-bld\acemd3_1632736748005\work\src\mdsim\context.cpp line 318: Cannot use a restart file on a different device!

http://www.gpugrid.net/result.php?resultid=32884878

ACMED 3 task
195 (0xc3) EXIT_CHILD_FAILED

This is a well known issue. You can’t restart the task on a different GPU. Basically can’t interrupt a running task at all.

I have had the same error, I suspend and shut down the client and exit via the menu at the end of my computing day. The next morning I start up again and the task resumes on the same GPU. But a half day later for full day later then it crashes.

08:01:06 (9168): wrapper (7.9.26016): starting
08:01:06 (9168): wrapper: running bin/acemd3.exe (--boinc --device 1)
Detected memory leaks!
Dumping objects ->
..\api\boinc_api.cpp(309) : {389760} normal block at 0x000001DBD2145AF0, 8 bytes long.
Data: < > 00 00 CC D3 DB 01 00 00
..\lib\diagnostics_win.cpp(417) : {388486} normal block at 0x000001DBD2175230, 1080 bytes long.
Data: <8 $ > 38 1E 00 00 CD CD CD CD 24 01 00 00 00 00 00 00
..\zip\boinc_zip.cpp(122) : {153} normal block at 0x000001DBD2150860, 260 bytes long.
Data: < > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Object dump complete.
08:37:06 (15692): wrapper (7.9.26016): starting
08:37:06 (15692): wrapper: running bin/acemd3.exe (--boinc --device 0)
ERROR: C:\Users\admin\miniconda3\conda-bld\acemd3_1632736748005\work\src\mdsim\context.cpp line 318: Cannot use a restart file on a different device!