01-05-2025, 10:49 PM
Just wanted to see if there's anything I can do to optimize my system for HC. Here's my benchmark test results. Thank you for helping this noob in advance.
.\hashcat.exe --benchmark -m 15700
hashcat (v6.2.6) 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: 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
* Device #2: 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
CUDA API (CUDA 12.7)
====================
* Device #1: NVIDIA GeForce RTX 4070 SUPER, 11053/12281 MB, 56MCU
OpenCL API (OpenCL 3.0 CUDA 12.7.33) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: NVIDIA GeForce RTX 4070 SUPER, skipped
OpenCL API (OpenCL 3.0 WINDOWS) - Platform #2 [Intel(R) Corporation]
====================================================================
* Device #3: AMD Ryzen 7 5700X3D 8-Core Processor, skipped
Benchmark relevant options:
===========================
* --optimized-kernel-enable
----------------------------------------------------------------
* Hash-Mode 15700 (Ethereum Wallet, SCRYPT) [Iterations: 262144]
----------------------------------------------------------------
Speed.#1.........: 1 H/s (7.71ms) @ Accel:1 Loops:1024 Thr:4 Vec:1
Started: Sun Jan 05 14:25:22 2025
Stopped: Sun Jan 05 14:25:34 2025
.\hashcat.exe --benchmark -m 15700
hashcat (v6.2.6) 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: 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
* Device #2: 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
CUDA API (CUDA 12.7)
====================
* Device #1: NVIDIA GeForce RTX 4070 SUPER, 11053/12281 MB, 56MCU
OpenCL API (OpenCL 3.0 CUDA 12.7.33) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: NVIDIA GeForce RTX 4070 SUPER, skipped
OpenCL API (OpenCL 3.0 WINDOWS) - Platform #2 [Intel(R) Corporation]
====================================================================
* Device #3: AMD Ryzen 7 5700X3D 8-Core Processor, skipped
Benchmark relevant options:
===========================
* --optimized-kernel-enable
----------------------------------------------------------------
* Hash-Mode 15700 (Ethereum Wallet, SCRYPT) [Iterations: 262144]
----------------------------------------------------------------
Speed.#1.........: 1 H/s (7.71ms) @ Accel:1 Loops:1024 Thr:4 Vec:1
Started: Sun Jan 05 14:25:22 2025
Stopped: Sun Jan 05 14:25:34 2025