hashcat Forum

Full Version: invalid value for --gpu-architecture
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I am an AI/ML researcher in the field of finance technologies therefore previously had installed CUDA.
When I run hashcat in benchmark mode "hashcat -b", every single method (MD5, Hash Mode xxxx) returns this:


Code:
hashcat (v6.2.6) starting in benchmark modeBenchmarking 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
Device #1: NVIDIA GeForce RTX 3060 Laptop GPU, 5136/6143 MB, 30MCUOpenCL API (OpenCL 3.0 CUDA 12.3.106) - 
Platform #1 [NVIDIA Corporation]

========================================================================
* Device #2: NVIDIA GeForce RTX 3060 Laptop GPU, skippedOpenCL API (OpenCL 3.0 ) - Platform #2 [Intel(R) Corporation]

=============================================================* 

Device #3: Intel(R) UHD Graphics, 3168/6450 MB (1612 MB allocatable), 32MCUBenchmark relevant options:
===========================* 
--optimized-kernel-enable-------------------*
Hash-Mode 0 (MD5)-------------------

nvrtcCompileProgram(): NVRTC_ERROR_INVALID_OPTION
nvrtc: error: invalid value for --gpu-architecture (-arch)
* Device #1: Kernel ./OpenCL/shared.cl build failed.
* Device #1: Kernel ./OpenCL/shared.cl build failed.
I use GTX 3060 Laptop, have properly selected the device, 

-My CUDA Toolkit version is 10.1
-I use Game Ready Driver 546.29
-Nvidia SMI is properly installed

Why would this happen?
Should my CUDA Toolkit be up to date, the same API that my GR Driver uses?
How can I fix it?
This is a toolkit/driver mismatch. Your driver is FAR newer than your toolkit version from what you've posted. You should be on toolkit 12.3update1 with a driver that new.
This solved my problem:
(12-05-2023, 09:35 AM)Chick3nman Wrote: [ -> ]This is a toolkit/driver mismatch. Your driver is FAR newer than your toolkit version from what you've posted. You should be on toolkit 12.3update1 with a driver that new.


+rep