08-27-2020, 11:06 PM
I'm pretty sure it's a very nasty driver bug. The same code works with all the other devices and drivers etc.
You might be able to work around it with different driver versions. but it's actually quite dangerous and probably nobody can guarantee that it works with all different attack types and hash types (and other parameters, masks, dicts etc).
It seems to be a very dangerous bug of the driver. not of hashcat
hashcat already tries to detect errors with the self-tests, but of course it can't do intensive testing on each and every run and therefore not all problems could be catch all the time.
I don't think this can be fixed with an easy update/change to hashcat... I think only a driver update, a fix of the GPU driver would resolve the main problem, unfortunately.
You might be able to work around it with different driver versions. but it's actually quite dangerous and probably nobody can guarantee that it works with all different attack types and hash types (and other parameters, masks, dicts etc).
It seems to be a very dangerous bug of the driver. not of hashcat
hashcat already tries to detect errors with the self-tests, but of course it can't do intensive testing on each and every run and therefore not all problems could be catch all the time.
I don't think this can be fixed with an easy update/change to hashcat... I think only a driver update, a fix of the GPU driver would resolve the main problem, unfortunately.