hashcat Forum › Support › hashcat v
m -15700 2h\s on 1080ti

Threaded Mode
m -15700 2h\s on 1080ti
gentl Offline
Junior Member
**
Posts: 49
Threads: 15
Joined: Mar 2019
#1
11-23-2019, 11:44 PM
Hello guys, want to recover my eth wallet
I installed actual K.ali Linux with hashcat on board
Then cuda and  nvidia drivers  (with instructions from k.ali website)

I am using wordlist attack
Problem that i have terrible speed on my 1080ti rig  0 - 2 h/s

hashcat -m 15700  -a 0 eth.hash ethpass.txt
Code:
hashcat (v5.1.0) starting...

* Device #1: Not a native Intel OpenCL runtime. Expect massive speed loss.
            You can use --force to override, but do not report related errors.
* 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: The pocl project
====================================
* Device #1: pthread-Intel(R) Xeon(R) CPU E5-2609 v3 @ 1.90GHz, skipped.

OpenCL Platform #2: Intel(R) Corporation
========================================
* Device #2: Intel(R) Xeon(R) CPU E5-2609 v3 @ 1.90GHz, skipped.

OpenCL Platform #3: NVIDIA Corporation
======================================
* Device #3: GeForce GTX 1080 Ti, 2793/11175 MB allocatable, 28MCU
* Device #4: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #5: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #6: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #7: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #8: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #9: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU

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

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

Watchdog: Temperature abort trigger set to 90c

Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 2.
Increasing single-block device memory allocatable for --scrypt-tmto 3.
SCRYPT tmto optimizer value set to: 4, mem: 7516192768

* Device #3: build_opts '-cl-std=CL1.2 -I OpenCL -I /usr/share/hashcat/OpenCL -D LOCAL_MEM_TYPE=1 -D VENDOR_ID=32 -D CUDA_ARCH=601 -D AMD_ROCM=0 -D VECT_SIZE=1 -D DEVICE_TYPE=4 -D DGST_R0=0 -D DGST_R1=1 -D DGST_R2=2 -D DGST_R3=3 -D DGST_ELEM=8 -D KERN_TYPE=15700 -D _unroll'


Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 2.
Increasing single-block device memory allocatable for --scrypt-tmto 3.
SCRYPT tmto optimizer value set to: 4, mem: 7516192768

* Device #4: build_opts '-cl-std=CL1.2 -I OpenCL -I /usr/share/hashcat/OpenCL -D LOCAL_MEM_TYPE=1 -D VENDOR_ID=32 -D CUDA_ARCH=601 -D AMD_ROCM=0 -D VECT_SIZE=1 -D DEVICE_TYPE=4 -D DGST_R0=0 -D DGST_R1=1 -D DGST_R2=2 -D DGST_R3=3 -D DGST_ELEM=8 -D KERN_TYPE=15700 -D _unroll'


Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 2.
Increasing single-block device memory allocatable for --scrypt-tmto 3.
SCRYPT tmto optimizer value set to: 4, mem: 7516192768

* Device #5: build_opts '-cl-std=CL1.2 -I OpenCL -I /usr/share/hashcat/OpenCL -D LOCAL_MEM_TYPE=1 -D VENDOR_ID=32 -D CUDA_ARCH=601 -D AMD_ROCM=0 -D VECT_SIZE=1 -D DEVICE_TYPE=4 -D DGST_R0=0 -D DGST_R1=1 -D DGST_R2=2 -D DGST_R3=3 -D DGST_ELEM=8 -D KERN_TYPE=15700 -D _unroll'


Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 2.
Increasing single-block device memory allocatable for --scrypt-tmto 3.
SCRYPT tmto optimizer value set to: 4, mem: 7516192768

* Device #6: build_opts '-cl-std=CL1.2 -I OpenCL -I /usr/share/hashcat/OpenCL -D LOCAL_MEM_TYPE=1 -D VENDOR_ID=32 -D CUDA_ARCH=601 -D AMD_ROCM=0 -D VECT_SIZE=1 -D DEVICE_TYPE=4 -D DGST_R0=0 -D DGST_R1=1 -D DGST_R2=2 -D DGST_R3=3 -D DGST_ELEM=8 -D KERN_TYPE=15700 -D _unroll'


Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 2.
Increasing single-block device memory allocatable for --scrypt-tmto 3.
SCRYPT tmto optimizer value set to: 4, mem: 7516192768

* Device #7: build_opts '-cl-std=CL1.2 -I OpenCL -I /usr/share/hashcat/OpenCL -D LOCAL_MEM_TYPE=1 -D VENDOR_ID=32 -D CUDA_ARCH=601 -D AMD_ROCM=0 -D VECT_SIZE=1 -D DEVICE_TYPE=4 -D DGST_R0=0 -D DGST_R1=1 -D DGST_R2=2 -D DGST_R3=3 -D DGST_ELEM=8 -D KERN_TYPE=15700 -D _unroll'


Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 2.
Increasing single-block device memory allocatable for --scrypt-tmto 3.
SCRYPT tmto optimizer value set to: 4, mem: 7516192768

* Device #8: build_opts '-cl-std=CL1.2 -I OpenCL -I /usr/share/hashcat/OpenCL -D LOCAL_MEM_TYPE=1 -D VENDOR_ID=32 -D CUDA_ARCH=601 -D AMD_ROCM=0 -D VECT_SIZE=1 -D DEVICE_TYPE=4 -D DGST_R0=0 -D DGST_R1=1 -D DGST_R2=2 -D DGST_R3=3 -D DGST_ELEM=8 -D KERN_TYPE=15700 -D _unroll'


Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 2.
Increasing single-block device memory allocatable for --scrypt-tmto 3.
SCRYPT tmto optimizer value set to: 4, mem: 7516192768

* Device #9: build_opts '-cl-std=CL1.2 -I OpenCL -I /usr/share/hashcat/OpenCL -D LOCAL_MEM_TYPE=1 -D VENDOR_ID=32 -D CUDA_ARCH=601 -D AMD_ROCM=0 -D VECT_SIZE=1 -D DEVICE_TYPE=4 -D DGST_R0=0 -D DGST_R1=1 -D DGST_R2=2 -D DGST_R3=3 -D DGST_ELEM=8 -D KERN_TYPE=15700 -D _unroll'

...

Speed.#3.........:        0 H/s (0.00ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.#4.........:        0 H/s (0.00ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.#5.........:        0 H/s (82579.72ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.#6.........:        0 H/s (0.00ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.#7.........:        0 H/s (80998.76ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.#8.........:        0 H/s (81218.51ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.#9.........:        0 H/s (81488.90ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.#*.........:        2 H/s

hashcat -b -m 15700

Code:
hashcat (v5.1.0) starting in benchmark mode...

Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.

* Device #1: Not a native Intel OpenCL runtime. Expect massive speed loss.
            You can use --force to override, but do not report related errors.
* 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: The pocl project
====================================
* Device #1: pthread-Intel(R) Xeon(R) CPU E5-2609 v3 @ 1.90GHz, skipped.

OpenCL Platform #2: Intel(R) Corporation
========================================
* Device #2: Intel(R) Xeon(R) CPU E5-2609 v3 @ 1.90GHz, skipped.

OpenCL Platform #3: NVIDIA Corporation
======================================
* Device #3: GeForce GTX 1080 Ti, 2793/11175 MB allocatable, 28MCU
* Device #4: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #5: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #6: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #7: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #8: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #9: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU

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

Hashmode: 15700 - Ethereum Wallet, SCRYPT (Iterations: 1)


Speed.#3.........:        3 H/s (9477.90ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.#4.........:        3 H/s (9884.17ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.#5.........:        3 H/s (9872.20ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.#6.........:        3 H/s (10001.87ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.#7.........:        3 H/s (9692.74ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.#8.........:        3 H/s (9656.35ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.#9.........:        3 H/s (9723.49ms) @ Accel:1 Loops:1 Thr:1 Vec:1
Speed.#*.........:      20 H/s


At same time  Bitcoin wallet showing good results
hashcat -b -m 11300

Code:
hashcat (v5.1.0) starting in benchmark mode...

Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.

* Device #1: Not a native Intel OpenCL runtime. Expect massive speed loss.
            You can use --force to override, but do not report related errors.
* 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: The pocl project
====================================
* Device #1: pthread-Intel(R) Xeon(R) CPU E5-2609 v3 @ 1.90GHz, skipped.

OpenCL Platform #2: Intel(R) Corporation
========================================
* Device #2: Intel(R) Xeon(R) CPU E5-2609 v3 @ 1.90GHz, skipped.

OpenCL Platform #3: NVIDIA Corporation
======================================
* Device #3: GeForce GTX 1080 Ti, 2793/11175 MB allocatable, 28MCU
* Device #4: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #5: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #6: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #7: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #8: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU
* Device #9: GeForce GTX 1080 Ti, 2794/11178 MB allocatable, 28MCU

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

Hashmode: 11300 - Bitcoin/Litecoin wallet.dat (Iterations: 199999)

Speed.#3.........:    7617 H/s (75.31ms) @ Accel:16 Loops:256 Thr:1024 Vec:1
Speed.#4.........:    7000 H/s (82.21ms) @ Accel:16 Loops:256 Thr:1024 Vec:1
Speed.#5.........:    7354 H/s (78.46ms) @ Accel:16 Loops:256 Thr:1024 Vec:1
Speed.#6.........:    7275 H/s (78.87ms) @ Accel:16 Loops:256 Thr:1024 Vec:1
Speed.#7.........:    7590 H/s (76.79ms) @ Accel:16 Loops:256 Thr:1024 Vec:1
Speed.#8.........:    7188 H/s (80.67ms) @ Accel:16 Loops:256 Thr:1024 Vec:1
Speed.#9.........:    6945 H/s (82.60ms) @ Accel:16 Loops:256 Thr:1024 Vec:1
Speed.#*.........:    50970 H/s
Find
Reply
undeath Offline
Sneaky Bastard
******
Posts: 2,301
Threads: 11
Joined: Jul 2010
#2
11-24-2019, 01:04 AM (This post was last modified: 11-24-2019, 01:04 AM by undeath.)
the ETH wallet is using scrypt which is specifically designed to be very slow on gpus. Your cpu might be faster.
Find
Reply
gentl Offline
Junior Member
**
Posts: 49
Threads: 15
Joined: Mar 2019
#3
11-24-2019, 12:03 PM
I ask cuz i read this post
https://hashcat.net/forum/thread-8000.html and guy told that he has 20 h/s on 1080 ti

and on this becnmark https://gist.github.com/epixoip/973da735...7527e4d073
i see
Hashtype: scrypt
Speed.Dev.#1.....: 911.1 kH/s (15.46ms)

or here https://www.servethehome.com/password-cr...0-ti-gpus/
Hashtype: scrypt
Speed.Dev.#1…..: 641.4 kH/s (18.60ms)
Speed.Dev.#2…..: 749.9 kH/s (18.46ms

How all this tests have 600 + kH/s speed...

I tested on
Xeon(R) CPU E5-2609 v3 - 8 h/s
Intel Coffee Lake I7-8700k - 27 h/s
Find
Reply
philsmd Offline
I'm phil
******
Posts: 2,267
Threads: 16
Joined: Feb 2013
#4
11-24-2019, 01:00 PM (This post was last modified: 11-24-2019, 01:00 PM by philsmd.)
it's called the cost factor (N, r, p).

different settings/cost implies different speed
Find
Reply
gentl Offline
Junior Member
**
Posts: 49
Threads: 15
Joined: Mar 2019
#5
11-24-2019, 09:06 PM
(11-24-2019, 01:00 PM)philsmd Wrote: it's called the cost factor (N, r, p).

different settings/cost implies different speed

I am not sure that i fully understand this factor...

But one thing is clear - Actual ethereum wallet format are fully protected from gpu
Find
Reply