11-26-2015, 02:16 PM
cr4zynou, I am pretty confident that you are not using the newest version of oclHashcat.
Because this looks *exactly* like the bug that was fixed with this ticket https://hashcat.net/trac/ticket/617 already with the release of version 1.37. So you must be using version 1.36 or an earlier version.
If that is true (and as already said I am pretty sure this is the case here, because with version <= 1.36 I get the *very* same numbers/problem), that is pretty evil to report a problem where you claim this is a (still) existing bug/problem without even letting us know which version of oclHashcat you are using etc. It would be very kind of you if you at least try with the newest version before reporting a problem.
So for the future:
1. always update to the lastest version
2. check if a similar problem was already fixed (or at least reported on trac)
3. specify the exact version, GPU model etc when reporting a problem
...
Because this looks *exactly* like the bug that was fixed with this ticket https://hashcat.net/trac/ticket/617 already with the release of version 1.37. So you must be using version 1.36 or an earlier version.
If that is true (and as already said I am pretty sure this is the case here, because with version <= 1.36 I get the *very* same numbers/problem), that is pretty evil to report a problem where you claim this is a (still) existing bug/problem without even letting us know which version of oclHashcat you are using etc. It would be very kind of you if you at least try with the newest version before reporting a problem.
So for the future:
1. always update to the lastest version
2. check if a similar problem was already fixed (or at least reported on trac)
3. specify the exact version, GPU model etc when reporting a problem
...