Please note, this is a STATIC archive of website hashcat.net from October 2020, cach3.com does not collect or store any user information, there is no "phishing" involved.

hashcat Forum

Full Version: "Not enough allocatable device memory for this attack."
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hey Guys,
so i saw a post on Twitter - a person was able to obtain 102 GH/s on a 2080ti.

i wanted to emulate this on my 4x1080 build, but i am a rookie in this, and i'm getting an error:

Quote:C:\Hashcat>hashcat64.exe -m 1000 -b -u 1024 -n 512 --opencl-vector-width 8 --force -O -w 4
hashcat (v5.1.0) starting in benchmark mode...

OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: GeForce GTX 1080, 2048/8192 MB allocatable, 20MCU
* Device #2: GeForce GTX 1080, 2048/8192 MB allocatable, 20MCU
* Device #3: GeForce GTX 1080, 2048/8192 MB allocatable, 20MCU
* Device #4: GeForce GTX 1080, 2048/8192 MB allocatable, 20MCU

Benchmark relevant options:
===========================
* --force
* --optimized-kernel-enable
* --opencl-vector-width=8
* --kernel-accel=512

Hashmode: 1000 - NTLM

* Device #1: Not enough allocatable device memory for this attack.

Started: Wed Jun 19 01:25:00 2019
Stopped: Wed Jun 19 01:25:04 2019

Can i get any assistance in understanding what i'm doing wrong/what is missing and how i can get the most out of my machine?

The specs are:
Windows 10 Pro 64-bit
CPU X 2 -Intel Xeon v4 @ 2.10GHz (Broadwell-E/EP 14nm Technology)
RAM - 32.0GB Dual-Channel Unknown @ 1066MHz (15-15-15-35)
Motherboard - Supermicro X10DRG-Q
Graphics X4 - 4095MB NVIDIA GeForce GTX 1080 (PNY)
Storage -  3726GB Hitachi HGST HUS724040ALA640 (SATA) 25 °C

Thank you!
You don't have enough VRAM for the tuning parameters you specified. GTX 1080 only has 8GB VRAM, whereas RTX 2080 Ti has 11GB VRAM.
Just do not use -n, then hashcat will automatically find a value which is within the available GPU memory.