+- 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: device memory allocation (/thread-10965.html)
device memory allocation - antzfarm - 08-15-2022
hashcat issue
os: Windows 10
issue: I try to crack md5 hashes and or any other hash and the following error message pops up:
c:\User\hashcat>hashcat -m900 [hash] hugewordlist.txt
hashcat (v6.2.5) starting
ADL2_New_QueryPMLogData_Get is missing from ADL shared library.
OpenCL API (OpenCL 2.0 AMD-APP (1800.11)) - Platform #1 [Advanced Micro Devices, Inc.]
======================================================================================
* Device #1: AMD Mobility Radeon HD 5000 Series, 384/512 MB (192 MB allocatable), 2MCU
* Device #2: , 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
Rules: 1
Optimizers applied:
* Zero-Byte
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* 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: Hardware monitoring interface not found on your system.
Watchdog: Temperature abort trigger disabled.
* Device #1: Not enough allocatable device memory for this attack.
Started: Mon Aug 15 21:35:25 2022
Stopped: Mon Aug 15 21:35:28 2022
What can be done so that I may be able to use hashcat?
RE: device memory allocation - Snoopy - 08-16-2022
* Device #1: AMD Mobility Radeon HD 5000 Series, 384/512 MB (192 MB allocatable), 2MCU
* Device #1: Not enough allocatable device memory for this attack.
your gpu isnt capable of running this or any other attack due to limited gpu ram, only 192 MB are free for use, mobil chips are not made for cracking
you can try to stick to CPU (lower performance) this way hashcat can use your ram (which should be more then 192mb free)
see output of
Code:
hashcat -D1 -b -m0