hashcat Forum

hi folks, im getting with my 2x 1080ti + 1070 on stock very weird speeds with md5 and ntlm. -w 3 and only 1 hash is being cracked, but still very low speeds. max 20917.9 MH/s  for NTLM, 12114.5 MH/s  for MD5 per 1080ti.

System specs:
i7 8700k, 64GB DDR4, MSI Z370 Sli plus, ubuntu 18.04,

below outputs.

hashcat64.bin -m 0 tmp_hash -a3 ?a?a?a?a?a?a?a?a
hashcat (v4.2.1) starting...

* Device #1: WARNING! Kernel exec timeout is not disabled.
             This may cause "CL_OUT_OF_RESOURCES" or related errors.
             To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #2: WARNING! Kernel exec timeout is not disabled.
             This may cause "CL_OUT_OF_RESOURCES" or related errors.
             To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #3: WARNING! Kernel exec timeout is not disabled.
             This may cause "CL_OUT_OF_RESOURCES" or related errors.
             To disable the timeout, see: https://hashcat.net/q/timeoutpatch
OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #2: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #3: GeForce GTX 1070, 2029/8119 MB allocatable, 15MCU

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

Applicable optimizers:
* Zero-Byte
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
* Raw-Hash

Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256

ATTENTION! Pure (unoptimized) OpenCL kernels selected.
This enables cracking passwords and salts > length 32 but for the price of drastically reduced performance.
If you want to switch to optimized OpenCL kernels, append -O to your commandline.

[s]tatus [p]ause ypass [c]heckpoint [q]uit => s

Session..........: hashcat
Status...........: Running
Hash.Type........: MD5
Hash.Target......: e778f845815adedeXXXXXXXXX
Time.Started.....: Tue Sep 25 23:10:27 2018 (11 secs)
Time.Estimated...: Fri Sep 28 13:48:30 2018 (2 days, 14 hours)
Guess.Mask.......: ?a?a?a?a?a?a?a?a [8]
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....: 10829.8 MH/s (10.58ms) @ Accel:128 Loops:32 Thr:1024 Vec:1
Speed.Dev.#2.....: 12114.5 MH/s (9.51ms) @ Accel:128 Loops:32 Thr:1024 Vec:1
Speed.Dev.#3.....:  6477.9 MH/s (9.51ms) @ Accel:128 Loops:32 Thr:1024 Vec:1
Speed.Dev.#*.....: 29422.1 MH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 316867084288/6634204312890625 (0.00%)
Rejected.........: 0/316867084288 (0.00%)
Restore.Point....: 0/7737809375 (0.00%)
Candidates.#1....: RlizXzus -> ;zurc~de
Candidates.#2....: 3 #erane -> E)c!AJUS
Candidates.#3....: E(*Q-uer -> :WOf*MY1
HWMon.Dev.#1.....: Temp: 61c Fan:100% Util:100% Core:1860MHz Mem:5005MHz Bus:8
HWMon.Dev.#2.....: Temp: 62c Fan:100% Util: 99% Core:1961MHz Mem:5005MHz Bus:8
HWMon.Dev.#3.....: Temp: 50c Fan:100% Util: 98% Core:1797MHz Mem:3802MHz Bus:4


[b]hashcat64.bin -m 1000 tmp_hash -a3 ?a?a?a?a?a?a?a?a -w3

[/b][s]tatus [p]ause ypass [c]heckpoint [q]uit => s

Session..........: hashcat
Status...........: Running
Hash.Type........: NTLM
Hash.Target......: b749e584fc1aaXXXXXXXXXXXXXXXXXXXXX
Time.Started.....: Tue Sep 25 23:15:28 2018 (5 secs)
Time.Estimated...: Thu Sep 27 12:45:43 2018 (1 day, 13 hours)
Guess.Mask.......: ?a?a?a?a?a?a?a?a [8]
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....: 18193.1 MH/s (50.70ms) @ Accel:128 Loops:256 Thr:1024 Vec:1
Speed.Dev.#2.....: 20917.9 MH/s (44.21ms) @ Accel:128 Loops:256 Thr:1024 Vec:1
Speed.Dev.#3.....: 10025.8 MH/s (49.56ms) @ Accel:256 Loops:128 Thr:1024 Vec:1
Speed.Dev.#*.....: 49140.0 MH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 239545090048/6634204312890625 (0.00%)
Rejected.........: 0/239545090048 (0.00%)
Restore.Point....: 0/7737809375 (0.00%)
Candidates.#1....: y*sm$GUS ->  am<yQQU
Candidates.#2....: -li~L(34 -> LynJ~dll
Candidates.#3....: .71erane -> c@#2#xer
HWMon.Dev.#1.....: Temp: 64c Fan: 35% Util:100% Core:1860MHz Mem:5005MHz Bus:8
HWMon.Dev.#2.....: Temp: 66c Fan: 36% Util:100% Core:1961MHz Mem:5005MHz Bus:8
HWMon.Dev.#3.....: Temp: 52c Fan: 32% Util:100% Core:1797MHz Mem:3802MHz Bus:4

here benchmark for ntlm:

Benchmark relevant options:
===========================
* --optimized-kernel-enable

Hashmode: 1000 - NTLM

Speed.Dev.#1.....: 60306.4 MH/s (60.43ms) @ Accel:128 Loops:1024 Thr:1024 Vec:2
Speed.Dev.#2.....: 65369.0 MH/s (55.82ms) @ Accel:128 Loops:1024 Thr:1024 Vec:2
Speed.Dev.#3.....: 32376.5 MH/s (61.48ms) @ Accel:256 Loops:512 Thr:1024 Vec:2
Speed.Dev.#*.....:   158.1 GH/s

Hashmode: 0 - MD5

Speed.Dev.#1.....: 36153.9 MH/s (51.07ms) @ Accel:128 Loops:512 Thr:1024 Vec:4
Speed.Dev.#2.....: 39065.0 MH/s (47.32ms) @ Accel:128 Loops:512 Thr:1024 Vec:4
Speed.Dev.#3.....: 19190.3 MH/s (51.83ms) @ Accel:256 Loops:256 Thr:1024 Vec:4
Speed.Dev.#*.....: 94409.2 MH/s

What could be wrong in my setting?

(09-25-2018, 11:27 PM)alish Wrote: [ -> ]What could be wrong in my setting?

You're not reading what's in front of you.

try with option -O

(09-26-2018, 10:43 PM)walterlacka Wrote: [ -> ]try with option -O

still with -O option slow....

hashcat64.bin -a3 tmp_hash -i --increment-min 8 ?l?l?l?l?l?l?l?l?l?l  -m 1000 -O -w3
hashcat (v4.2.1) starting...

OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #2: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #3: GeForce GTX 1070, 2029/8119 MB allocatable, 15MCU

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

Applicable optimizers:
* Optimized-Kernel
* Zero-Byte
* Precompute-Init
* Precompute-Merkle-Demgard
* Meet-In-The-Middle
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
* Raw-Hash

Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 27

Watchdog: Temperature abort trigger set to 90c

[s]tatus [p]ause ypass [c]heckpoint [q]uit => s

Session..........: hashcat
Status...........: Running
Hash.Type........: NTLM
Hash.Target......: 95b8437026xxxxxxxxxxxxxxxxxxxxx
Time.Started.....: Wed Sep 26 23:48:11 2018 (1 sec)
Time.Estimated...: Wed Sep 26 23:48:14 2018 (2 secs)
Guess.Mask.......: ?l?l?l?l?l?l?l?l [8]
Guess.Queue......: 1/3 (33.33%)
Speed.Dev.#1.....: [b]25448.4 MH/s (40.96ms) @ Accel:128 Loops:676 Thr:1024 Vec:2
Speed.Dev.#2.....: 25792.4 MH/s (40.79ms) @ Accel:128 Loops:676 Thr:1024 Vec:2
Speed.Dev.#3.....: 20467.2 MH/s (85.76ms) @ Accel:256 Loops:676 Thr:1024 Vec:2
Speed.Dev.#*.....: 71708.0 MH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 48023732224/208827064576 (23.00%)
Rejected.........: 0/48023732224 (0.00%)
Restore.Point....: 63700992/308915776 (20.62%)
Candidates.#1....: saccmcqg -> xzzchdyg
Candidates.#2....: saecrbig -> xzmcmcqg
Candidates.#3....: saihylzf -> xzqbrbig
HWMon.Dev.#1.....: Temp: 51c Fan: 29% Util:100% Core:1873MHz Mem:5005MHz Bus:8
HWMon.Dev.#2.....: Temp: 51c Fan: 29% Util:100% Core:1860MHz Mem:5005MHz Bus:8
HWMon.Dev.#3.....: Temp: 44c Fan: 32% Util:100% Core:1771MHz Mem:3802MHz Bus:4

uname -a

Linux men 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

nvidia-settings -h

nvidia-settings:  version 396.54


[/b]

you're not supplying enough work

Time.Started.....: Wed Sep 26 23:48:11 2018 (1 sec)
Time.Estimated...: Wed Sep 26 23:48:14 2018 (2 secs)

(09-26-2018, 11:58 PM)undeath Wrote: [ -> ]you're not supplying enough work

Time.Started.....: Wed Sep 26 23:48:11 2018 (1 sec)
Time.Estimated...: Wed Sep 26 23:48:14 2018 (2 secs)

i dunno, what u going to prove with that, but  after 9min, it is still slow!

hashcat64.bin -a3 tmp_hash  ?l?l?l?l?l?l?l?l?a?a  -m 1000 -O -w3
hashcat (v4.2.1) starting...

OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #2: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #3: GeForce GTX 1070, 2029/8119 MB allocatable, 15MCU

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

Applicable optimizers:
* Optimized-Kernel
* Zero-Byte
* Precompute-Init
* Precompute-Merkle-Demgard
* Meet-In-The-Middle
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
* Raw-Hash

Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 27

Watchdog: Temperature abort trigger set to 90c

[s]tatus [p]ause ypass [c]heckpoint [q]uit => s


Session..........: hashcat
Status...........: Running
Hash.Type........: NTLM
Hash.Target......: 95b8437xxxxxxxx
Time.Started.....: Thu Sep 27 17:53:46 2018 (9 mins, 58 secs)
Time.Estimated...: Fri Sep 28 01:17:58 2018 (7 hours, 14 mins)
Guess.Mask.......: ?l?l?l?l?l?l?l?l?a?a [10]
Guess.Queue......: 1/1 (100.00%)
[b]Speed.Dev.#1.....: 25368.0 MH/s (41.65ms) @ Accel:128 Loops:676 Thr:1024 Vec:2
Speed.Dev.#2.....: 25306.4 MH/s (42.09ms) @ Accel:128 Loops:676 Thr:1024 Vec:2
Speed.Dev.#3.....: 20032.3 MH/s (84.82ms) @ Accel:256 Loops:676 Thr:1024 Vec:2
Speed.Dev.#*.....: 70706.7 MH/s
[/b]Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 42441815097344/1884664257798400 (2.25%)
Rejected.........: 0/42441815097344 (0.00%)
Restore.Point....: 62776410112/2787964878400 (2.25%)
Candidates.#1....: savvifog-" -> xzrwdgwg-"
Candidates.#2....: satwdgwg-" -> xzwwygeh-"
Candidates.#3....: saxaqpfg-" -> xzjvifog-"
HWMon.Dev.#1.....: Temp: 66c Fan: 75% Util: 99% Core:1822MHz Mem:5005MHz Bus:8
HWMon.Dev.#2.....: Temp: 72c Fan: 71% Util:100% Core:1771MHz Mem:5005MHz Bus:8
HWMon.Dev.#3.....: Temp: 63c Fan: 71% Util: 99% Core:1733MHz Mem:3802MHz Bus:4

Try -w 4 instead of 3. Also, in my limited testing, Nvidia seems to have broken the latest drivers and knocked off 5-10% for some “older” cards.

Try ?a?a?l?l?l?l?l?l?l?l instead of ?l?l?l?l?l?l?l?l?a?a (because of unicode)

(09-28-2018, 08:25 PM)atom Wrote: [ -> ]Try ?a?a?l?l?l?l?l?l?l?l instead of ?l?l?l?l?l?l?l?l?a?a (because of unicode)

that did bring to good speeds, but as soon the file contains > 1 hashes, speeds drop again. Is that speeddrop normal ? then how to crack 100 of ntlm hashes with [b]135.8 GH/s[/b]in one go, if hashcat drops like that because of many hashes in one file?

Session..........: hashcat
Status...........: Running
Hash.Type........: NTLM
Hash.Target......: 95b843xxxxxxxxxxxxxxx
Time.Started.....: Fri Sep 28 22:18:00 2018 (2 secs)
Time.Estimated...: Sat Sep 29 02:09:19 2018 (3 hours, 51 mins)
Guess.Mask.......: ?a?a?l?l?l?l?l?l?l?l [10]
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....: 53000.0 MH/s (62.31ms) @ Accel:128 Loops:1024 Thr:1024 Vec:2
Speed.Dev.#2.....: 53065.3 MH/s (62.37ms) @ Accel:128 Loops:1024 Thr:1024 Vec:2
Speed.Dev.#3.....: 29717.0 MH/s (63.64ms) @ Accel:256 Loops:512 Thr:1024 Vec:2
Speed.Dev.#*.....:   135.8 GH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 292469604352/1884664257798400 (0.02%)
Rejected.........: 0/292469604352 (0.00%)

hashcat64.bin -m 1000 -O -w3 2x_split -a3 ?a?a?a?a?a?a?a?a

Session..........: hashcat
Status...........: Quit
Hash.Type........: NTLM
Hash.Target......: 2x_split
Time.Started.....: Fri Sep 28 22:27:01 2018 (1 min, 15 secs)
Time.Estimated...: Sat Sep 29 05:20:09 2018 (6 hours, 51 mins)
Guess.Mask.......: ?a?a?l?l?l?l?l?l?l?l [10]
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....: 29939.0 MH/s (60.37ms) @ Accel:128 Loops:512 Thr:1024 Vec:2
Speed.Dev.#2.....: 30045.4 MH/s (58.67ms) @ Accel:128 Loops:512 Thr:1024 Vec:2
Speed.Dev.#3.....: 16046.5 MH/s (60.17ms) @ Accel:256 Loops:256 Thr:1024 Vec:2
Speed.Dev.#*.....: 76031.0 MH/s
Recovered........: 1/2 (50.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 5654123905024/1884664257798400 (0.30%)
Rejected.........: 0/5654123905024 (0.00%)
Restore.Point....: 606863360/208827064576 (0.29%)
Candidates.#1....: E5ptstyaca -> ):ounugbca
Candidates.#2....: tKytxsqaca -> KPgtstyaca
Candidates.#3....: o[tyediaca -> |]ltxsqaca
HWMon.Dev.#1.....: Temp: 78c Fan: 70% Util: 98% Core:1847MHz Mem:5054MHz Bus:8
HWMon.Dev.#2.....: Temp: 82c Fan: 70% Util:100% Core:1809MHz Mem:5054MHz Bus:8
HWMon.Dev.#3.....: Temp: 62c Fan: 70% Util:100% Core:1797MHz Mem:3855MHz Bus:4

Yes that's perfectly normal. With multiple hashes there's some optimization that we can not do.