hashcat Forum › Support › hashcat v
Hashcat RTX 3080 Performance issues (Windows)

Threaded Mode
Hashcat RTX 3080 Performance issues (Windows)
xcookes Offline
Junior Member
**
Posts: 2
Threads: 1
Joined: Mar 2022
#1
03-18-2022, 07:15 PM (This post was last modified: 03-18-2022, 08:41 PM by xcookes.)
Hello Everyone,


I'm experimenting with hashcat (v6.2.5) on Windows cracking “bcrypt $2*$, Blowfish (Unix)” hashes, but I feel like my hashrate is really slow on RTX 3080.

Is this hashrate correct for this GPU?

Code:
hashcat-6.2.5>hashcat.exe -m 3200 hash.txt rockyou.txt -w 3 -a 0 -O
hashcat (v6.2.5) starting

CUDA API (CUDA 11.6)
====================
* Device #1: NVIDIA GeForce RTX 3080, 9106/10239 MB, 68MCU

OpenCL API (OpenCL 3.0 CUDA 11.6.110) - Platform #1 [NVIDIA Corporation]
========================================================================
* Device #2: NVIDIA GeForce RTX 3080, skipped

Kernel ./OpenCL/m03200-optimized.cl:
Optimized kernel requested, but not available or not required
Falling back to pure kernel

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

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

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

Watchdog: Temperature abort trigger set to 90c

Host memory required for this attack: 6 MB

Dictionary cache hit:
* Filename..: rockyou.txt
* Passwords.: 14344385
* Bytes.....: 139921507
* Keyspace..: 14344385

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

Session..........: hashcat
Status...........: Running
Hash.Mode........: 3200 (bcrypt $2*$, Blowfish (Unix))
Hash.Target......: $2y$13$XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Time.Started.....: Fri Mar 18 16:57:41 2022 (23 secs)
Time.Estimated...: Sat Mar 19 04:19:59 2022 (11 hours, 21 mins)
Kernel.Feature...: Pure Kernel
Guess.Base.......: File (rockyou.txt)
Guess.Queue......: 1/1 (100.00%)
Speed.#1.........:      350 H/s (67.98ms) @ Accel:64 Loops:128 Thr:24 Vec:1
Recovered........: 0/1 (0.00%) Digests
Progress.........: 7680/14344385 (0.05%)
Rejected.........: 0/7680 (0.00%)
Restore.Point....: 7680/14344385 (0.05%)
Restore.Sub.#1...: Salt:0 Amplifier:0-1 Iteration:2944-3072
Candidate.Engine.: Device Generator
Candidates.#1....: somebody -> sassy123
Hardware.Mon.#1..: Temp: 57c Fan: 30% Util:100% Core:1964MHz Mem:9242MHz Bus:16

[s]tatus [p]ause [b]ypass [c]heckpoint [f]inish [q]uit =>
Find
Reply
Chick3nman Offline
The Man, The Myth, The Chicken
******
Posts: 407
Threads: 2
Joined: Dec 2015
#2
03-18-2022, 08:25 PM
That is correct. In fact, that's a little faster than i would have expected. Bcrypt is built to be extremely difficult to crack and it does a really god job of it. There's nothing you can do to make it go any faster on that hardware.
Find
Reply
xcookes Offline
Junior Member
**
Posts: 2
Threads: 1
Joined: Mar 2022
#3
03-18-2022, 08:44 PM (This post was last modified: 03-18-2022, 08:45 PM by xcookes.)
(03-18-2022, 08:25 PM)Chick3nman Wrote: That is correct. In fact, that's a little faster than i would have expected. Bcrypt is built to be extremely difficult to crack and it does a really god job of it. There's nothing you can do to make it go any faster on that hardware.

Thank you for your response, thats good to hear. The GPU seems quiter than it usually is under load, but I guess thats due to the low memory usage of this type of attack.
Find
Reply