Your link is not available and yields a 404.
I don’t know which custom kernels you are using, but since the illegal memory access seems to be size-dependent, I guess some int32/int64 indexing might fail.
You could run the code via cuda-gdb and create an issue in the corresponding repository, where the kernel is provided.