Cracking performance lower than expected?

[MA40]

Hello.
 
HashCat always sends me this message:
 

Code:

Cracking performance lower than expected?                 * Update your backend API runtime / driver the right way: https://hashcat.net/faq/wrongdriver * Create more work items to make use of your parallelization power: https://hashcat.net/faq/morework

 
Is this always done as a rule or is it that I have something wrong configured and I have to improve it?
 
All the best.

[philsmd]

you need to mention more about what you are trying to do (including the command and the input size: size of dictionary, size of rules etc).

The FAQ (the link) explains it quite good, what the "problem" could be. Sometimes it's not worth to bother too much about this message (depending on the time needed to finish the attack etc), but it's important that you understand that hashcat isn't able to achieve full acceleration with the current command and input (that's the most important part of the warning message). Just read and try to understand

[MA40]

Thanks.
 
The command is as follows:
 

Code:

$ ./hashcat.bin -O -m 11300 -a 0 -w 4 -D 1,2 -S -o bitcoin.cracked bitcoin.hashes **********.txt

 
The dictionary file **********.txt is 21.7 GB.
 
The bitcoin.hashes file has 86 hashes.
 
All the best.
 

Code:

$ ./hashcat.bin --restore hashcat (v6.2.2) starting in restore mode...   CUDA API (CUDA 11.4) ==================== * Device #1: NVIDIA GeForce GTX 750 Ti, 1971/2001 MB, 5MCU   OpenCL API (OpenCL 2.1 LINUX) - Platform #1 [Intel(R) Corporation] ================================================================== * Device #2: Intel(R) Core(TM) i7 CPU         980  @ 3.33GHz, 23986/24050 MB (6012 MB allocatable), 12MCU   OpenCL API (OpenCL 3.0 CUDA 11.4.94) - Platform #2 [NVIDIA Corporation] ======================================================================= * Device #3: NVIDIA GeForce GTX 750 Ti, skipped   Kernel /opt/HashCat/OpenCL/m11300-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: 256   Hashes: 88 digests; 86 unique digests, 85 unique salts Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates Rules: 1   Optimizers applied: * Zero-Byte * Slow-Hash-SIMD-LOOP * Uses-64-Bit   Watchdog: Temperature abort trigger set to 90c   Host memory required for this attack: 430 MB   Dictionary cache hit: * Filename..: **********.txt * Passwords.: 1973218843 * Bytes.....: 21744529702 * Keyspace..: 1973218843   [s]tatus [p]ause [b]ypass [c]heckpoint [f]inish [q]uit => s   Session..........: hashcat Status...........: Running Hash.Name........: Bitcoin/Litecoin wallet.dat Hash.Target......: bitcoin.hashes Time.Started.....: Thu Aug  5 15:01:39 2021 (4 hours, 40 mins) Time.Estimated...: Thu Jul 25 15:10:24 2024 (2 years, 354 days) Kernel.Feature...: Pure Kernel Guess.Base.......: File (**********.txt) Guess.Queue......: 1/1 (100.00%) Speed.#1.........:     1590 H/s (319.13ms) @ Accel:64 Loops:128 Thr:1024 Vec:1 Speed.#2.........:      191 H/s (358.86ms) @ Accel:512 Loops:1024 Thr:1 Vec:2 Speed.#*.........:     1781 H/s Recovered........: 0/86 (0.00%) Digests, 0/85 (0.00%) Salts Progress.........: 776404992/167723601655 (0.46%) Rejected.........: 0/776404992 (0.00%) Restore.Point....: 9152512/1973218843 (0.46%) Restore.Sub.#1...: Salt:80 Amplifier:0-1 Iteration:138240-138368 Restore.Sub.#2...: Salt:13 Amplifier:0-1 Iteration:24576-25600 Candidate.Engine.: Host Generator + PCIe Candidates.#1....: syntasswn -> kumpu Candidates.#2....: jondom -> jerry760 Hardware.Mon.#1..: Temp: 68c Fan: 45% Util:100% Core:1150MHz Mem:2700MHz Bus:16 Hardware.Mon.#2..: N/A   [s]tatus [p]ause [b]ypass [c]heckpoint [f]inish [q]uit =>