cudaHashcat 0 H/s bcrypt
#8
0 H/s in this case doesn't mean literally "no hashes per second", it means the kernel is taking too long to run and hasn't reached a checkpoint yet and thus the main thread is not able to calculate the speed.

In your first example you provided, you tested 544 candidates in 409 seconds. That's a hash rate of 1.33 H/s. In your second example, you tested 32 candidates in 24 seconds, for a hash rate of 1.33 H/s.


Messages In This Thread
cudaHashcat 0 H/s bcrypt - by dominator_sd - 04-04-2016, 10:11 AM
RE: cudaHashcat 0 H/s bcrypt - by undeath - 04-04-2016, 10:23 AM
RE: cudaHashcat 0 H/s bcrypt - by dominator_sd - 04-04-2016, 10:32 AM
RE: cudaHashcat 0 H/s bcrypt - by rurapenthe - 04-04-2016, 11:15 AM
RE: cudaHashcat 0 H/s bcrypt - by dominator_sd - 04-04-2016, 05:15 PM
RE: cudaHashcat 0 H/s bcrypt - by dominator_sd - 04-04-2016, 01:26 PM
RE: cudaHashcat 0 H/s bcrypt - by undeath - 04-04-2016, 06:50 PM
RE: cudaHashcat 0 H/s bcrypt - by epixoip - 04-04-2016, 07:37 PM