clCreateContext(): CL_OUT_OF_HOST_MEMORY

[aperson]

I found out the reason why it shows 512MB at earlier test, it is because hashcat run under the 32.exe, if I used 64.exe, it used more RAM but still prompts with clCreateContext(): CL_OUT_OF_HOST_MEMORY, it anyways to know how many RAM hashcat will it need for my system to run

C:\hashcat-5.1.0>hashcat64.exe -I
hashcat (v5.1.0) starting...

OpenCL Info:

Platform ID #1
Vendor : Intel(R) Corporation
Name : Intel(R) OpenCL
Version : OpenCL 2.1 WINDOWS

Device ID #1
Type : CPU
Vendor ID : 8
Vendor : Intel(R) Corporation
Name : Intel(R) Xeon(R) Gold 6226 CPU @ 2.70GHz
Version : OpenCL 2.1 (Build 0)
Processor(s) : 48
Clock : 2700
Memory : 16298/65193 MB allocatable
OpenCL Version : OpenCL C 2.0
Driver Version : 2020.11.11.0.13_160000


C:\hashcat-5.1.0>hashcat64.exe -b
hashcat (v5.1.0) starting in benchmark mode...

Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.

OpenCL Platform #1: Intel(R) Corporation
========================================
* Device #1: Intel(R) Xeon(R) Gold 6226 CPU @ 2.70GHz, 16298/65193 MB allocatable, 48MCU

Benchmark relevant options:
===========================
* --optimized-kernel-enable

Hashmode: 0 - MD5

clCreateContext(): CL_OUT_OF_HOST_MEMORY

Started: Mon Apr 12 09:09:57 2021
Stopped: Mon Apr 12 09:09:58 2021

C:\hashcat-5.1.0>hashcat64.exe -m 22 temp.txt -a 3 ?l
hashcat (v5.1.0) starting...

OpenCL Platform #1: Intel(R) Corporation
========================================
* Device #1: Intel(R) Xeon(R) Gold 6226 CPU @ 2.70GHz, 16298/65193 MB allocatable, 48MCU

Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates

Applicable optimizers:
* Zero-Byte
* Early-Skip
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
* Raw-Hash

Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256
Minimim salt length supported by kernel: 0
Maximum salt length supported by kernel: 256

ATTENTION! Pure (unoptimized) OpenCL kernels selected.
This enables cracking passwords and salts > length 32 but for the price of drastically reduced performance.
If you want to switch to optimized OpenCL kernels, append -O to your commandline.

Watchdog: Hardware monitoring interface not found on your system.
Watchdog: Temperature abort trigger disabled.

clCreateContext(): CL_OUT_OF_HOST_MEMORY

Started: Mon Apr 12 09:11:18 2021
Stopped: Mon Apr 12 09:11:18 2021

C:\hashcat-5.1.0>hashcat32.exe -m 22 temp.txt -a 3 ?l
hashcat (v5.1.0) starting...

OpenCL Platform #1: Intel(R) Corporation
========================================
* Device #1: Intel(R) Xeon(R) Gold 6226 CPU @ 2.70GHz, 511/511 MB allocatable, 48MCU

Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates

Applicable optimizers:
* Zero-Byte
* Early-Skip
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
* Raw-Hash

Minimum password length supported by kernel: 0
Maximum password length supported by kernel: 256
Minimim salt length supported by kernel: 0
Maximum salt length supported by kernel: 256

ATTENTION! Pure (unoptimized) OpenCL kernels selected.
This enables cracking passwords and salts > length 32 but for the price of drastically reduced performance.
If you want to switch to optimized OpenCL kernels, append -O to your commandline.

Watchdog: Hardware monitoring interface not found on your system.
Watchdog: Temperature abort trigger disabled.

clCreateContext(): CL_OUT_OF_HOST_MEMORY

Started: Mon Apr 12 09:11:40 2021
Stopped: Mon Apr 12 09:11:41 2021