+- 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: Not enough allocatable device memory for this attack (/thread-10730.html)
Not enough allocatable device memory for this attack - BowenD - 04-20-2022
Hello guys,
How are you?
I just have this error when i used hashcat..
hashcat --user hash.txt ~/rockyou.txt
hashcat (v6.2.5) starting in autodetect mode
OpenCL API (OpenCL 2.0 pocl 1.8 Linux, None+Asserts, RELOC, LLVM 11.1.0, SLEEF, DISTRO, POCL_DEBUG) - Platform #1 [The pocl project]
=====================================================================================================================================
* Device #1: pthread-Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, 708/1480 MB (256 MB allocatable), 4MCU
Hash-mode was not specified with -m. Attempting to auto-detect hash mode.
The following mode was auto-detected as the only one matching your input hash:
400 | phpass | Generic KDF
NOTE: Auto-detect is best effort. The correct hash-mode is NOT guaranteed!
Do NOT report auto-detect issues unless you are certain of the hash type.
Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256
Hashes: 2 digests; 2 unique digests, 2 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1
Optimizers applied:
* Zero-Byte
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
* Device #1: Not enough allocatable device memory for this attack.
Started: Wed Apr 20 16:31:20 2022
Stopped: Wed Apr 20 16:31:58 2022
How do I solve it?
RE: Not enough allocatable device memory for this attack - Snoopy - 04-21-2022
well it seems you are on a vps or something similar?
1.5 GB RAM in total seems very odd in these days, i mean for sure, every consumer laptop nowadays has minimum 4 to 8 gb
cracking hashes needs power, storage and ram, real power (at least one dedicated gpu would be great)
you could try adding option -O to use optimized kernel, but im not sure if this helps
RE: Not enough allocatable device memory for this attack - BowenD - 04-22-2022
(04-21-2022, 01:35 PM)Snoopy Wrote: well it seems you are on a vps or something similar?
1.5 GB RAM in total seems very odd in these days, i mean for sure, every consumer laptop nowadays has minimum 4 to 8 gb
cracking hashes needs power, storage and ram, real power (at least one dedicated gpu would be great)
you could try adding option -O to use optimized kernel, but im not sure if this helps
Hello Snoopy,
Yes i am using The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) linux in VMware..
Is it because hashcat did not detect my host computer's RAM?
kind regards
RE: Not enough allocatable device memory for this attack - Snoopy - 04-22-2022
(04-22-2022, 08:12 AM)BowenD Wrote: Hello Snoopy,
Yes i am using The-Distribution-Which-Does-Not-Handle-OpenCL-Well (The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali)) linux in VMware..
Is it because hashcat did not detect my host computer's RAM?
kind regards
i think you created your vm with standard settings, given this your vm has probably 2 gb in ram only , if you are running this on your own machine, modify your vm settings and adding more ram to it
RE: Not enough allocatable device memory for this attack - hetcat - 08-06-2022
hello forum,
my windows 10 laptop is also showing the identical problem.. ...any solution for this... guide me . thanks for the help.
C:\hashcat625>hashcat.exe -O -w 2 -m 9400 -a 3 "C:\hashcat625\index-hash.txt" -i --increment-min 6 --increment-max 10 ?l?l?l?l?l?l?l?l?l?l
hashcat (v6.2.5) starting
OpenCL API (OpenCL 1.2 ) - Platform #1 [Intel(R) Corporation]
=============================================================
* Device #1: Intel(R) HD Graphics 4400, 768/1629 MB (203 MB allocatable), 20MCU
* Device #2: Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz, skipped
Kernel ./OpenCL/m09400-optimized.cl:
Optimized kernel requested, but not available or not required
Falling back to pure kernel
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
* Single-Hash
* Single-Salt
* Brute-Force
* Slow-Hash-SIMD-LOOP
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: Sat Aug 06 21:36:45 2022
Stopped: Sat Aug 06 21:36:47 2022
RE: Not enough allocatable device memory for this attack - b8vr - 08-06-2022
Your mask is way to big. You don't have enough memory to contain all the candidates. Try with --increment-max 9 or 8 although this is still a lot of candidates. Maybe you should not increment at all.
RE: Not enough allocatable device memory for this attack - Snoopy - 08-08-2022
(08-06-2022, 06:44 PM)hetcat Wrote: hashcat (v6.2.5) starting
OpenCL API (OpenCL 1.2 ) - Platform #1 [Intel(R) Corporation]
=============================================================
Next Thing, OpenCL 1.2 is way to old, use at least 2.1, install this opencl driver from intel
*ttp://registrationcenter-download.intel.com/akdlm/irc_nas/vcp/13794/opencl_runtime_18.1_x64_setup.msi