Message boards : Number crunching : All ACEMD3 tasks failing on W10 computer
Author | Message |
---|---|
I've not been able to finish any "New version of ACEMD" (ACEMD3) task on my Windows 10 computer so far. | |
ID: 52848 | Rating: 0 | rate: / Reply Quote | |
Do you overclock this GTX 1050Ti under Windows 10? | |
ID: 52849 | Rating: 0 | rate: / Reply Quote | |
Do you overclock this GTX 1050Ti under Windows 10? +1 With the Wrapper, it seems the Work Unit errors are not being passed back to the Exit Status, we are just seeing the Wrapper error (195 (0xc3) EXIT_CHILD_FAILED) The two v2.08 work units both report # Engine failed: Error invoking kernel: CUDA_ERROR_LAUNCH_FAILED (719) The CUDA Toolkit defines this as an exception referencing shared memory, invalid device pointer or system specific issue as possible causes. https://docs.nvidia.com/cuda/cuda-driver-api/group__CUDA__TYPES.html The v2.06 work units don't offer an obvious error. As both v2.06 and v2.08 work units fail, perhaps a once over on the system health. The work units are not failing immediately, there appears to be a stability issue (hardware or software) If your overclocking is ok, how about the other usual suspects such as power supply, memory etc? Looking at Win10 specifically, are there any scheduled tasks causing an issue? Is power management set to full (no sleep)? Any clues in the Windows System and Application event log? Windows Update issues, are you on Win10 1903, or has it recently updated to 1903? I found multiple updates and auto reboots long after applying 1903. Is Windows Defender / AV protection playing nicely with ACEMD3 tasks? | |
ID: 52851 | Rating: 0 | rate: / Reply Quote | |
Thank you very much for your kind advices. Do you overclock this GTX 1050Ti under Windows 10? I left playing with overclocking a long time ago. When something fails, not overclocking restricts looking for causes to "other reasons"... Is Windows Defender / AV protection playing nicely with ACEMD3 tasks? Definitively not. I set exceptions in AV to acemd3 and wrapper processes, and it did the trick! Probably AV monitoring was interfering with processes at some critical moments... After that, this system has successfully finished its first two ACEMD3 WUs. AV exceptions: New version of ACEMD v2.08 (cuda 101) Result ID: 21447085 New version of ACEMD v2.06 (cuda 100) Result ID: 21447098 | |
ID: 52856 | Rating: 0 | rate: / Reply Quote | |
I set exceptions in AV to acemd3 and wrapper processes, and it did the trick! Thanks for the feedback. Great to see you resolved the issue. When AV is blocking Work Units for ACEMD3, it is harder to spot as the Wrapper does not pass the Work Unit error to the Exit Status. | |
ID: 52858 | Rating: 0 | rate: / Reply Quote | |
on the other hand, since it's now obvious that there seems to be a problem between AVAST and the acemd3 app, the devs at GPUGRID should take care of this, right? | |
ID: 52862 | Rating: 0 | rate: / Reply Quote | |
Message boards : Number crunching : All ACEMD3 tasks failing on W10 computer