When I googled the error I did see that it was related somehow to indexing, but I somehow doubt that is the actual problem. The code runs for most of an epoch before it crashes, and when I add checks to see what is happening with the gradients, my checks show that the gradients are becoming NaN before this error gets thrown. I suspect whatever the CUDA error is is just a symptom of the gradients/weights becoming NaN, and whatever is causing that is the actual problem.
Ah, that is interesting. I will definitely try that then. 0.4.x fixes that issue?