Using CUDA or not??

[fjastlo]

I'm running into issue with v6.2.2. Installed CUDA and getting mixed error messages and unsure if it is using NVIDIA GPU.

The Green seems to suggest it detected and is using the GPU
But the Red are error messages.

And does the benchmarking looks like about right for an NVIDIA RTX-2080?

Thanks.


--------------------------------------------------------------------

C:\Program Files\Hashcat>hashcat -b

hashcat (v6.2.2) 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.

Successfully initialized NVIDIA CUDA library.

Failed to initialize NVIDIA RTC library.

* Device #1: CUDA SDK Toolkit not installed or incorrectly installed.
            CUDA SDK Toolkit required for proper device support and utilization.
            Falling back to OpenCL runtime.

* 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
OpenCL API (OpenCL 3.0 CUDA 11.4.56) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #1: NVIDIA GeForce RTX 2080, 7360/8192 MB (2048 MB allocatable), 46MCU

Benchmark relevant options:
===========================
* --optimized-kernel-enable

Hashmode: 0 - MD5

Speed.#1.........: 39443.3 MH/s (77.98ms) @ Accel:64 Loops:1024 Thr:1024 Vec:8

Hashmode: 100 - SHA1

Speed.#1.........: 12474.4 MH/s (61.59ms) @ Accel:64 Loops:256 Thr:1024 Vec:1

Hashmode: 1400 - SHA2-256

Speed.#1.........:  5319.2 MH/s (72.27ms) @ Accel:64 Loops:128 Thr:1024 Vec:1

Hashmode: 1700 - SHA2-512

Speed.#1.........:  1565.2 MH/s (61.35ms) @ Accel:2 Loops:1024 Thr:1024 Vec:1

Hashmode: 22000 - WPA-PBKDF2-PMKID+EAPOL (Iterations: 4095)

Speed.#1.........:  616.4 kH/s (76.05ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1

Hashmode: 1000 - NTLM

Speed.#1.........: 70910.1 MH/s (43.24ms) @ Accel:64 Loops:1024 Thr:1024 Vec:8

Hashmode: 3000 - LM

Speed.#1.........: 35610.3 MH/s (86.24ms) @ Accel:1024 Loops:1024 Thr:64 Vec:1

Hashmode: 5500 - NetNTLMv1 / NetNTLMv1+ESS

Speed.#1.........: 36360.8 MH/s (84.57ms) @ Accel:64 Loops:1024 Thr:1024 Vec:2

Hashmode: 5600 - NetNTLMv2

Speed.#1.........:  2700.1 MH/s (71.15ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1

Hashmode: 1500 - descrypt, DES (Unix), Traditional DES

Speed.#1.........:  1411.1 MH/s (67.91ms) @ Accel:32 Loops:1024 Thr:64 Vec:1

Hashmode: 500 - md5crypt, MD5 (Unix), Cisco-IOS $1$ (MD5) (Iterations: 1000)

Speed.#1.........: 16864.5 kH/s (85.50ms) @ Accel:64 Loops:500 Thr:1024 Vec:1

Hashmode: 3200 - bcrypt $2*$, Blowfish (Unix) (Iterations: 32)

Speed.#1.........:    24978 H/s (39.03ms) @ Accel:2 Loops:32 Thr:11 Vec:1

Hashmode: 1800 - sha512crypt $6$, SHA512 (Unix) (Iterations: 5000)

Speed.#1.........:  186.0 kH/s (50.27ms) @ Accel:8 Loops:128 Thr:1024 Vec:1

Hashmode: 7500 - Kerberos 5, etype 23, AS-REQ Pre-Auth

Speed.#1.........:  627.2 MH/s (76.60ms) @ Accel:256 Loops:128 Thr:32 Vec:1

Hashmode: 13100 - Kerberos 5, etype 23, TGS-REP

Speed.#1.........:  615.8 MH/s (78.01ms) @ Accel:256 Loops:128 Thr:32 Vec:1

Hashmode: 15300 - DPAPI masterkey file v1 (Iterations: 23999)

Speed.#1.........:  100.6 kH/s (79.63ms) @ Accel:16 Loops:256 Thr:1024 Vec:1

Hashmode: 15900 - DPAPI masterkey file v2 (Iterations: 12899)

Speed.#1.........:    57072 H/s (63.20ms) @ Accel:2 Loops:512 Thr:1024 Vec:1

Hashmode: 7100 - macOS v10.8+ (PBKDF2-SHA512) (Iterations: 1023)

Speed.#1.........:  734.0 kH/s (50.58ms) @ Accel:4 Loops:255 Thr:1024 Vec:1

Hashmode: 11600 - 7-Zip (Iterations: 16384)

Speed.#1.........:  617.2 kH/s (73.48ms) @ Accel:4 Loops:4096 Thr:1024 Vec:1

Hashmode: 12500 - RAR3-hp (Iterations: 262144)

Speed.#1.........:    71662 H/s (81.88ms) @ Accel:16 Loops:16384 Thr:128 Vec:1

Hashmode: 13000 - RAR5 (Iterations: 32799)

Speed.#1.........:    63863 H/s (89.21ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1

Hashmode: 6211 - TrueCrypt RIPEMD160 + XTS 512 bit (Iterations: 1999)

Speed.#1.........:  472.0 kH/s (101.25ms) @ Accel:64 Loops:32 Thr:1024 Vec:1

Hashmode: 13400 - KeePass 1 (AES/Twofish) and KeePass 2 (AES) (Iterations: 24569)

Speed.#1.........:    38539 H/s (203.58ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1

Hashmode: 6800 - LastPass + LastPass sniffed (Iterations: 499)

Speed.#1.........:  4124.1 kH/s (87.88ms) @ Accel:8 Loops:499 Thr:1024 Vec:1

Hashmode: 11300 - Bitcoin/Litecoin wallet.dat (Iterations: 200459)

Speed.#1.........:    7544 H/s (63.63ms) @ Accel:2 Loops:1024 Thr:1024 Vec:1

Started: Tue Jul 06 22:50:35 2021
Stopped: Tue Jul 06 22:54:37 2021

[atom]

The CUDA SDK is not installed correctly. One has to understand that there's a difference between:

- NVIDIA CUDA library
- NVIDIA RTC library

The NVIDIA CUDA library comes with the CUDA SDK, but also with the NVIDIA Driver.

The NVIDIA RTC library comes with the CUDA SDK alone. If the install is not completed correctly, hashcat can't use CUDA. Maybe you had unticked it during installation options menu.

Hashcat felt back to OpenCL because the CUDA SDK is not installed correctly, this is why you see this:

OpenCL API (OpenCL 3.0 CUDA 11.4.56)

Because the NV Driver also ships with an OpenCL API. The NV OpenCL API replaces the NVRTC because it ships with it's on JiT compiler. This JiT compiler creates the PTX code similar to NVRTC does. It's good enough for the CUDA library to take over after JiT compile phase, which is why in this case NV CUDA library is enough and hashcat can start.

However, using CUDA specific architecture the NVRTC can compile more efficient code than the OpenCL JiT, which is why you should stick to the CUDA NVRTC. So you need to fix your CUDA SDK installation.

[TheAleph]

I'm running into issue with v6.2.2. Installed CUDA and getting mixed error messages and unsure if it is using NVIDIA GPU.

The Green seems to suggest it detected and is using the GPU
But the Red are error messages.

And does the benchmarking looks like about right for an NVIDIA RTX-2080?

Thanks.


--------------------------------------------------------------------

C:\Program Files\Hashcat>hashcat -b

hashcat (v6.2.2) 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.

Successfully initialized NVIDIA CUDA library.

Failed to initialize NVIDIA RTC library.

* Device #1: CUDA SDK Toolkit not installed or incorrectly installed.
            CUDA SDK Toolkit required for proper device support and utilization.
            Falling back to OpenCL runtime.

* 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
OpenCL API (OpenCL 3.0 CUDA 11.4.56) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #1: NVIDIA GeForce RTX 2080, 7360/8192 MB (2048 MB allocatable), 46MCU

Benchmark relevant options:
===========================
* --optimized-kernel-enable

Hashmode: 0 - MD5

Speed.#1.........: 39443.3 MH/s (77.98ms) @ Accel:64 Loops:1024 Thr:1024 Vec:8

Hashmode: 100 - SHA1

Speed.#1.........: 12474.4 MH/s (61.59ms) @ Accel:64 Loops:256 Thr:1024 Vec:1

Hashmode: 1400 - SHA2-256

Speed.#1.........:  5319.2 MH/s (72.27ms) @ Accel:64 Loops:128 Thr:1024 Vec:1

Hashmode: 1700 - SHA2-512

Speed.#1.........:  1565.2 MH/s (61.35ms) @ Accel:2 Loops:1024 Thr:1024 Vec:1

Hashmode: 22000 - WPA-PBKDF2-PMKID+EAPOL (Iterations: 4095)

Speed.#1.........:  616.4 kH/s (76.05ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1

Hashmode: 1000 - NTLM

Speed.#1.........: 70910.1 MH/s (43.24ms) @ Accel:64 Loops:1024 Thr:1024 Vec:8

Hashmode: 3000 - LM

Speed.#1.........: 35610.3 MH/s (86.24ms) @ Accel:1024 Loops:1024 Thr:64 Vec:1

Hashmode: 5500 - NetNTLMv1 / NetNTLMv1+ESS

Speed.#1.........: 36360.8 MH/s (84.57ms) @ Accel:64 Loops:1024 Thr:1024 Vec:2

Hashmode: 5600 - NetNTLMv2

Speed.#1.........:  2700.1 MH/s (71.15ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1

Hashmode: 1500 - descrypt, DES (Unix), Traditional DES

Speed.#1.........:  1411.1 MH/s (67.91ms) @ Accel:32 Loops:1024 Thr:64 Vec:1

Hashmode: 500 - md5crypt, MD5 (Unix), Cisco-IOS $1$ (MD5) (Iterations: 1000)

Speed.#1.........: 16864.5 kH/s (85.50ms) @ Accel:64 Loops:500 Thr:1024 Vec:1

Hashmode: 3200 - bcrypt $2*$, Blowfish (Unix) (Iterations: 32)

Speed.#1.........:    24978 H/s (39.03ms) @ Accel:2 Loops:32 Thr:11 Vec:1

Hashmode: 1800 - sha512crypt $6$, SHA512 (Unix) (Iterations: 5000)

Speed.#1.........:  186.0 kH/s (50.27ms) @ Accel:8 Loops:128 Thr:1024 Vec:1

Hashmode: 7500 - Kerberos 5, etype 23, AS-REQ Pre-Auth

Speed.#1.........:  627.2 MH/s (76.60ms) @ Accel:256 Loops:128 Thr:32 Vec:1

Hashmode: 13100 - Kerberos 5, etype 23, TGS-REP

Speed.#1.........:  615.8 MH/s (78.01ms) @ Accel:256 Loops:128 Thr:32 Vec:1

Hashmode: 15300 - DPAPI masterkey file v1 (Iterations: 23999)

Speed.#1.........:  100.6 kH/s (79.63ms) @ Accel:16 Loops:256 Thr:1024 Vec:1

Hashmode: 15900 - DPAPI masterkey file v2 (Iterations: 12899)

Speed.#1.........:    57072 H/s (63.20ms) @ Accel:2 Loops:512 Thr:1024 Vec:1

Hashmode: 7100 - macOS v10.8+ (PBKDF2-SHA512) (Iterations: 1023)

Speed.#1.........:  734.0 kH/s (50.58ms) @ Accel:4 Loops:255 Thr:1024 Vec:1

Hashmode: 11600 - 7-Zip (Iterations: 16384)

Speed.#1.........:  617.2 kH/s (73.48ms) @ Accel:4 Loops:4096 Thr:1024 Vec:1

Hashmode: 12500 - RAR3-hp (Iterations: 262144)

Speed.#1.........:    71662 H/s (81.88ms) @ Accel:16 Loops:16384 Thr:128 Vec:1

Hashmode: 13000 - RAR5 (Iterations: 32799)

Speed.#1.........:    63863 H/s (89.21ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1

Hashmode: 6211 - TrueCrypt RIPEMD160 + XTS 512 bit (Iterations: 1999)

Speed.#1.........:  472.0 kH/s (101.25ms) @ Accel:64 Loops:32 Thr:1024 Vec:1

Hashmode: 13400 - KeePass 1 (AES/Twofish) and KeePass 2 (AES) (Iterations: 24569)

Speed.#1.........:    38539 H/s (203.58ms) @ Accel:4 Loops:1024 Thr:1024 Vec:1

Hashmode: 6800 - LastPass + LastPass sniffed (Iterations: 499)

Speed.#1.........:  4124.1 kH/s (87.88ms) @ Accel:8 Loops:499 Thr:1024 Vec:1

Hashmode: 11300 - Bitcoin/Litecoin wallet.dat (Iterations: 200459)

Speed.#1.........:    7544 H/s (63.63ms) @ Accel:2 Loops:1024 Thr:1024 Vec:1

Started: Tue Jul 06 22:50:35 2021
Stopped: Tue Jul 06 22:54:37 2021

Hi,

i have had the same issue and I'm still having it each time i download a new release from git.

The problem is happening only on windows.
I have reported it perviously the issue and the solution which wil only affect windows builds only.
To solve the problem you have to rebuild the source doing the code modification shown on the following post:

https://hashcat.net/forum/thread-9342.html

If you know howto build hashcat from source you can try with this. I'm almost sure yor problem will be fxed.

Hope this can be useful for you.

[atom]

Keep in mind that there's no need to recompile anything from source, or even the need to change the source. If you have a clean install everything will work out of the box.

[TheAleph]

Testing the CUDA installation is easy, you need only to run the cuda samples to verify if all is fine.
On the other hand on windows the cuda installation is straightforward, you just have to give the installation path and maybe you need to uninstall the previous version first.

[fadedmaple]

Keep in mind that there's no need to recompile anything from source, or even the need to change the source. If you have a clean install everything will work out of the box.

I have similar problem with the latest 471.11 driver and CUDA toolkit 11.4 installed. All 7 demo suites come with CUDA like deviceQuery.exe nbody.exe works well. 

Code:

PS C:\Users\XXX> $Env:CUDA_PATH
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.4

nvtrc64_112_0.dll is in the bin folder, I tried to make a copy and rename it to nvtrc64.dll but  still doesn't work.

https://hashcat.net/forum/thread-9818.html CUDA SDK Toolkit NOT detected - Win 10
https://hashcat.net/forum/thread-9342.html Question about --force option and CUDA Toolkit SDK

[TheAleph]

Keep in mind that there's no need to recompile anything from source, or even the need to change the source. If you have a clean install everything will work out of the box.

I have similar problem with the latest 471.11 driver and CUDA toolkit 11.4 installed. All 7 demo suites come with CUDA like deviceQuery.exe nbody.exe works well. 

Code:

PS C:\Users\XXX> $Env:CUDA_PATH
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.4

nvtrc64_112_0.dll is in the bin folder, I tried to make a copy and rename it to nvtrc64.dll but  still doesn't work.

https://hashcat.net/forum/thread-9818.html CUDA SDK Toolkit NOT detected - Win 10
https://hashcat.net/forum/thread-9342.html Question about --force option and CUDA Toolkit SDK

Hi,

keep in mind that as on the post i have said, ths is a fast and dirty slution just to verify and maybe run hashcat on windows if you have this probkem. It is not by far a solution to the probkem.

Try rename it to nvtrc.dll

[fadedmaple]

Keep in mind that there's no need to recompile anything from source, or even the need to change the source. If you have a clean install everything will work out of the box.

I have similar problem with the latest 471.11 driver and CUDA toolkit 11.4 installed. All 7 demo suites come with CUDA like deviceQuery.exe nbody.exe works well. 

Code:

PS C:\Users\XXX> $Env:CUDA_PATH
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.4

nvtrc64_112_0.dll is in the bin folder, I tried to make a copy and rename it to nvtrc64.dll but  still doesn't work.

https://hashcat.net/forum/thread-9818.html      CUDA SDK Toolkit NOT detected - Win 10
https://hashcat.net/forum/thread-9342.html      Question about --force option and CUDA Toolkit SDK

Hi,

keep in mind that as on the post i have said, ths is a fast and dirty slution just to verify and maybe run hashcat on windows if you have this probkem.  It is not by far a solution to the probkem.

Try rename it to nvtrc.dll

I have tried both nvtrc64.dll and nvtrc.dll but useless

[TheAleph]

Keep in mind that there's no need to recompile anything from source, or even the need to change the source. If you have a clean install everything will work out of the box.

I have similar problem with the latest 471.11 driver and CUDA toolkit 11.4 installed. All 7 demo suites come with CUDA like deviceQuery.exe nbody.exe works well. 

Code:

PS C:\Users\XXX> $Env:CUDA_PATH
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.4

nvtrc64_112_0.dll is in the bin folder, I tried to make a copy and rename it to nvtrc64.dll but  still doesn't work.

https://hashcat.net/forum/thread-9818.html      CUDA SDK Toolkit NOT detected - Win 10
https://hashcat.net/forum/thread-9342.html      Question about --force option and CUDA Toolkit SDK

Hi,

keep in mind that as on the post i have said, ths is a fast and dirty slution just to verify and maybe run hashcat on windows if you have this probkem.  It is not by far a solution to the probkem.

Try rename it to nvtrc.dll

I have tried both nvtrc64.dll and nvtrc.dll but useless

Please be carefull with the dll name.
It must be nvrtc.dll and not the name you have written.
I have copied from your previous post but it was wrong. Sorry about that

[fadedmaple]

Keep in mind that there's no need to recompile anything from source, or even the need to change the source. If you have a clean install everything will work out of the box.

I have similar problem with the latest 471.11 driver and CUDA toolkit 11.4 installed. All 7 demo suites come with CUDA like deviceQuery.exe nbody.exe works well. 

Code:

PS C:\Users\XXX> $Env:CUDA_PATH
C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.4

nvtrc64_112_0.dll is in the bin folder, I tried to make a copy and rename it to nvtrc64.dll but  still doesn't work.

https://hashcat.net/forum/thread-9818.html      CUDA SDK Toolkit NOT detected - Win 10
https://hashcat.net/forum/thread-9342.html      Question about --force option and CUDA Toolkit SDK

Hi,

keep in mind that as on the post i have said, ths is a fast and dirty slution just to verify and maybe run hashcat on windows if you have this probkem.  It is not by far a solution to the probkem.

Try rename it to nvtrc.dll

I have tried both nvtrc64.dll and nvtrc.dll but useless

Please be carefull with the dll name.
It must be nvrtc.dll and not the name you have written.
I have copied from your previous post but it was wrong. Sorry about that

Actually I just deleted the suffix instead type it, never mind