Computation finished,... Output file absent GPU OpenCL tasks LATeah0010L

You will probably find more enlightenment for this type of problem in reviewing the stderr returned by the task than by observing the message log.

For example this can be found for one of your tasks here.

I'm copying from that task stderr to here the lines which seem most particular to your failure

<message> The remote adapter is not compatible. (0x3c) - exit code 60 (0x3c) </message>

and later

% Filling array of photon pairs
Error in OpenCL context: CL_MEM_OBJECT_ALLOCATION_FAILURE error executing CL_COMMAND_WRITE_BUFFER on GeForce GT 640 (Device 0).

Error during OpenCL bloc_info host->device transfer - qsort (error: -4)
Error in OpenCL context: CL_MEM_OBJECT_ALLOCATION_FAILURE error executing CL_COMMAND_NDRANGE_KERNEL on GeForce GT 640 (Device 0).

ERROR: /home/bema/fermilat/src/bridge_fft_clfft.c:867: Clear fft_vec failed. status=-4
ERROR: opencl_ts_2_phase_diff_sorted() returned with error 0
11:50:36 (19684): [CRITICAL]: ERROR: MAIN() returned with error '-4'
FPU status flags: PRECISION
11:50:48 (19684): [normal]: done. calling boinc_finish(60).

Sadly I'm not the one to diagnose what is wrong, but perhaps someone else will come along who can.  One possibility is that a GT 640 just cannot run these tasks.

I'm assuming I am having similar results but with slightly different hardware.  Here is my stderr for one WU:

<core_client_version>7.6.33</core_client_version>
<![CDATA[
<message>
(unknown error) - exit code -1073740940 (0xc0000374)
</message>
<stderr_txt>
08:37:17 (9196): [normal]: This Einstein@home App was built at: Feb 15 2017 09:23:49

08:37:17 (9196): [normal]: Start of BOINC application 'projects/einstein.phys.uwm.edu/hsgamma_FGRPB1G_1.20_windows_x86_64__FGRPopencl1K-nvidia.exe'.
08:37:17 (9196): [debug]: 1.1e+016 fp, 3.7e+009 fp/s, 2804377 s, 778h59m37s39
08:37:17 (9196): [normal]: % CPU usage: 1.000000, GPU usage: 1.000000
command line: projects/einstein.phys.uwm.edu/hsgamma_FGRPB1G_1.20_windows_x86_64__FGRPopencl1K-nvidia.exe --inputfile ../../projects/einstein.phys.uwm.edu/LATeah0035L.dat --alpha 4.42281478648 --delta -0.0345027837249 --skyRadius 2.152570e-06 --ldiBins 15 --f0start 868.0 --f0Band 8.0 --firstSkyPoint 0 --numSkyPoints 1 --f1dot -1e-13 --f1dotBand 1e-13 --df1dot 3.344368011e-15 --ephemdir ..\..\projects\einstein.phys.uwm.edu\JPLEPH --Tcoh 2097152.0 --toplist 10 --cohFollow 10 --numCells 1 --useWeights 1 --Srefinement 1 --CohSkyRef 1 --cohfullskybox 1 --mmfu 0.1 --reftime 56100 --model 0 --f0orbit 0.005 --mismatch 0.1 --demodbinary 1 --BinaryPointFile ../../projects/einstein.phys.uwm.edu/templates_LATeah0035L_0876_1847360.dat --debug 1 --device 0 -o LATeah0035L_876.0_0_0.0_1847360_0_0.out
output files: 'LATeah0035L_876.0_0_0.0_1847360_0_0.out' '../../projects/einstein.phys.uwm.edu/LATeah0035L_876.0_0_0.0_1847360_0_0' 'LATeah0035L_876.0_0_0.0_1847360_0_0.out.cohfu' '../../projects/einstein.phys.uwm.edu/LATeah0035L_876.0_0_0.0_1847360_0_1'
08:37:17 (9196): [debug]: Flags: X64 SSE SSE2 GNUC X86 GNUX86
08:37:17 (9196): [debug]: Set up communication with graphics process.

</stderr_txt>
]]>

I have an NVIDIA NVS 5400M with the latest drivers 1GB, and an Intel HD Graphics 4000.  Just checking to see if I am doing something else wrong, or if I need to wait for a patch.

Bear with me, I'm a noob with BOINC; I'm not sure what all information is pertinent, but I can get it if needed.

Gary,

Thanks for the help!  I'm not sure I get everything you've explained, but I'll read through it a few more times and see if I have any questions.

In the meantime, I think I can fill you in on a few of your questions.  I am working on the computer while running Einstein/BOINC in the background.  Occasionally, I may snooze the GPU and/or CPU if I am running a program that needs more resources, or if I can't deal with the lag.

Yes, I noticed that one WU happened to crunch numbers for a period of time, and when I checked on it later in the morning it has a computation error, as well as the rest of the GPU WUs that I had in the queue.

The Intel GPU is used for the laptop display.  The Nvidia GPU is used for an external monitor.  So, when I an processing with the GPUs, both displays are typically on.  I think when the WUs we are talking about were processed when both displays were on, so I doubt the computation error occurred when I activated the display to be run by the Nvidia GPU (for example).

This brings up another problem that I have with the GPUs.  If I have my laptop in the docking station (and connected to the external monitor), the GPUs are not identified when I start up BOINC.  However, if I have BOINC closed, open up the Nvidia control panel, and disable the Nvidia GPU from displaying to the external monitor, then BOINC will recognize the GPUs when I start it up.  After BOINC starts, then I turn on the external display, and life moves on.  I am also running Seti@home, and it crunches a lot of WUs on both GPUs with no problems.

Hi,

I searched a bit for the error code of your tasks (0xc0000374) which is a Microsoft errorcode for Heap corruption. Looking through other forum reports it seems that some application on the computer produces this heap corruption and the Einstein@Home app suffers from that. In one case it was a Logitech Gaming Software that produced the Heap corruption but didn't crash by itself.

I would suggest to think about what program you updated or installed prior to recognizing the error. Or boot in Clean Mode and see if the app starts. It could also help to remove the Nvidia Driver (using a driver cleaner tool) and install a fresh copy because it seems the app can't enumerate the OpenCL devices which is done by querying the driver (but that doesn't mean the driver is the source of the eap corruption).

I've got a similar problem. Some project apps always fail to find the output file at 100% completion. Here are the last view lines from task 671324524:

% Following up candidate number: 10
% Refining in S
% Following-up in P
% Writing follow-up output file.
FPU status flags:  PRECISION
00:11:13 (18052): [normal]: done. calling boinc_finish(0).
00:11:13 (18052): called boinc_finish

</stderr_txt>
<message>
upload failure: <file_xfer_error>
  <file_name>LATeah0037L_1132.0_0_0.0_5794335_1_0</file_name>
  <error_code>-161 (not found)</error_code>
</file_xfer_error>
<file_xfer_error>
  <file_name>LATeah0037L_1132.0_0_0.0_5794335_1_1</file_name>
  <error_code>-161 (not found)</error_code>
</file_xfer_error>

</message>
]]>

I debugged the problem to the point where boinc_finish was called. It tries to move the file back to the project directory, but my slot dir is a symbolic link to another drive. So, the move operation fails because they forgot to set a special flag to move files from one drive to another drive. I created a pull request for this in the past and they merged it into the master branch:

https://github.com/BOINC/boinc/pull/1449

But the problem with these BOINC project apps is that they statically link a relatively outdated BOINC-API library where this fix wasn't present.

So now, I have a request to the project owners: Please recompile your project apps with the newest BOINC-API library!