Increasing single-block device memory allocatable for --scrypt-tmto 1 / clCreateBuffe
#1
Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 1.
clCreateBuffer(): CL_OUT_OF_HOST_MEMORY

it's okay, but there are problems when starting up, when enabled -D1 everything was fine, decided -D1,2 and started to throw this error, after the back -D1 error remained, preload does not help / CPU i7 3770 RAM 16gb

hashcat64.exe -1 ?l?u -a3 -D1 -m15700 $ethereum$s*262144*8*1*ff3ce6cd147186e..13306acbef8be8b0a1f45..14dc4e7b514df58f385d030a*b6c9e8f85085207a..813032bf1447faf24521434290..ba8fa48f0ded3663ff*7646c81e80e..6d8049a67607b8f11b89cb0e2f020d6b8da7852c..5ec9420ff ?1rypto?h?h?h?h --status --status-timer=5 -w3 --force
hashcat (v4.1.0) starting...

OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
* Device #1: Ellesmere, skipped.
* Device #2: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 4086/16344 MB allocatable, 8MCU

OpenCL Platform #2: Intel(R) Corporation
========================================
* Device #3: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 4086/16344 MB allocatable, 8MCU

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
* Single-Hash
* Single-Salt
* Brute-Force

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

Watchdog: Temperature abort trigger set to 90c

Increasing single-block device memory allocatable for --scrypt-tmto 1.
Increasing single-block device memory allocatable for --scrypt-tmto 1.
clCreateBuffer(): CL_OUT_OF_HOST_MEMORY

Started: Sun Mar 11 22:31:24 2018
Stopped: Sun Mar 11 22:31:28 2018
#2
I'm shocked, on the version v4.0.1 2017.11.07 everything is in order, but earlier I could use the function -D1,2