Hi vigo & ssavec
I have this fixed in internal builds; the problem was indeed that the installed cl runtime did not support v1.2, and we did not handle that case gracefully (at all).
The easiest solution was to implement logic to fall back to CPU processing if an insufficient cl runtime is detected. This does imply that heterogeneous computing is disabled on runtimes < v1.2, but it does recover gracefully. We are considering releasing a bugfix release for v6.0.4, but I don't have a date I can commit too.
Kent