clCreateContext(): CL_OUT_OF_HOST_MEMORY

[aperson]

I have tried from post suggestion to increase on the virtual memory but didn't work
I also tried the 6.1.1 but it won't run at all, hope some expert can provide some help or hint what i should look into to resolve the memory error

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: Fri Apr 09 17:12:11 2021
Stopped: Fri Apr 09 17:12:11 2021

C:\hashcat-5.1.0>hashcat32.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, 511/511 MB allocatable, 48MCU

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

Hashmode: 0 - MD5

clCreateContext(): CL_OUT_OF_HOST_MEMORY

Started: Fri Apr 09 17:25:49 2021
Stopped: Fri Apr 09 17:25:49 2021

C:\hashcat-5.1.0>

[aperson]

I have found this under window event log, any idea
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: hashcat.exe
P2: 0.0.0.0
P3: 5f214d91
P4: KERNELBASE.dll
P5: 10.0.17763.1790
P6: c97af40a
P7: c06d007e
P8: 0000000000039689
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1B46.tmp.WERInternalMetadata.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_hashcat.exe_d65583901db2c6645ea04482e1d6d3c6d5f4934_fcafdaf0_0fac6d3c

Analysis symbol:
Rechecking for solution: 0
Report Id: 2a58614b-9efd-4cd1-9d0d-2d6c1f89ba3d
Report Status: 4196
Hashed bucket:
Cab Guid: 0

[Snoopy]

for short the error means the follwoing

RE: clCreateContext(): CL_OUT_OF_HOST_MEMORY
Device #1: Intel(R) Xeon(R) Gold 6226 CPU @ 2.70GHz, 511/511 MB allocatable, 48MCU

you / hashcat has not enough RAM to go for this attack, server / xeon CPU with just 512 MB RAM seems really strange to me, try to add some more RAM

[aperson]

this server has 32G MB RAM，and only 10GB/32GB used, is anyways to force use more memory?

C:\>systeminfo
OS Name: Microsoft Windows Server 2019 Standard
OS Version: 10.0.17763 N/A Build 17763
OS Build Type: Multiprocessor Free
System Manufacturer: HPE
System Model: ProLiant DL380 Gen10
System Type: x64-based PC
Processor(s): 2 Processor(s) Installed.
[01]: Intel64 Family 6 Model 85 Stepping 7 GenuineIntel ~2694 Mhz
[02]: Intel64 Family 6 Model 85 Stepping 7 GenuineIntel ~2694 Mhz
BIOS Version: HPE U30, 2020/3/9
Total Physical Memory: 65,193 MB
Available Physical Memory: 53,595 MB
Virtual Memory: Max Size: 74,238 MB
Virtual Memory: Available: 62,559 MB
Virtual Memory: In Use: 11,679 MB

[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

[Snoopy]

try newest beta from 
https://hashcat.net/beta/

and start it with option -D 1, telling hahscvt to use your cpu

i tried your commandline and i get
Host memory required for this attack: 104 MB
so there must be another problem with your setup/maschine

sometimes windows dont like running such programms straight from C:, do you have a second partition? try it there

[aperson]

Tried as running the newest beta in D: and seems still the same error

D:\test\hashcat-6.1.1+245\hashcat-6.1.1>dir
Volume in drive D is New Volume
Volume Serial Number is 3A9E-994E

Directory of D:\test\hashcat-6.1.1+245\hashcat-6.1.1

2021/04/20 15:04 <DIR> .
2021/04/20 15:04 <DIR> ..
2021/04/20 13:41 <DIR> charsets
2021/04/20 13:41 <DIR> docs
2021/04/19 16:44 1,069,601 example.dict
2021/04/19 16:44 67 example0.cmd
2021/04/19 16:44 214,302 example0.hash
2021/04/19 16:44 61 example0.sh
2021/04/19 16:44 63 example400.cmd
2021/04/19 16:44 35 example400.hash
2021/04/19 16:44 56 example400.sh
2021/04/19 16:44 56 example500.cmd
2021/04/19 16:44 35 example500.hash
2021/04/19 16:44 50 example500.sh
2021/04/20 13:41 <DIR> extra
2021/04/19 16:44 1,087,704 hashcat.bin
2021/04/19 16:44 1,284,608 hashcat.exe
2021/04/19 16:44 240,526 hashcat.hcstat2
2021/04/19 16:44 30,722 hashcat.hctune
2021/04/20 13:41 <DIR> layouts
2021/04/20 13:41 <DIR> masks
2021/04/20 13:46 <DIR> modules
2021/04/20 13:55 <DIR> OpenCL
2021/04/20 13:56 <DIR> rules
2021/04/07 18:07 42 temp.txt
15 File(s) 3,927,928 bytes
10 Dir(s) 176,515,080,192 bytes free

D:\test\hashcat-6.1.1+245\hashcat-6.1.1>hashcat.exe -I
hashcat (v6.1.1-245-g8e47fdf8f) starting...

clCreateContext(): CL_OUT_OF_HOST_MEMORY

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

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

Backend 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.Total...: 65193 MB (limited to 16298 MB allocatable in one block)
Memory.Free....: 0 MB
OpenCL.Version.: OpenCL C 2.0
Driver.Version.: 2020.11.11.0.13_160000


D:\test\hashcat-6.1.1+245\hashcat-6.1.1>hashcat.exe -b
hashcat (v6.1.1-245-g8e47fdf8f) 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.

clCreateContext(): CL_OUT_OF_HOST_MEMORY

OpenCL API (OpenCL 2.1 WINDOWS) - Platform #1 [Intel(R) Corporation]
====================================================================
* Device #1: Intel(R) Xeon(R) Gold 6226 CPU @ 2.70GHz, skipped

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

Hashmode: 0 - MD5
Hashmode: 100 - SHA1
Hashmode: 1400 - SHA2-256
Hashmode: 1700 - SHA2-512
Hashmode: 22000 - WPA-PBKDF2-PMKID+EAPOL (Iterations: 4095)
Hashmode: 1000 - NTLM
Hashmode: 3000 - LM
Hashmode: 5500 - NetNTLMv1 / NetNTLMv1+ESS
Hashmode: 5600 - NetNTLMv2
Hashmode: 1500 - descrypt, DES (Unix), Traditional DES
Hashmode: 500 - md5crypt, MD5 (Unix), Cisco-IOS $1$ (MD5) (Iterations: 1000)
Hashmode: 3200 - bcrypt $2*$, Blowfish (Unix) (Iterations: 32)
Hashmode: 1800 - sha512crypt $6$, SHA512 (Unix) (Iterations: 5000)
Hashmode: 7500 - Kerberos 5, etype 23, AS-REQ Pre-Auth
Hashmode: 13100 - Kerberos 5, etype 23, TGS-REP
Hashmode: 15300 - DPAPI masterkey file v1 (Iterations: 23999)
Hashmode: 15900 - DPAPI masterkey file v2 (Iterations: 12899)
Hashmode: 7100 - macOS v10.8+ (PBKDF2-SHA512) (Iterations: 1023)
Hashmode: 11600 - 7-Zip (Iterations: 16384)
Hashmode: 12500 - RAR3-hp (Iterations: 262144)
Hashmode: 13000 - RAR5 (Iterations: 32799)
Hashmode: 6211 - TrueCrypt RIPEMD160 + XTS 512 bit (Iterations: 1999)
Hashmode: 13400 - KeePass 1 (AES/Twofish) and KeePass 2 (AES) (Iterations: 24569)
Hashmode: 6800 - LastPass + LastPass sniffed (Iterations: 499)
Hashmode: 11300 - Bitcoin/Litecoin wallet.dat (Iterations: 200459)
Started: Tue Apr 20 15:05:36 2021
Stopped: Tue Apr 20 15:05:50 2021

D:\test\hashcat-6.1.1+245\hashcat-6.1.1>hashcat.exe -D 1 -m 22 temp.txt
hashcat (v6.1.1-245-g8e47fdf8f) starting...

clCreateContext(): CL_OUT_OF_HOST_MEMORY

OpenCL API (OpenCL 2.1 WINDOWS) - Platform #1 [Intel(R) Corporation]
====================================================================
* Device #1: Intel(R) Xeon(R) Gold 6226 CPU @ 2.70GHz, skipped

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

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

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

ATTENTION! Pure (unoptimized) backend kernels selected.
Using pure kernels enables cracking longer passwords but for the price of drastically reduced performance.
If you want to switch to optimized backend 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.

Started: Tue Apr 20 15:06:12 2021
Stopped: Tue Apr 20 15:06:12 2021

D:\test\hashcat-6.1.1+245\hashcat-6.1.1>

[Snoopy]

Memory.Total...: 65193 MB (limited to 16298 MB allocatable in one block)
Memory.Free....: 0 MB

dont know why, but it seems your whole ram is consumed by antoher process, what kind of computer is this? virtual maschine?

[kolotovalexander]

How to solve this problem? The graphics card does not work computing on a GTX 660 graphics card. Sometimes zaupskaetsya without error . But most often this clCreateContext(): CL_OUT_OF_HOST_MEMORY error appears.

nvmlDeviceGetCurrPcieLinkWidth(): Not Supported

nvmlDeviceGetClockInfo(): Not Supported

nvmlDeviceGetClockInfo(): Not Supported

nvmlDeviceGetTemperatureThreshold(): Not Supported

nvmlDeviceGetTemperatureThreshold(): Not Supported

nvmlDeviceGetUtilizationRates(): Not Supported

OpenCL API (OpenCL 3.0 CUDA 11.4.264) - Platform #1 [NVIDIA Corporation]
========================================================================
* Device #1: NVIDIA GeForce GTX 660, 1152/1536 MB (384 MB allocatable), 6MCU

OpenCL API (OpenCL 2.1 WINDOWS) - Platform #2 [Intel(R) Corporation]
====================================================================
* Device #2: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz, 8140/16344 MB (2043 MB allocatable), 4MCU

Minimum password length supported by kernel: 8
Maximum password length supported by kernel: 63

C:\Users\kolotovalexander\Documents\wifi\wordlist\leaked_email_2014.txt: Byte Order Mark (BOM) was detected
Hashes: 5 digests; 5 unique digests, 2 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1

Optimizers applied:
* Zero-Byte
* Slow-Hash-SIMD-LOOP

Watchdog: Temperature abort trigger set to 90c

INFO: Removed 2 hashes found as potfile entries.

clCreateContext(): CL_OUT_OF_HOST_MEMORY

Host memory required for this attack: 1 MB

Dictionary cache hit:
* Filename..: C:\Users\kolotovalexander\Documents\wifi\wordlist\wifimaps-wordlist.dic
* Passwords.: 257469
* Bytes.....: 3279514
* Keyspace..: 257469




[s]tatus [p]ause [b]ypass [c]heckpoint [f]inish [q]uit => Finished autotune


Session..........: hashcat
Status...........: Quit
Hash.Mode........: 22000 (WPA-PBKDF2-PMKID+EAPOL)
Hash.Target......: C:\Users\kolotovalexander\Documents\wifi\file\31175_1665558966.hc22000
Time.Started.....: Wed Oct 12 11:40:50 2022 (1 sec)
Time.Estimated...: Wed Oct 12 11:41:36 2022 (45 secs)
Kernel.Feature...: Pure Kernel
Guess.Base.......: File (C:\Users\kolotovalexander\Documents\wifi\wordlist\wifimaps-wordlist.dic)
Guess.Queue......: 1/36 (2.78%)
Speed.#2.........:    5622 H/s (90.10ms) @ Accel:1024 Loops:512 Thr:1 Vec:4
Speed.#*.........:    5622 H/s
Recovered........: 2/5 (40.00%) Digests (total), 0/5 (0.00%) Digests (new), 1/2 (50.00%) Salts
Progress.........: 0/514938 (0.00%)
Rejected.........: 0/0 (0.00%)
Restore.Point....: 0/257469 (0.00%)
Restore.Sub.#2...: Salt:0 Amplifier:0-1 Iteration:0-3
Candidate.Engine.: Device Generator
Candidates.#2....: !!!!!!!! -> ("kalipso"
Hardware.Mon.#2..: N/A

[Snoopy]

clCreateContext(): CL_OUT_OF_HOST_MEMORY
the error tells, that your device has not emough free ram to run this attack

anyway, it seems your cuda sdk isnt installed properly, as hashcat does a fallback to opencl, install cuda sdk 11.6 from nvidia homepage DONT 11.7, as this version seems to be a troublemaker on such old hardware, so please stick to 11.6

hashcat -I should show you something like this when everthing is okay

y:\hashcat>hashcat -I
hashcat (v6.2.6-41-g88d5540c4) starting in backend information mode

CUDA Info:
==========

CUDA.Version.: 11.6

Backend Device ID #1 (Alias: #3)
Name...........: NVIDIA GeForce GTX 1050 Ti
Processor(s)...: 6
Clock..........: 1417
Memory.Total...: 4095 MB
Memory.Free....: 3376 MB
Local.Memory...: 48 KB
PCI.Addr.BDFe..: 0000:05:00.0

Backend Device ID #2 (Alias: #4)
Name...........: NVIDIA GeForce GTX 1050 Ti
Processor(s)...: 6
Clock..........: 1430
Memory.Total...: 4095 MB
Memory.Free....: 3227 MB
Local.Memory...: 48 KB
PCI.Addr.BDFe..: 0000:06:00.0