The illegal memory access was most likely triggered before the copy kernel, so the blocking launch is apparently not working.
Could you post an executable code snippet, which would reproduce this issue?