hi team, i am very new to this. i found an article online explaining how to use hashcat5.1.0 that i can successfully crack the example passwords. i am trying to crack my own wifi password using it, i have a gtx3090 and an amd5950x cpu. when i run 5.1.0 with the md5 version of my wifi’s .pcap file (that i retrieved with an pwnagotchi) the time remaining is 1 minute then it becomes hours after the first minute is up.
i thought i would download the latest version of haschat but when i try running it (using the command hashcat.exe -m0 -a3 -o cracked.txt hash.txt) , i get the following:
Code:
C:UsersMuratDownloadshashcat-6.2.4hashcat-6.2.4>hashcat.exe -m0 -a3 -o cracked.txt hash.txt
hashcat (v6.2.4) starting
* 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 11.1)
====================
* Device #1: GeForce RTX 3090, 23336/24576 MB, 82MCU
OpenCL API (OpenCL 1.2 CUDA 11.1.96) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: GeForce RTX 3090, skipped
Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256
Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Optimizers applied:
* Zero-Byte
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
* Raw-Hash
ATTENTION! Pure (unoptimized) backend kernels selected.
Pure kernels can crack longer passwords, but drastically reduce performance.
If you want to switch to optimized kernels, append -O to your commandline.
See the above message to find out about the exact limits.
Watchdog: Temperature abort trigger set to 90c
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.
Started: Sat Oct 23 13:54:11 2021
Stopped: Sat Oct 23 13:54:12 2021
can anyone please let me know what i have to do to get it running, and whether its even possible to crack my wifi password (which is only random characters that my isp provided)
thank you
Posts: 16
Threads: 6
Joined: Sep 2021
Hi Muri,
Your command looks a bit funky:
hashcat.exe -m0 -a3 -o cracked.txt hash.txt
Try this instead:
hashcat.exe -a 3 -o cracked.txt hash.txt
Posts: 7
Threads: 1
Joined: Oct 2021
(10-23-2021, 12:43 PM)HostileBlue2020 Wrote: Hi Muri,
Your command looks a bit funky:
hashcat.exe -m0 -a3 -o cracked.txt hash.txt
Try this instead:
hashcat.exe -a 3 -o cracked.txt hash.txt
hello, thanks for your reply. running your command i still get an error:
Code:
C:UsersMuratDownloadshashcat-6.2.4hashcat-6.2.4>hashcat.exe -m0 -a3 -o cracked.txt hash.txt
hashcat (v6.2.4) starting
* 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 11.1)
====================
* Device #1: GeForce RTX 3090, 23336/24576 MB, 82MCU
OpenCL API (OpenCL 1.2 CUDA 11.1.96) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: GeForce RTX 3090, skipped
Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256
Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Optimizers applied:
* Zero-Byte
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
* Raw-Hash
ATTENTION! Pure (unoptimized) backend kernels selected.
Pure kernels can crack longer passwords, but drastically reduce performance.
If you want to switch to optimized kernels, append -O to your commandline.
See the above message to find out about the exact limits.
Watchdog: Temperature abort trigger set to 90c
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.
Started: Sun Oct 24 00:30:53 2021
Stopped: Sun Oct 24 00:30:54 2021
Posts: 16
Threads: 6
Joined: Sep 2021
Muri, are you sure you ran the new command? it looks like you ran the same one again:
C:UsersMuratDownloadshashcat-6.2.4hashcat-6.2.4>hashcat.exe -m0 -a3 -o cracked.txt hash.txt
hashcat (v6.2.4) starting
* 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 11.1)
====================
* Device #1: GeForce RTX 3090, 23336/24576 MB, 82MCU
OpenCL API (OpenCL 1.2 CUDA 11.1.96) — Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: GeForce RTX 3090, skipped
Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256
Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Optimizers applied:
* Zero-Byte
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
* Raw-Hash
ATTENTION! Pure (unoptimized) backend kernels selected.
Pure kernels can crack longer passwords, but drastically reduce performance.
If you want to switch to optimized kernels, append -O to your commandline.
See the above message to find out about the exact limits.
Watchdog: Temperature abort trigger set to 90c
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.
Started: Sun Oct 24 00:30:53 2021
Stopped: Sun Oct 24 00:30:54 2021
Posts: 7
Threads: 1
Joined: Oct 2021
10-24-2021, 01:27 AM
(This post was last modified: 10-24-2021, 01:37 AM by Muri.)
(10-23-2021, 05:39 PM)HostileBlue2020 Wrote: Muri, are you sure you ran the new command? it looks like you ran the same one again:
C:UsersMuratDownloadshashcat-6.2.4hashcat-6.2.4>hashcat.exe -m0 -a3 -o cracked.txt hash.txt
hashcat (v6.2.4) starting* 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 11.1)
====================
* Device #1: GeForce RTX 3090, 23336/24576 MB, 82MCUOpenCL API (OpenCL 1.2 CUDA 11.1.96) — Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: GeForce RTX 3090, skippedMinimum password length supported by kernel: 0
Maximum password length supported by kernel: 256Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotatesOptimizers applied:
* Zero-Byte
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
* Raw-HashATTENTION! Pure (unoptimized) backend kernels selected.
Pure kernels can crack longer passwords, but drastically reduce performance.
If you want to switch to optimized kernels, append -O to your commandline.
See the above message to find out about the exact limits.Watchdog: Temperature abort trigger set to 90c
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.
Started: Sun Oct 24 00:30:53 2021
Stopped: Sun Oct 24 00:30:54 2021
Hi again, you are absolutely right I accidentally ran the same command again without checking, my bad. running the new command now asks me to specify a hash mode. I put my original .pcap file into an md5 converter, which i assume means i need to run «-m0», but the output I now get is:
Code:
C:UsersMuratDownloadshashcat-6.2.4hashcat-6.2.4>hashcat.exe -a 3 -o cracked.txt hash.txt
hashcat (v6.2.4) starting in autodetect mode
* 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 11.1)
====================
* Device #1: GeForce RTX 3090, 23336/24576 MB, 82MCU
OpenCL API (OpenCL 1.2 CUDA 11.1.96) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: GeForce RTX 3090, skipped
The following 11 hash-modes match the structure of your input hash:
# | Name | Category
======+=====================================================+======================================
900 | MD4 | Raw Hash
0 | MD5 | Raw Hash
70 | md5(utf16le($pass)) | Raw Hash
2600 | md5(md5($pass)) | Raw Hash, Salted and/or Iterated
3500 | md5(md5(md5($pass))) | Raw Hash, Salted and/or Iterated
4400 | md5(sha1($pass)) | Raw Hash, Salted and/or Iterated
20900 | md5(sha1($pass).md5($pass).sha1($pass)) | Raw Hash, Salted and/or Iterated
4300 | md5(strtoupper(md5($pass))) | Raw Hash, Salted and/or Iterated
1000 | NTLM | Operating System
9900 | Radmin2 | Operating System
8600 | Lotus Notes/Domino 5 | Enterprise Application Software (EAS)
Please specify the hash-mode with -m [hash-mode].
Started: Sun Oct 24 10:23:37 2021
Stopped: Sun Oct 24 10:23:42 2021
When I add -m 0 (hashcat.exe -m 0 -a 3 -o cracked.txt hash.txt) i receive the same error as in my original post. Would you know a way around this?
thanks so much
Posts: 7
Threads: 1
Joined: Oct 2021
just wanted to add that even when i try to run the benchmark (hashcat.exe -b) i get the following error (where nvrtc: error: invalid value for —gpu-architecture (-arch) is not red)
C:UsersMuratDownloadshashcat-6.2.4hashcat-6.2.4>hashcat.exe -b
hashcat (v6.2.4) 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 11.1)
====================
* Device #1: GeForce RTX 3090, 23336/24576 MB, 82MCU
OpenCL API (OpenCL 1.2 CUDA 11.1.96) — Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: GeForce RTX 3090, skipped
Benchmark 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.
Started: Sun Oct 24 10:53:51 2021
Stopped: Sun Oct 24 10:53:52 2021
Posts: 46
Threads: 1
Joined: Apr 2018
10-24-2021, 04:56 AM
(This post was last modified: 10-24-2021, 04:57 AM by CUwindows00.)
Hi…
.pcap is the new 22000 mode
hashcat -m22000 -a3 cracked.txt ?d?d?d?d?d?d?d?d
Posts: 46
Threads: 1
Joined: Apr 2018
Try like this
hashcat -O -m0 -a3 -o cracked.txt hash.txt
Posts: 7
Threads: 1
Joined: Oct 2021
would anyone know how to overcome this error?
thanks
Posts: 624
Threads: 13
Joined: Sep 2017
(10-25-2021, 06:44 AM)Muri Wrote: would anyone know how to overcome this error?
thanks
-m 0 ist MD5
so you tell hashcat you want to crack MD5, wlan mode is 22000, so this is your first error in your commandline and therefore hahscat will not start cracking because it knwos, that your provided hash doesnt fit
first of all, update all your drivers
most recent cuda version is 11.5
you can tell hahscat to use cudabackend only by adding options (in your case)
-D 2 -d 1
Describe the bug
Hashcat fails to start in cuda mode with GeForce 3060 — the new LHR version
Works when started in opencl mode with —backend-ignore-cuda
Tried with cuda sdk 9.1, 11.3, and 11.0
I also tried to compile from github, but i got the same error.
To Reproduce
run ./hashcat -b
Expected behavior
to work
Hardware/Compute device (please complete the following information):
- Compute device name: NVIDIA GeForce RTX 3060
- OpenCL/CUDA driver name: NVIDIA DRIVER
- OpenCL/CUDA driver version: 470.42.01
- OpenCL/CUDA driver source: runtime installer
Hashcat version (please complete the following information):
- OS: Linux
- Distribution: Ubuntu 18.04
- Version: 6.2.0
- Also tried with compiled from github master. Error is the same
Diagnostic output compute devices:
hashcat (v6.2.2-58-gb30d55c5d) 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.
CUDA API (CUDA 11.4)
====================
* Device #1: NVIDIA GeForce RTX 3060, 11937/12053 MB, 28MCU
OpenCL API (OpenCL 3.0 CUDA 11.4.56) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: NVIDIA GeForce RTX 3060, skipped
Benchmark relevant options:
===========================
* --optimized-kernel-enable
Hashmode: 0 - MD5
nvrtcCompileProgram(): NVRTC_ERROR_INVALID_OPTION
nvrtc: error: invalid value for --gpu-architecture (-arch)
* Device #1: Kernel /home/user/hashcat_github/OpenCL/shared.cl build failed.
* Device #1: Kernel /home/user/hashcat_github/OpenCL/shared.cl build failed.
Started: Sat Jun 26 14:41:33 2021
Stopped: Sat Jun 26 14:41:34 2021
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.42.01 Driver Version: 470.42.01 CUDA Version: 11.4 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 NVIDIA GeForce ... On | 00000000:07:00.0 On | N/A |
| 30% 36C P0 27W / 170W | 14MiB / 12053MiB | 0% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=============================================================================|
| 0 N/A N/A 1039 G /usr/lib/xorg/Xorg 12MiB |
+-----------------------------------------------------------------------------+
hashcat (v6.2.2-58-gb30d55c5d) starting in backend information mode
CUDA Info:
==========
CUDA.Version.: 11.4
Backend Device ID #1 (Alias: #2)
Name...........: NVIDIA GeForce RTX 3060
Processor(s)...: 28
Clock..........: 1777
Memory.Total...: 12053 MB
Memory.Free....: 11937 MB
PCI.Addr.BDFe..: 0000:07:00.0
OpenCL Info:
============
OpenCL Platform ID #1
Vendor..: NVIDIA Corporation
Name....: NVIDIA CUDA
Version.: OpenCL 3.0 CUDA 11.4.56
Backend Device ID #2 (Alias: #1)
Type...........: GPU
Vendor.ID......: 32
Vendor.........: NVIDIA Corporation
Name...........: NVIDIA GeForce RTX 3060
Version........: OpenCL 3.0 CUDA
Processor(s)...: 28
Clock..........: 1777
Memory.Total...: 12053 MB (limited to 3013 MB allocatable in one block)
Memory.Free....: 11904 MB
OpenCL.Version.: OpenCL C 1.2
Driver.Version.: 470.42.01
PCI.Addr.BDF...: 07:00.0
Additional context
nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2020 NVIDIA Corporation
Built on Thu_Jun_11_22:26:38_PDT_2020
Cuda compilation tools, release 11.0, V11.0.194
Build cuda_11.0_bu.TC445_37.28540450_0
2 changed files with 28 additions and 5 deletions
-
3
include/types.h -
30
src/backend.c
@ -1557,6 +1557,9 @@ typedef struct backend_ctx |
||||
|
||||
// cuda |
||||
|
||||
int rc_cuda_init; |
||||
int rc_nvrtc_init; |
||||
|
||||
int nvrtc_driver_version; |
||||
int cuda_driver_version; |
||||
|
||||
|
@ -4935,8 +4935,7 @@ int backend_ctx_init (hashcat_ctx_t *hashcat_ctx) |
||||
|
||||
if (rc_cuda_init == -1) |
||||
{ |
||||
event_log_warning (hashcat_ctx, "Failed to initialize NVIDIA CUDA library."); |
||||
event_log_warning (hashcat_ctx, NULL); |
||||
backend_ctx->rc_cuda_init = rc_cuda_init; |
||||
|
||||
cuda_close (hashcat_ctx); |
||||
} |
||||
@ -4953,8 +4952,7 @@ int backend_ctx_init (hashcat_ctx_t *hashcat_ctx) |
||||
|
||||
if (rc_nvrtc_init == -1) |
||||
{ |
||||
event_log_warning (hashcat_ctx, "Failed to initialize NVIDIA RTC library."); |
||||
event_log_warning (hashcat_ctx, NULL); |
||||
backend_ctx->rc_nvrtc_init = rc_nvrtc_init; |
||||
|
||||
nvrtc_close (hashcat_ctx); |
||||
} |
||||
@ -6269,7 +6267,29 @@ int backend_ctx_devices_init (hashcat_ctx_t *hashcat_ctx, const int comptime) |
||||
{ |
||||
if (user_options->backend_ignore_cuda == false) |
||||
{ |
||||
event_log_warning (hashcat_ctx, "* Device #%u: CUDA SDK Toolkit installation NOT detected.", device_id + 1); |
||||
if (backend_ctx->rc_cuda_init == -1) |
||||
{ |
||||
event_log_warning (hashcat_ctx, "Failed to initialize NVIDIA CUDA library."); |
||||
event_log_warning (hashcat_ctx, NULL); |
||||
} |
||||
else |
||||
{ |
||||
event_log_warning (hashcat_ctx, "Successfully initialized NVIDIA CUDA library."); |
||||
event_log_warning (hashcat_ctx, NULL); |
||||
} |
||||
|
||||
if (backend_ctx->rc_nvrtc_init == -1) |
||||
{ |
||||
event_log_warning (hashcat_ctx, "Failed to initialize NVIDIA RTC library."); |
||||
event_log_warning (hashcat_ctx, NULL); |
||||
} |
||||
else |
||||
{ |
||||
event_log_warning (hashcat_ctx, "Successfully initialized NVIDIA RTC library."); |
||||
event_log_warning (hashcat_ctx, NULL); |
||||
} |
||||
|
||||
event_log_warning (hashcat_ctx, "* Device #%u: CUDA SDK Toolkit installation NOT detected or incorrectly installed.", device_id + 1); |
||||
event_log_warning (hashcat_ctx, " CUDA SDK Toolkit installation required for proper device support and utilization"); |
||||
event_log_warning (hashcat_ctx, " Falling back to OpenCL Runtime"); |
||||
|
||||
|
-
Перейти на CTF площадку Игры Кодебай
Выполняйте задания по кибербезопасности в формате CTF и получайте бесценный опыт. Ознакомиться с подробным описанием можно тут.
-
B правой части каждого сообщения есть стрелки ⇧ и ⇩. Не стесняйтесь оценивать ответы. Чтобы автору вопроса закрыть свой тикет, надо выбрать лучший ответ. Просто нажмите значок ✔ в правой части сообщения.
-
#1
А вот собственно и сама ошибка:
* Device #1: WARNING! Kernel exec timeout is not disabled.
This may cause «CL_OUT_OF_RESOURCES» or related errors.
To disable the timeout, see:
Ссылка скрыта от гостей
* Device #2: WARNING! Kernel exec timeout is not disabled.
This may cause «CL_OUT_OF_RESOURCES» or related errors.
To disable the timeout, see:
Ссылка скрыта от гостей
-
Снимок экрана от 2022-08-27 10-01-43.png
14,4 КБ
· Просмотры: 132
-
Снимок экрана от 2022-08-27 10-02-45.png
34,7 КБ
· Просмотры: 36
-
Снимок экрана от 2022-08-27 10-03-21.png
31,9 КБ
· Просмотры: 31
-
Снимок экрана от 2022-08-27 10-03-52.png
34,2 КБ
· Просмотры: 39
-
#2
В интернете нашёл, hashcat issue [github] — эта проблема вероятно связана с тем, что твой ноутбук не поддерживает nvmlDeviceGetFanSpeed(), и охлаждение твоей видеокарты управляется не ей, а hashcat не может контроллировать скорость кулеров по-другому и выбивает такую ошибку. Разработчик пишет, что эта ошибка распространённая, неисправима и рекомендует не использовать ноутбук с hashcat.
-
#3
А вот собственно и сама ошибка:
* Device #1: WARNING! Kernel exec timeout is not disabled.
This may cause «CL_OUT_OF_RESOURCES» or related errors.
To disable the timeout, see:Ссылка скрыта от гостей
* Device #2: WARNING! Kernel exec timeout is not disabled.
This may cause «CL_OUT_OF_RESOURCES» or related errors.
To disable the timeout, see:Ссылка скрыта от гостей
Так написано же что режим 16800 изменили на 22000
попробуй изменить и запустить
-
#4
В интернете нашёл, hashcat issue [github] — эта проблема вероятно связана с тем, что твой ноутбук не поддерживает nvmlDeviceGetFanSpeed(), и охлаждение твоей видеокарты управляется не ей, а hashcat не может контроллировать скорость кулеров по-другому и выбивает такую ошибку. Разработчик пишет, что эта ошибка распространённая, неисправима и рекомендует не использовать ноутбук с hashcat.
почему тогда от процессора тоже не работает? Для процессора тоже необходим кулер или программа без поддержки видюхи не работает?
-
#5
почему тогда от процессора тоже не работает? Для процессора тоже необходим кулер или программа без поддержки видюхи не работает?
Для того что бы работало от процессора, нужно указывать именно процессор -D 3 вроде у тебя