hashcat Forum

Full Version: Error hipDeviceGetCount(): 100
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hello.
I have hashcat v6.2.6 and NVIDIA GeForce RTX 3050 Laptop GPU and AMD Ryzen 5 5600H with Radeon Graphics.
I have an error:


Code:
hashcat (v6.2.6) starting

hipDeviceGetCount(): 100

nvmlDeviceGetFanSpeed(): Not Supported

CUDA API (CUDA 11.8)
====================
* Device #1: NVIDIA GeForce RTX 3050 Laptop GPU, 3328/4095 MB, 16MCU

OpenCL API (OpenCL 3.0 CUDA 11.8.88) - Platform #1 [NVIDIA Corporation]
=======================================================================
* Device #2: NVIDIA GeForce RTX 3050 Laptop GPU, skipped

Minimum password length supported by kernel: 8
Maximum password length supported by kernel: 63

Hashfile 'sergeevamv.hccapx' on line 1 (HCPX♦): Separator unmatched
Hashfile 'sergeevamv.hccapx' on line 2 (): Separator unmatched
Hashfile 'sergeevamv.hccapx' on line 3 (): Separator unmatched
Hashfile 'sergeevamv.hccapx' on line 4 (): Separator unmatched
Hashfile 'sergeevamv.hccapx' on line 5 (): Separator unmatched
No hashes loaded.


Can you please tell me how I can fix this error?
Thank you!
I have CUDA Toolkit.
Check your hashes with example https://hashcat.net/wiki/doku.php?id=example_hashes

Paste here your command.
wpa

hashcat.exe -m 2500 -a 3 proba.hccapx '7?d?d?d?d?d?d'
--------------
hipDeviceGetCount(): 100
nvmlDeviceGetFanSpeed(): Not Supported
...
The plugin 2500 is deprecated and was replaced with plugin 22000. For more details, please read: https://hashcat.net/forum/thread-10253.html
---------------

Then... hashcat.exe -m 22000 -a 3 proba.hccapx '7?d?d?d?d?d?d'
-------
hipDeviceGetCount(): 100
nvmlDeviceGetFanSpeed(): Not Supported
...
No hashes loaded.
---------

if - hashcat.exe -m 22000 -a 3 proba.cap '7?d?d?d?d?d?d'

-----
Hashfile 'proba.cap' on line 189841 (): Separator unmatched

* Token length exception: 4/4 hashes
  This error happens if the wrong hash type is specified, if the hashes are
  malformed, or if input is otherwise not as expected (for example, if the
  --username option is used but no username is present)
-------
You're using old methods. See the hcxtools thread to learn the proper way to capture WPA hashes now.
Thank you for the information.
I understand that. I'm researching the information now...
I use airodump-ng for handshake (file.cap)

Then converting the file:
hcxpcapngtool -o 303.hc22000 file.cap
https://hashcat.net/wiki/doku.php?id=cracking_wpawpa2

Then:
hashcat.exe -m 22000 -a 303.hc22000 '5?d?d?'
It seems to work. Am I doing everything right?

However, information always appears:
hipDeviceGetCount(): 100
nvmlDeviceGetFanSpeed(): Not Supported
aircrack-ng suite might not take advantage of all capture methods (I haven't used it in ages so can't relate to if its been updated or not with PMKID) Eitherway, hcxdumptool is a more effective way of capturing data. If you're not familiar with it you can always use scripts such as wifite2 to automate the process for you.

As for the errors...

Code:
hipDeviceGetCount(): 100
nvmlDeviceGetFanSpeed(): Not Supported

This would be relating to just your CPU's onboard graphics which I am assuming you are not using. It should not have any impact on the cracking process it is strictly just informing you of the drivers details.
(02-03-2023, 07:48 PM)slyexe Wrote: [ -> ]aircrack-ng suite might not take advantage of all capture methods (I haven't used it in ages so can't relate to if its been updated or not with PMKID) Eitherway, hcxdumptool is a more effective way of capturing data. If you're not familiar with it you can always use scripts such as wifite2 to automate the process for you.



As for the errors...



Code:
hipDeviceGetCount(): 100

nvmlDeviceGetFanSpeed(): Not Supported



This would be relating to just your CPU's onboard graphics which I am assuming you are not using. It should not have any impact on the cracking process it is strictly just informing you of the drivers details.





Thanks for the information! Thank you for your response!