Bug: bitcoin GPU recovery is broken since olcHashcat 1.37 till current (hashcat 3.10)

[md55]

I tried to recover test wallet.dat from this post http://www.gobitgo.com/articles/1005/How...-Password/

I created dic with 1 pass: GoBktGo
Latest hashcat-3.10 can find it on CPU:
Status.........: Cracked
but can't find on GPU:
Status.........: Exhausted

Hashcat introduced 11300 Bitcoin type since 1.36 so I tested some versions on GPU:
oclHashcat-1.36  found
oclHashcat-1.37  no
oclHashcat-2.01  no
    hashcat-3.00  no
    hashcat-3.10  no

oclHashcat-1.36 - is the only version worked right with test pass

My config:
Windows 7 x64, no SP
HIS Radeon HD 6990 (Device #1: Cayman, 512/2048 MB allocatable, 24MCU)
amd-catalyst-15.7.1-with-dotnet45-win7-64bit

[Chick3nman]

Working fine for me. Windows 7 x64, 2x GTX 1080



Hash Type:11300
hashcat (v3.10) starting...

OpenCL Platform #1: Intel(R) Corporation
========================================
- Device #1: Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, skipped

OpenCL Platform #2: NVIDIA Corporation
======================================
- Device #2: GeForce GTX 1080, 2048/8192 MB allocatable, 20MCU
- Device #3: GeForce GTX 1080, 2048/8192 MB allocatable, 20MCU

Hashes: 1 hashes; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1
Applicable Optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c

$bitcoin$96$6f1fda9af07911d230667721ed6ca45479f190956479229d3ced364e31e517c87bab73b9927652e5a7251affaf16c485$16$e7aaad845d0d7778$138
598$96$cc3de7e5bfbda99669a02e1df017f17a939b3d335ff1e32bac88fb09922eefbc823aebe7ae59e4aad9cd37ec9facc88d$66$03fa4f2b45e6f1764f8bc44c2
4ab51f70b19786d1d3bc912b78fa3fa1ff672d9bd:GoBktGo

Session.Name...: hashcat
Status.........: Cracked
Input.Mode.....: File (.\dicts\0)
Hash.Target....: $bitcoin$96$6f1fda9af07911d230667721ed6ca...
Hash.Type......: Bitcoin/Litecoin wallet.dat
Time.Started...: Tue Oct 25 16:37:51 2016 (2 secs)
Speed.Dev.#2...: 1736 H/s (0.30ms)
Speed.Dev.#3...: 1939 H/s (0.29ms)
Speed.Dev.#*...: 3675 H/s
Recovered......: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.......: 10816/10816 (100.00%)
Rejected.......: 0/10816 (0.00%)

Started: Tue Oct 25 16:37:51 2016
Stopped: Tue Oct 25 16:38:02 2016
Press any key to continue . . .

[atom]

Works fine, even with amd-gpu-pro:

root@sf:~/hashcat# cat > hash
$bitcoin$96$6f1fda9af07911d230667721ed6ca45479f190956479229d3ced364e31e517c87bab73b9927652e5a7251affaf16c485$16$e7aaad845d0d7778$138598$96$cc3de7e5bfbda99669a02e1df017f17a939b3d335ff1e32bac88fb09922eefbc823aebe7ae59e4aad9cd37ec9facc88d$66$03fa4f2b45e6f1764f8bc44c24ab51f70b19786d1d3bc912b78fa3fa1ff672d9bd
root@sf:~/hashcat# cat > pass
GoBktGo
root@sf:~/hashcat# ./hashcat -m 11300 hash pass
hashcat (v3.10-553-g6582a8a) starting...

OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
* Device #1: Ellesmere, 2047/4037 MB allocatable, 14MCU
* Device #2: AMD FX(tm)-6100 Six-Core Processor, skipped

Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1

Applicable Optimizers:
* Zero-Byte
* Single-Hash
* Single-Salt

Watchdog: Hardware Monitoring Interface not found on your system
Watchdog: Temperature abort trigger disabled
Watchdog: Temperature retain trigger disabled

Generated dictionary stats for pass: 8 bytes, 1 words, 1 keyspace

Generated dictionary stats for pass: 8 bytes, 1 words, 1 keyspace

The wordlist or mask you are using is too small.
Therefore, hashcat is unable to utilize the full parallelization power of your device(s).
The cracking speed will drop.
Workaround: https://hashcat.net/wiki/doku.php?id=fre...full_speed

INFO: approaching final keyspace, workload adjusted      

$bitcoin$96$6f1fda9af07911d230667721ed6ca45479f190956479229d3ced364e31e517c87bab73b9927652e5a7251affaf16c485$16$e7aaad845d0d7778$138598$96$cc3de7e5bfbda99669a02e1df017f17a939b3d335ff1e32bac88fb09922eefbc823aebe7ae59e4aad9cd37ec9facc88d$66$03fa4f2b45e6f1764f8bc44c24ab51f70b19786d1d3bc912b78fa3fa1ff672d9bd:GoBktGo
                                                         
Session........: hashcat
Status.........: Cracked
Hash.Type......: Bitcoin/Litecoin wallet.dat
Hash.Target....: $bitcoin$96$6f1fda9af07911d230667721ed6ca45479f190956479229d3ced364e31e517c87bab73b9927652e5a7251affaf16c485$16$e7aaad845d0d7778$138598$96$cc3de7e5bfbda99669a02e1df017f17a939b3d335ff1e32bac88fb09922eefbc823aebe7ae59e4aad9cd37ec9facc88d$6B^A
Time.Started...: Wed Oct 26 14:27:09 2016 (5 secs)
Time.Estimated.: Wed Oct 26 14:27:09 2016 (0 secs)
Input.Base.....: File (pass)
Speed.Dev.#1...:        0 H/s (0.74ms)
Recovered......: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Recovered/Time.: CUR:N/A,N/A,N/A AVG:11.81,708.83,17012.01 (Min,Hour,Day)
Progress.......: 1/1 (100.00%)
Rejected.......: 0/1 (0.00%)
Restore.Point..: 0/1 (0.00%)
Candidates.#1..: GoBktGo -> GoBktGo
HWMon.Dev.#1...: N/A

Started: Wed Oct 26 14:26:58 2016
Stopped: Wed Oct 26 14:27:14 2016

[md55]

Can it be device-specific bug for HIS Radeon HD 6990?

[atom]

Absolutely!