If you are not using a custom CUDA extension, which might create this illegal memory access, then it’s a bug and we need to look into it and fix it.
Thanks for the debugging so far and please let us know, if we can assist somehow.