cudaHashcat 0 H/s bcrypt

[dominator_sd]

I am trying to crack bcrypt passwords using the rockyou dictionary but the "status" shows 0% progress and a GPU speed of 0 H/s. 

command and status:

>cudaHashcat64.exe -m
 3200 --weak-hash-threshold=0 --potfile-disable --outfile=bcrypt_cracked.txt brc
rypt_digests.txt rockyou.txt
cudaHashcat v2.01 starting...

Device #1: GeForce GT 630M, 2048MB, 1600Mhz, 2MCU

Hashes: 37145 hashes; 37145 unique digests, 37145 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1
Applicable Optimizers:
* Zero-Byte
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: Kernel ./kernels/4318/m03200.sm_21.64.cubin
Device #1: Kernel ./kernels/4318/amp_a0_v1.sm_21.64.cubin

Cache-hit dictionary stats rockyou.txt: 1008205 bytes, 110038 words, 110038 keys
pace

[s]tatus [p]ause [r]esume [b]ypass [q]uit =>

Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: File (rockyou.txt)
Hash.Target....: File (brcrypt_digests.txt)
Hash.Type......: bcrypt, Blowfish(OpenBSD)
Time.Started...: Mon Apr 04 13:29:09 2016 (6 mins, 49 secs)
Time.Estimated.: 0 secs
Speed.GPU.#1...:        0 H/s
Recovered......: 0/37145 (0.00%) Digests, 0/37145 (0.00%) Salts
Recovered/Time.: CUR:0,N/A,N/A AVG:0.00,0.00,0.00 (Min,Hour,Day)
Progress.......: 544/4087361510 (0.00%)
Rejected.......: 0/544 (0.00%)
Restore.Point..: 0/110038 (0.00%)
HWMon.GPU.#1...: 99% Util, 73c Temp, N/A Fan

[undeath]

Your gpu is very slow and bcrypt is very slow and you are trying to crack many hashes. It will probably be faster running this on cpu.

[dominator_sd]

Your gpu is very slow and bcrypt is very slow and you are trying to crack many hashes. It will probably be faster running this on cpu.

Is it possible that my gpu is so slow that the progress 0% even after one hour?

[rurapenthe]

Your gpu is very slow and bcrypt is very slow and you are trying to crack many hashes. It will probably be faster running this on cpu.

Is it possible that my gpu is so slow that the progress 0% even after one hour?

Yes, it is quite possible. Remember too if this is Windows, it will adjust your 630M usage to match requirements by the system too. So even then its probably not at 100%, which still wouldnt help as undeath mentioned above.

I'm afraid you need CPU, and a LOT of it for bcrypt.

[dominator_sd]

Ok. I was aware that bcrypt was built to avoid GPU optimization but did not expect it to be so slow. As suggested I will try to use a CPU instead of my GPU, would a Xeon dual core be a good choice?
Also, is there a way to run cudaHashcat with CPU instead of the GPU?

[dominator_sd]

Your gpu is very slow and bcrypt is very slow and you are trying to crack many hashes. It will probably be faster running this on cpu.

I just tried to crack a single password and it cracked it within 30 seconds. How is it possible if my gpu is too slow and processes 0 H/s?

command and response:

>cudaHashcat64.exe -m
 3200 --weak-hash-threshold=0 --potfile-disable  $2a$12$n3BbgsUMGxdq6pNJBbmyseVQ
82ZEiK09KyiGqT3CSPM72n4uZ**** rockyou.txt

$2a$12$n3BbgsUMGxdq6pNJBbmyseVQ82ZEiK09KyiGqT3CSPM72n4uZ****:passw****

Session.Name...: cudaHashcat
Status.........: Cracked
Input.Mode.....: File (rockyou.txt)
Hash.Target....: $2a$12$n3BbgsUMGxdq6pNJBbmyseVQ82ZEiK09Ky...
Hash.Type......: bcrypt, Blowfish(OpenBSD)
Time.Started...: Mon Apr 04 20:38:15 2016 (24 secs)
Speed.GPU.#1...:        0 H/s
Recovered......: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.......: 32/110038 (0.03%)
Rejected.......: 0/32 (0.00%)
Restore.Point..: 0/110038 (0.00%)
HWMon.GPU.#1...: 46% Util, 57c Temp, N/A Fan

Started: Mon Apr 04 20:38:15 2016
Stopped: Mon Apr 04 20:38:40 2016

[undeath]

Time.Started...: Mon Apr 04 13:29:09 2016 (6 mins, 49 secs)
Recovered......: 0/37145 (0.00%) Digests, 0/37145 (0.00%) Salts
Progress.......: 544/4087361510 (0.00%)

Time.Started...: Mon Apr 04 20:38:15 2016 (24 secs)
Recovered......: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.......: 32/110038 (0.03%)

compare those numbers yourself

[epixoip]

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.