I get CL_OUT_OF_RESOURCES with -m 15700/ethereum

[svobodnui11]

Please help me, why do I get such a mistake? tell me what to do, have already reviewed everything on the forum, 2 months can not return the password to the wallet, nerves at the limit, I really need help, thank you in advance

C:\hashcat>hashcat64.exe -m 15700 -b
hashcat (v4.0.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.

* Device #1: WARNING! Kernel exec timeout is not disabled.
             This may cause "CL_OUT_OF_RESOURCES" or related errors.
             To disable the timeout, see: https://hashcat.net/q/timeoutpatch
nvmlDeviceSetPowerManagementLimit(): Insufficient Permissions

OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: GeForce GTX 1060 6GB, 1536/6144 MB allocatable, 10MCU

OpenCL Platform #2: Intel(R) Corporation
========================================
* Device #2: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, skipped.

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

Hashmode: 15700 - Ethereum Wallet, SCRYPT

clWaitForEvents(): CL_OUT_OF_RESOURCES

clEnqueueWriteBuffer(): CL_OUT_OF_RESOURCES

Started: Sun Oct 29 19:24:08 2017
Stopped: Sun Oct 29 19:24:18 2017

C:\hashcat>

[philsmd]

The cost factor (and memory needed) for ethereum/scrypt is too high for your GPU.
Try to use -D 1 and therefore run hashcat with your CPU.

[svobodnui11]

The cost factor (and memory needed) for ethereum/scrypt is too high for your GPU.
Try to use -D 1 and therefore run hashcat with your CPU.

C:\hashcat>hashcat64.exe -m 15700 -D 1 -b

hashcat (v4.0.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.



* Device #2: Outdated or broken Intel OpenCL runtime detected!



You are STRONGLY encouraged to use the officially supported NVIDIA driver.

See hashcat.net for officially supported NVIDIA drivers.

See also: https://hashcat.net/faq/wrongdriver

You can use --force to override this, but do not report related errors.



Started: Sun Oct 29 19:33:30 2017

Stopped: Sun Oct 29 19:33:30 2017


C:\hashcat>

[svobodnui11]

The cost factor (and memory needed) for ethereum/scrypt is too high for your GPU.
Try to use -D 1 and therefore run hashcat with your CPU.

Is my GTX 1060 6GB small? I thought this top-end video card

[philsmd]

please also apply the timeout patch (https://hashcat.net/wiki/doku.php?id=timeout_patch) like the warning says.

For intel CPUs you need to install the OpenCL driver (not the SDK).

[svobodnui11]

please also apply the timeout patch (https://hashcat.net/wiki/doku.php?id=timeout_patch) like the warning says.

For intel CPUs you need to install the OpenCL driver (not the SDK).

I can not find this driver for the i7 3770, Is my GTX 1060 6GB version 387.92, I also put cuda_9.0.176_win10 and NVIDIA_SDK_9.52.0324.0405 and intel_aocl_setup_7.0.0.2519 , it's Windows 10, I still have 5 amd rx 470

I installed the patch, thanks, but did not help
intel_aocl_setup_7.0.0.2519 can it be it?


C:\hashcat>hashcat64.exe -D1 -b
hashcat (v4.0.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.

* Device #2: Outdated or broken Intel OpenCL runtime detected!

You are STRONGLY encouraged to use the officially supported NVIDIA driver.
See hashcat.net for officially supported NVIDIA drivers.
See also: https://hashcat.net/faq/wrongdriver
You can use --force to override this, but do not report related errors.

Started: Sun Oct 29 19:41:34 2017
Stopped: Sun Oct 29 19:41:35 2017

[philsmd]

do not install the cuda sdk.

For the intel OpenCL driver, follow this link: https://software.intel.com/en-us/article...PU_runtime (and as already said, you do not need the SDK, but just the driver/Runtime)

[svobodnui11]

do not install the cuda sdk.

For the intel OpenCL driver, follow this link: https://software.intel.com/en-us/article...PU_runtime (and as already said, you do not need the SDK, but just the driver/Runtime)

install - Latest release (16.1.1)

• OpenCL™ Runtime 16.1.1 for Intel® Core™ and Intel® Xeon® Processors for Windows* (64-bit & 32-bit)
  but not help. help please, I will thank
  

C:\hashcat>hashcat64.exe -D1 -b
hashcat (v4.0.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.

* Device #2: Outdated or broken Intel OpenCL runtime detected!

You are STRONGLY encouraged to use the officially supported NVIDIA driver.
See hashcat.net for officially supported NVIDIA drivers.
See also: https://hashcat.net/faq/wrongdriver
You can use --force to override this, but do not report related errors.

Started: Sun Oct 29 19:53:20 2017
Stopped: Sun Oct 29 19:53:20 2017

[svobodnui11]

do not install the cuda sdk.

For the intel OpenCL driver, follow this link: https://software.intel.com/en-us/article...PU_runtime (and as already said, you do not need the SDK, but just the driver/Runtime)

the topic is closed? (((I can write you a private message, I'm sorry for the text, it is translated by Google translator, there may be errors

[svobodnui11]

do not install the cuda sdk.

For the intel OpenCL driver, follow this link: https://software.intel.com/en-us/article...PU_runtime (and as already said, you do not need the SDK, but just the driver/Runtime)

i do what you recomended but i have this error

C:\hashcat>hashcat64.exe -m 15700 -b -D 1 -O
hashcat (v4.0.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: NVIDIA Corporation
======================================
* Device #1: GeForce GTX 1060 6GB, skipped.

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

Benchmark relevant options:
===========================
* --opencl-device-types=1
* --optimized-kernel-enable

Hashmode: 15700 - Ethereum Wallet, SCRYPT

* Device #2: ATTENTION! OpenCL kernel self-test failed.

Your device driver installation is probably broken.
See also: https://hashcat.net/faq/wrongdriver

Speed.Dev.#2.....:        0 H/s (774.24ms)