Hey and thx for your testing and the report.
I don't really like to discuss 2+ different problems within the same thread....
Anyway,
1. please open a trac ticket https://hashcat.net/trac/ with a set of *minimal* hccap files (for instance this one: multi hccap : merge A+B+D or B+C+D D found (A B C not found) ), add those files in a 7z archive and attach it to the trac ticket.
Please make sure that the cap/hccap are self generated and do not contain any sensitive info (i.e. please make captures w/ fake ESSID / BSSID / non-sensitive passwords)
2. it could be, since you use windows, that you didn't apply this patch: http://hashcat.net/wiki/doku.php?id=timeout_patch and/or GPU cooling is not done (correctly).
Furthermore, bcrypt is a slow and demanding algo, therefore it is very likely that w/o the reg patch etc... since driver does not respond in time, you see the crash. If not you need to do further test, when exactly it crashes...
I don't really like to discuss 2+ different problems within the same thread....
Anyway,
1. please open a trac ticket https://hashcat.net/trac/ with a set of *minimal* hccap files (for instance this one: multi hccap : merge A+B+D or B+C+D D found (A B C not found) ), add those files in a 7z archive and attach it to the trac ticket.
Please make sure that the cap/hccap are self generated and do not contain any sensitive info (i.e. please make captures w/ fake ESSID / BSSID / non-sensitive passwords)
2. it could be, since you use windows, that you didn't apply this patch: http://hashcat.net/wiki/doku.php?id=timeout_patch and/or GPU cooling is not done (correctly).
Furthermore, bcrypt is a slow and demanding algo, therefore it is very likely that w/o the reg patch etc... since driver does not respond in time, you see the crash. If not you need to do further test, when exactly it crashes...