hashcat Forum › Support › hashcat v
Not enough allocatable device memory on Mac

Threaded Mode
Not enough allocatable device memory on Mac
CheeseMachine Offline
Junior Member
**
Posts: 8
Threads: 2
Joined: Mar 2022
#1
04-05-2022, 11:19 PM
I'm new to Hashcat and am trying to use my Mac's GPU but keep getting this error when using command -d 3 -D 2 -b:

METAL API (Metal 261.13)
========================
* Device #1: Intel(R) Iris(TM) Graphics 6000, skipped

OpenCL API (OpenCL 1.2 (Feb 12 2022 01:56:27)) - Platform #1 [Apple]
====================================================================
* Device #2: Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz, skipped
* Device #3: Intel(R) Iris(TM) Graphics 6100, 704/1536 MB (192 MB allocatable), 48MCU

Benchmark relevant options:
===========================
* --backend-devices=3
* --opencl-device-types=2
* --optimized-kernel-enable

-------------------
* Hash-Mode 0 (MD5)
-------------------

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

---------------------------------------------------------------------------------------------------------------------

My Mac has an Intel HD Graphics 6000.
I tried using -d 1 for device 1 but keep getting a No devices found/left error.


-I returns this:

hashcat (v6.2.5-378-g4f6a1498c) starting in backend information mode

Metal Info:
===========

Metal.Version.: 261.13

Backend Device ID #1
  Type...........: GPU
  Vendor.ID......: 2
  Vendor.........: Apple
  Name...........: Intel(R) Iris(TM) Graphics 6000
  Processor(s)...: 1
  Clock..........: N/A
  Memory.Total...: 1536 MB (limited to 1024 MB allocatable in one block)
  Memory.Free....: 704 MB
  Local.Memory...: 32 KB
  Phys.Location..: built-in
  Feature.Set....: macOS GPU Family 1 v4
  Registry.ID....: 1080
  Max.TX.Rate....: N/A
  GPU.Properties.: headless 0, low-power 1, removable 0

OpenCL Info:
============

OpenCL Platform ID #1
  Vendor..: Apple
  Name....: Apple
  Version.: OpenCL 1.2 (Feb 12 2022 01:56:27)

  Backend Device ID #2
    Type...........: CPU
    Vendor.ID......: 8
    Vendor.........: Intel
    Name...........: Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz
    Version........: OpenCL 1.2
    Processor(s)...: 4
    Clock..........: 2200
    Memory.Total...: 8192 MB (limited to 1024 MB allocatable in one block)
    Memory.Free....: 4064 MB
    Local.Memory...: 32 KB
    OpenCL.Version.: OpenCL C 1.2
    Driver.Version.: 1.1

  Backend Device ID #3
    Type...........: GPU
    Vendor.ID......: 8
    Vendor.........: Intel Inc.
    Name...........: Intel(R) Iris(TM) Graphics 6100
    Version........: OpenCL 1.2
    Processor(s)...: 48
    Clock..........: 1000
    Memory.Total...: 1536 MB (limited to 192 MB allocatable in one block)
    Memory.Free....: 704 MB
    Local.Memory...: 64 KB
    OpenCL.Version.: OpenCL C 1.2
    Driver.Version.: 1.2(Mar 20 2022 20:40:15)

--------------------------------------------------------------------------------------------------------------------------

Is this error simply due to hardware constraints?
Why am I only able to use device 3 (6100) when device 1 (6000) is my actual GPU?
Is 192 MB not enough for any type of crack?
Would using an older version of Hashcat improve performance?

Any additional info would be much appreciated
Find
Reply
Snoopy Offline
Posting Freak
*****
Posts: 883
Threads: 15
Joined: Sep 2017
#2
04-08-2022, 01:44 PM
Device 1 and 3 is all the same, just differs in the used backend (metal vs opencl) so it doesnt really matter

you can try to -D1 -d2 to tell hahscat to use CPU only (on integrated CPU/GPU devices this should be no difference in speed), on the other hand opencl1.2 is really old, the problem is, apple dropped their opencl support some time ago i think

not quite sure whether there is a possibility to update opencl at least to 2.1 with homebrew or similar
Find
Reply
CheeseMachine Offline
Junior Member
**
Posts: 8
Threads: 2
Joined: Mar 2022
#3
04-08-2022, 08:26 PM
(04-08-2022, 01:44 PM)Snoopy Wrote: Device 1 and 3 is all the same, just differs in the used backend (metal vs opencl) so it doesnt really matter

you can try to -D1 -d2 to tell hahscat to use CPU only (on integrated CPU/GPU devices this should be no difference in speed), on the other hand opencl1.2 is really old, the problem is, apple dropped their opencl support some time ago i think

not quite sure whether there is a possibility to update opencl at least to 2.1 with homebrew or similar

I don't think I'm able to update opencl because they no longer support it and the version is attached to my Mac model and os. Apple is now transitioning to Metal, since my device 1 and 3 are the same, do you know why whenever I try to use device 1 I get a No devices found/left error? Does Hashcat even support Metal? Is there a workaround for this?
Find
Reply
Snoopy Offline
Posting Freak
*****
Posts: 883
Threads: 15
Joined: Sep 2017
#4
04-09-2022, 05:01 PM
i think hashcat skips the metal part GPU because of the same problem, not enough ram to run this/an attack ( but im not sure about this)
Find
Reply
ffamax-pitirib Offline
Junior Member
**
Posts: 1
Threads: 0
Joined: Jan 2023
#5
01-06-2023, 06:56 AM
Use older version

Quote:% ~/hashcat-6.2.6/hashcat -b -m 2500 -w 3 -D 2
hashcat (v6.2.6) starting in benchmark mode

* Device #3: Apple's OpenCL drivers (GPU) are known to be unreliable.
            You have been warned.

METAL API (Metal 212.8)
=======================
* Device #1: Intel Iris Pro Graphics, skipped

OpenCL API (OpenCL 1.2 (Jun  8 2020 17:36:15)) - Platform #1 [Apple]
====================================================================
* Device #2: Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz, skipped
* Device #3: Iris Pro, 704/1536 MB (192 MB allocatable), 40MCU

Benchmark relevant options:
===========================
* --opencl-device-types=2
* --workload-profile=3

The plugin 2500 is deprecated and was replaced with plugin 22000. For more details, please read: https://hashcat.net/forum/thread-10253.html

------------------------------------------------------
* Hash-Mode 2500 (WPA-EAPOL-PBKDF2) [Iterations: 4095]
------------------------------------------------------

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

Started: Thu Jan  5 20:54:01 2023
Stopped: Thu Jan  5 20:54:02 2023


% ~/hashcat-5.1.0/hashcat -b -m 2500 -w 3 -D 2
hashcat (v5.1.0) starting in benchmark mode...

OpenCL Platform #1: Apple
=========================
* Device #1: Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz, skipped.
* Device #2: Iris Pro, 384/1536 MB allocatable, 40MCU

Benchmark relevant options:
===========================
* --opencl-device-types=2
* --workload-profile=3

Hashmode: 2500 - WPA-EAPOL-PBKDF2 (Iterations: 4096)

Speed.#2.........:    8396 H/s (74.85ms) @ Accel:16 Loops:8 Thr:512 Vec:1

Started: Thu Jan  5 20:54:12 2023
Stopped: Thu Jan  5 20:54:18 2023
Find
Reply