![]() |
Using my hardware correctly? - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Support (https://hashcat.net/forum/forum-3.html) +--- Forum: hashcat (https://hashcat.net/forum/forum-45.html) +--- Thread: Using my hardware correctly? (/thread-10221.html) |
Using my hardware correctly? - Marcolator - 07-21-2021 Hello After trying to update drivers etc. i went from ~500 H/s to ~40.000 H/s, but that still seems kinda low.. As far as I can see, it is only running on 1 of my GPU's and not on my CPU at all. How can that be, am i doing something wrong or is my hardware just not strong enough? * Device #3: Unstable OpenCL driver detected! This OpenCL driver may fail kernel compilation or produce false negatives. You can use --force to override, but do not report related errors. nvmlDeviceGetFanSpeed(): Not Supported CUDA API (CUDA 11.4) ==================== * Device #1: NVIDIA GeForce MX150, 1661/2048 MB, 3MCU OpenCL API (OpenCL 3.0 CUDA 11.4.56) - Platform #1 [NVIDIA Corporation] ======================================================================= * Device #2: NVIDIA GeForce MX150, skipped OpenCL API (OpenCL 2.1 ) - Platform #2 [Intel(R) Corporation] ============================================================= * Device #3: Intel(R) UHD Graphics 620, skipped OpenCL API (OpenCL 2.1 WINDOWS) - Platform #3 [Intel(R) Corporation] ==================================================================== * Device #4: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz, skipped Minimum password length supported by kernel: 8 Maximum password length supported by kernel: 63 Hashes: 4 digests; 2 unique digests, 1 unique salts Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates Optimizers applied: * Zero-Byte * Single-Salt * Brute-Force * Slow-Hash-SIMD-LOOP Watchdog: Temperature abort trigger set to 90c Host memory required for this attack: 52 MB Session..........: hashcat Status...........: Running Hash.Name........: WPA-EAPOL-PBKDF2 Hash.Target......: capture.hccapx Time.Started.....: Wed Jul 21 00:57:59 2021 (3 mins, 15 secs) Time.Estimated...: Wed Dec 20 07:50:58 2023 (2 years, 152 days) Kernel.Feature...: Pure Kernel Guess.Mask.......: ?u?l?l?l?l?l?d?d?d?d [10] Guess.Queue......: 1/1 (100.00%) Speed.#1.........: 40522 H/s (148.55ms) @ Accel:64 Loops:128 Thr:1024 Vec:1 Recovered........: 0/2 (0.00%) Digests Progress.........: 7864320/3089157760000 (0.00%) Rejected.........: 0/7864320 (0.00%) Restore.Point....: 196608/118813760000 (0.00%) Restore.Sub.#1...: Salt:0 Amplifier:14-15 Iteration:1152-1280 Candidate.Engine.: Device Generator Candidates.#1....: Nfvyta1234 -> Nbtsza1234 Hardware.Mon.#1..: Temp: 72c Util: 98% Core:1649MHz Mem:2504MHz Bus:4 RE: Using my hardware correctly? - Snoopy - 07-21-2021 first see https://hashcat.net/forum/thread-7717.html ,your kind of attack is considered to be outdated (mode 2500) second, try using options -D 1,2 -O this will tell hashcat to use CPU and GPU together with optimized kernel third, hashrate depends on hashmode and attack, you can use hashcat -D 1,2 -b -m 2500 to see your "very maximum speed" example output Speed.#1.........: 95898 H/s (45.44ms) @ Accel:8 Loops:512 Thr:1024 Vec:1 Speed.#2.........: 123.9 kH/s (46.01ms) @ Accel:64 Loops:64 Thr:1024 Vec:1 Speed.#5.........: 4776 H/s (71.94ms) @ Accel:128 Loops:512 Thr:1 Vec:4 Speed.#6.........: 5099 H/s (65.56ms) @ Accel:128 Loops:512 Thr:1 Vec:4 Speed.#*.........: 229.7 kH/s i think your rate is quite okay for this "old gpu" |