+- 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: CUDA SDK Toolkit NOT detected - Win 10 (/thread-9818.html)
Pages:
1
2
RE: CUDA SDK Toolkit NOT detected - Win 10 - w41l3r - 06-09-2023
I know its been a long long time, but... for the sake of science.. I've solved this problem here as follows:
- download/install CUDA (https://developer.nvidia.com/cuda-downloads)
- on a privileged powershell, execute (filenames will depend on your cuda version) :
PS> copy "C:\program files\NVIDIA GPU Computing Toolkit\CUDA\v12.1\bin\nvrtc64_120_0.dll" "C:\windows\system32\nvrtc64.dll"
PS> copy "C:\program files\NVIDIA GPU Computing Toolkit\CUDA\v12.1\bin\nvrtc64_120_0.dll" "C:\windows\system32\nvrtc.dll"
PS> copy "C:\program files\NVIDIA GPU Computing Toolkit\CUDA\v12.1\bin\nvrtc-builtins64_121.dll" c:\windows\system32\
have fun!
RE: CUDA SDK Toolkit NOT detected - Win 10 - banky228 - 09-27-2023
thank you alot man. i struggling so hard
my speed of GPU was like 850-950 kH/s before found your forum
now it's up to ~1600-1800 kH/s
i wondering do it possible to run cuda as AMD CPUs chipset.
i'm going to go learning process about it
btw thanks
RE: CUDA SDK Toolkit NOT detected - Win 10 - skola28 - 11-07-2023
(06-09-2023, 08:20 PM)w41l3r Wrote: I know its been a long long time, but... for the sake of science.. I've solved this problem here as follows:
- download/install CUDA (https://developer.nvidia.com/cuda-downloads)
- on a privileged powershell, execute (filenames will depend on your cuda version) :
...
PS> copy "C:\program files\NVIDIA GPU Computing Toolkit\CUDA\v12.1\bin\nvrtc-builtins64_121.dll" c:\windows\system32\
Just registered to ensure you know you're a legend.
Cut my time in half.I also wanted to post that the final file in your list (referenced in the quote above) has a different filename in v12.3.
FWIW, in v12.3 the final finalname is nvrtc-builtins64_123.dll
RE: CUDA SDK Toolkit NOT detected - Win 10 - Artifice - 02-06-2024
(06-09-2023, 08:20 PM)w41l3r Wrote: I know its been a long long time, but... for the sake of science.. I've solved this problem here as follows:
- download/install CUDA (https://developer.nvidia.com/cuda-downloads)
- on a privileged powershell, execute (filenames will depend on your cuda version) :
PS> copy "C:\program files\NVIDIA GPU Computing Toolkit\CUDA\v12.1\bin\nvrtc64_120_0.dll" "C:\windows\system32\nvrtc64.dll"
PS> copy "C:\program files\NVIDIA GPU Computing Toolkit\CUDA\v12.1\bin\nvrtc64_120_0.dll" "C:\windows\system32\nvrtc.dll"
PS> copy "C:\program files\NVIDIA GPU Computing Toolkit\CUDA\v12.1\bin\nvrtc-builtins64_121.dll" c:\windows\system32\
have fun!
You are absolute lifesaver. I was banging my head against the desk trying to find why this wasn't working until I tried this.
RE: CUDA SDK Toolkit NOT detected - Win 10 - duansq - 04-26-2024
Is there a way to use it in win11? I followed the tutorial and copied C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.4\bin, but it didn’t work.
C:\windows\system32\nvrtc64.dll
C:\windows\system32\nvrtc.dll
C:\windows\system32\nvrtc-builtins64_124.dll
Windows11 3060Ti CUDA12.4
错误：./OpenCL/m17400_a0-optimized.cl: Pure kernel not found, falling back to optimized kernel
Windows11 3060Ti CUDA12.4
D:\Zm\hashcat>hashcat -m17400 -a0 1 2
hashcat (v6.2.6) starting
CUDA API (CUDA 12.4)
====================
* Device #1: NVIDIA GeForce RTX 3060 Ti, 7128/8191 MB, 38MCU
OpenCL API (OpenCL 3.0 CUDA 12.4.89) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: NVIDIA GeForce RTX 3060 Ti, skipped
./OpenCL/m17400_a0-optimized.cl: Pure kernel not found, falling back to optimized kernel
Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 31
INFO: All hashes found as potfile and/or empty entries! Use --show to display them.
Started: Sat Apr 27 03:38:12 2024
Stopped: Sat Apr 27 03:38:12 2024
RE: CUDA SDK Toolkit NOT detected - Win 10 - duansq - 04-27-2024
I have already resolved it, it doesn't seem like it was a mistake