5pot,
Yes it was marked Valid.

Result Name: BETA_ X0900060941203200511301452_ 0--

<core_client_version>6.12.34</core_client_version>
<![CDATA[
<stderr_txt>
Commandline: projects/www.worldcommunitygrid.org/wcg_beta3_img_6.44_windows_intelx86__cuda_opencl X0900060941203200511301452.jp2 --device 0
Boinc requested NVIDIA gpu device number 0
Found compute platform NVIDIA Corporation
Selecting this platform
CL_DEVICE_NAME: GeForce GTX 680
CL_DEVICE_VENDOR: NVIDIA Corporation
CL_DEVICE_VERSION: 301.25
CL_DEVICE_MAX_COMPUTE_UNITS: 
CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: 3
CL_DEVICE_MAX_WORK_ITEM_SIZES: 1024 / 1024 / 64
CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
CL_DEVICE_MAX_CLOCK_FREQUENCY: 705 MHz
CL_DEVICE_ADDRESS_BITS: 32
CL_DEVICE_MAX_MEM_ALLOC_SIZE: 512 MByte
CL_DEVICE_GLOBAL_MEM_SIZE: 2048 MByte
CL_DEVICE_ERROR_CORRECTION_SUPPORT: no
CL_DEVICE_LOCAL_MEM_TYPE: local
CL_DEVICE_LOCAL_MEM_SIZE: 48 KByte
CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE: 64 KByte
CL_DEVICE_QUEUE_PROPERTIES: CL_QUEUE_OUT_OF_ORDER_EXEC_MODE_ENABLE
CL_DEVICE_QUEUE_PROPERTIES: CL_QUEUE_PROFILING_ENABLE
CL_DEVICE_EXTENSIONS:
cl_khr_byte_addressable_store
cl_khr_icd
cl_khr_gl_sharing
cl_nv_d3d9_sharing
cl_nv_d3d10_sharing
cl_khr_d3d10_sharing
cl_nv_d3d11_sharing
cl_nv_compiler_options
cl_nv_device_attribute_query
cl_nv_pragma_unroll
cl_khr_global_int32_base_atomics
cl_khr_global_int32_extended_atomics
cl_khr_local_int32_base_atomics
cl_khr_local_int32_extended_atomics
cl_khr_fp64
CL_DEVICE_COMPUTE_CAPABILITY_NV: 3.0
CL_DEVICE_REGISTERS_PER_BLOCK_NV: 65536
CL_DEVICE_WARP_SIZE_NV: 32
CL_DEVICE_GPU_OVERLAP_NV: CL_TRUE
CL_DEVICE_KERNEL_EXEC_TIMEOUT_NV: CL_TRUE
CL_DEVICE_INTEGRATED_MEMORY_NV: CL_FALSE
Estimated kernel execution time = 0.41940 [sec]
Starting analysis of ../../projects/www.worldcommunitygrid.org/BETA_X0900060941203200511301452_X0900060941203200511301452.jp2...
Extracting GLCM features...
Total kernel time: 150.639053 (1026 kernel executions)
Total memory transfer time: 18.478487
Average kernel time: 0.146822
Min kernel time: 0.122454 (dx=25 dy=5 sample_dist=24 )
Max kernel time: 0.350555 dx=8 dy=7 sample_dist=10
Total time for ../../projects/www.worldcommunitygrid.org/BETA_X0900060941203200511301452_X0900060941203200511301452.jp2: 278 seconds
Finished Image #0, pctComplete = 1.000000
CPU time used = 170.633894
05:01:06 (2088): called boinc_finish

</stderr_txt>
]]>

Tomas T

BOINC 7.0.25
NVIDIA GeForce GTX 560 (1023MB) driver: 301.24 -> 50 valids and 3 pending
Alongside 8 cores 100% busy with CPU tasks.
During most of the tasks on the GPU also a Folding@Home task was running. No negative influence on these BETA's

Elapsed times between 5:17 and 10:31 and CPU times inversely proportional between 1:25 and 5:09.

Remark: Most of the result logs look like:

<core_client_version>7.0.25</core_client_version>
<![CDATA[
<stderr_txt>

</stderr_txt>
]]>

and only a few give the whole information.
But when looking to the wingmen results, I can see their full info.

2nd remark: For the multi-project crunchers, one has to know that running WCG GPU tasks will result in a high Recent Estimated Credit (REC - in BOINC 7 used for work fetch policy), could lead to only WCG GPU-tasks and no CPU-tasks for WCG, but only CPU-tasks of the other projects.

3rd remark: The fast running GPU-tasks lead to high runtime estimates for the WCG CPU-tasks. E.g. C4CW normally has an estimate of 1h50min, after running the GPU's the estimate is 13 hours.

Noticed that the amount of credits for each WU dropped during this run from about 125 each at the start to about 75 each at the end.

Yes I noticed that also , with the exception of the first one I ran
122.5 / 44.2
and near the end...
88.7 / 35.3

I think these are the ones I ran with a 680 as wingman.

BOINC 7.0.25
2 x GTX560
Windows 7 64 bit SP1
i7-2600k@3.40GHz
285.62 driver
RAM 10 GB

Got 53 WUs, 48 valid and 5 with error:

Error: .\GlcmBuilder.cpp:837 Invalid command queue ---- x1
Error: .\GlcmBuilder.cpp:674 Invalid command queue ---- x2
Error: .\GlcmBuilder.cpp:305 Out of resources ------------ x2