We would need somebody to test and troubleshoot the hashcat "versions"/changes/commits on github to identify the problem. that is what I was trying to say.
If we know it can be fixed by using the volatile again, we can be sure what the problem is (driver issue) and how to fix it.
The problem also is that it's not currently reproducible by a dev... we would probably need to test the same setup/system with same GPU etc (windows? adrenalin driver? only 290x ?). The best thing would be if an affected user would be able to test the git changes (like mentioned here: https://hashcat.net/forum/thread-8605-po...l#pid45813), i.e. carefully compile the individual versions/changes one-by-one and see when it started to fail (we already pinpointed it a little bit with the "beta version" to git commit mapping)
If we know it can be fixed by using the volatile again, we can be sure what the problem is (driver issue) and how to fix it.
The problem also is that it's not currently reproducible by a dev... we would probably need to test the same setup/system with same GPU etc (windows? adrenalin driver? only 290x ?). The best thing would be if an affected user would be able to test the git changes (like mentioned here: https://hashcat.net/forum/thread-8605-po...l#pid45813), i.e. carefully compile the individual versions/changes one-by-one and see when it started to fail (we already pinpointed it a little bit with the "beta version" to git commit mapping)