hashcat Forum › Misc › Hardware v
Multiple GPU Problem

Threaded Mode
Multiple GPU Problem
korsangazi Offline
Junior Member
**
Posts: 2
Threads: 1
Joined: Mar 2020
#1
03-11-2020, 02:26 PM (This post was last modified: 03-11-2020, 02:43 PM by korsangazi.)
Hello,
Os : Windows 10
Hascat Version: v5.1.0
GPUs : 12 X Manli P106L Mining Card
https://www.techpowerup.com/gpu-specs/ma...6-gb.b6880

I have speed problem

one gpu 5883.6 MH/s for md5
all gpu each one : 1591 - 1913.5 MH/s for md5

I need help.

One GPU Benchmark
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 #13: Intel's OpenCL runtime (GPU only) is currently broken.             We are waiting for updated OpenCL drivers from Intel.             You can use --force to override, but do not report related errors. OpenCL Platform #1: NVIDIA Corporation ====================================== * Device #1: P106-090, 1519/6077 MB allocatable, 5MCU * Device #2: P106-090, skipped. * Device #3: P106-090, skipped. * Device #4: P106-090, skipped. * Device #5: P106-090, skipped. * Device #6: P106-090, skipped. * Device #7: P106-090, skipped. * Device #8: P106-090, skipped. * Device #9: P106-090, skipped. * Device #10: P106-090, skipped. * Device #11: P106-090, skipped. * Device #12: P106-090, skipped. OpenCL Platform #2: Intel(R) Corporation ======================================== * Device #13: Intel(R) HD Graphics 510, skipped. * Device #14: Intel(R) Pentium(R) CPU G4400 @ 3.30GHz, skipped. Benchmark relevant options: =========================== * --opencl-devices=1 * --optimized-kernel-enable Hashmode: 0 - MD5 Speed.#1.........:  5883.6 MH/s (56.70ms) @ Accel:64 Loops:1024 Thr:1024 Vec:1 Started: Wed Mar 11 12:11:51 2020                                   Stopped: Wed Mar 11 12:12:00 2020


ALL GPU:
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 #13: Intel's OpenCL runtime (GPU only) is currently broken.             We are waiting for updated OpenCL drivers from Intel.             You can use --force to override, but do not report related errors. OpenCL Platform #1: NVIDIA Corporation ====================================== * Device #1: P106-090, 1519/6077 MB allocatable, 5MCU * Device #2: P106-090, 1519/6077 MB allocatable, 5MCU * Device #3: P106-090, 1519/6077 MB allocatable, 5MCU * Device #4: P106-090, 1519/6077 MB allocatable, 5MCU * Device #5: P106-090, 1519/6077 MB allocatable, 5MCU * Device #6: P106-090, 1519/6077 MB allocatable, 5MCU * Device #7: P106-090, 1519/6077 MB allocatable, 5MCU * Device #8: P106-090, 1519/6077 MB allocatable, 5MCU * Device #9: P106-090, 1519/6077 MB allocatable, 5MCU * Device #10: P106-090, 1519/6077 MB allocatable, 5MCU * Device #11: P106-090, 1519/6077 MB allocatable, 5MCU * Device #12: P106-090, 1519/6077 MB allocatable, 5MCU OpenCL Platform #2: Intel(R) Corporation ======================================== * Device #13: Intel(R) HD Graphics 510, skipped. * Device #14: Intel(R) Pentium(R) CPU G4400 @ 3.30GHz, skipped. Benchmark relevant options: =========================== * --optimized-kernel-enable Hashmode: 0 - MD5 Speed.#1.........:  1646.4 MH/s (56.72ms) @ Accel:64 Loops:1024 Thr:1024 Vec:1 Speed.#2.........:  1647.0 MH/s (57.50ms) @ Accel:64 Loops:1024 Thr:1024 Vec:1 Speed.#3.........:  1647.1 MH/s (57.36ms) @ Accel:64 Loops:1024 Thr:1024 Vec:1 Speed.#4.........:  1591.2 MH/s (59.66ms) @ Accel:64 Loops:1024 Thr:1024 Vec:1 Speed.#5.........:  1724.4 MH/s (57.47ms) @ Accel:64 Loops:1024 Thr:1024 Vec:1 Speed.#6.........:  1666.7 MH/s (58.25ms) @ Accel:64 Loops:1024 Thr:1024 Vec:1 Speed.#7.........:  1640.9 MH/s (57.27ms) @ Accel:64 Loops:1024 Thr:1024 Vec:1 Speed.#8.........:  1667.5 MH/s (59.23ms) @ Accel:64 Loops:1024 Thr:1024 Vec:1 Speed.#9.........:  1667.6 MH/s (57.57ms) @ Accel:64 Loops:1024 Thr:1024 Vec:1 Speed.#10.........:  1752.7 MH/s (56.79ms) @ Accel:64 Loops:1024 Thr:1024 Vec:1 Speed.#11.........:  1913.5 MH/s (59.07ms) @ Accel:64 Loops:1024 Thr:1024 Vec:1 Speed.#12.........:  1905.4 MH/s (58.32ms) @ Accel:64 Loops:1024 Thr:1024 Vec:1 Speed.#*.........: 20470.4 MH/s Started: Wed Mar 11 12:08:43 2020                                   Stopped: Wed Mar 11 12:09:17 2020
Find
Reply
undeath Offline
Sneaky Bastard
******
Posts: 2,293
Threads: 11
Joined: Jul 2010
#2
03-11-2020, 07:50 PM
possibly heat or power throttling.
Find
Reply
korsangazi Offline
Junior Member
**
Posts: 2
Threads: 1
Joined: Mar 2020
#3
03-11-2020, 08:54 PM
(03-11-2020, 07:50 PM)undeath Wrote: possibly heat or power throttling.
Not heat because working with ubuntu. Windows have this problem.
how can i solve do you have a idea ?
Find
Reply
philsmd Offline
I'm phil
******
Posts: 2,255
Threads: 16
Joined: Feb 2013
#4
03-12-2020, 11:03 AM
try to use some task manager and tuning tools (like afterburner) etc.

could be bad risers, too slow CPU/cores, little RAM, configurations etc etc etc
try test with -d 1,2,3 etc and add GPUs until it slows down

BTW: it seems you were very eager to just copy-paste the same problem also here https://github.com/hashcat/hashcat/issues/2325 , that's a little bit digusting/disrecpectful and counter-productive (where should we answer now, nowhere because we can't decide ?). Sometimes less and having a little bit of patience is better !
Find
Reply