+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: Vega64 clCreateCommandQueue(): CL_OUT_OF_HOST_MEMORY (/thread-8283.html)
Vega64 clCreateCommandQueue(): CL_OUT_OF_HOST_MEMORY - conma293 - 04-04-2019
Have a Vega64, im sure it has worked in the past, but now presents the following error -
c:\hashcat-5.1.0>example400.cmd
c:\hashcat-5.1.0>type example.dict | hashcat64.exe -m 400 example400.hash
hashcat (v5.1.0) starting...
OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
* Device #1: gfx900, 4048/8176 MB allocatable, 64MCU
OpenCL Platform #2: Advanced Micro Devices, Inc.
================================================
* Device #2: gfx900, 4048/8176 MB allocatable, 64MCU
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:
* Zero-Byte
* Single-Hash
* Single-Salt
Minimum password length supported by kernel: 0
Maximum password 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: Temperature abort trigger set to 90c
clCreateCommandQueue(): CL_OUT_OF_HOST_MEMORY
Started: Thu Apr 04 20:20:28 2019
Stopped: Thu Apr 04 20:20:30 2019
The process tried to write to a nonexistent pipe.
c:\hashcat-5.1.0>pause
Press any key to continue . . .
c:\hashcat-5.1.0>example500.cmd
c:\hashcat-5.1.0>hashcat64.exe -m 500 example500.hash example.dict
hashcat (v5.1.0) starting...
OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
* Device #1: gfx900, 4048/8176 MB allocatable, 64MCU
OpenCL Platform #2: Advanced Micro Devices, Inc.
================================================
* Device #2: gfx900, 4048/8176 MB allocatable, 64MCU
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:
* Zero-Byte
* Single-Hash
* Single-Salt
Minimum password length supported by kernel: 0
Maximum password 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: Temperature abort trigger set to 90c
clCreateCommandQueue(): CL_OUT_OF_HOST_MEMORY
Started: Thu Apr 04 20:20:43 2019
Stopped: Thu Apr 04 20:20:53 2019
c:\hashcat-5.1.0>pause
Press any key to continue . . .
c:\hashcat-5.1.0>example0.cmd
c:\hashcat-5.1.0>hashcat64.exe -t 32 -a 7 example0.hash ?a?a?a?a example.dict
hashcat (v5.1.0) starting...
OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
* Device #1: gfx900, 4048/8176 MB allocatable, 64MCU
OpenCL Platform #2: Advanced Micro Devices, Inc.
================================================
* Device #2: gfx900, 4048/8176 MB allocatable, 64MCU
Dictionary cache hit:
* Filename..: example.dict
* Passwords.: 128416
* Bytes.....: 1069601
* Keyspace..: 128416
Hashes: 6494 digests; 6494 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Applicable optimizers:
* Zero-Byte
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Salt
* Raw-Hash
Minimum password length supported by kernel: 0
Maximum password 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: Temperature abort trigger set to 90c
INFO: Removed 54 hashes found in potfile.
clCreateCommandQueue(): CL_OUT_OF_HOST_MEMORY
Started: Thu Apr 04 20:21:07 2019
Stopped: Thu Apr 04 20:21:10 2019
c:\hashcat-5.1.0>pause
RE: Vega64 clCreateCommandQueue(): CL_OUT_OF_HOST_MEMORY - atom - 04-05-2019
Please retry with the latest beta from https://hashcat.net/beta/
RE: Vega64 clCreateCommandQueue(): CL_OUT_OF_HOST_MEMORY - p96xl - 04-11-2019
(04-05-2019, 04:24 PM)atom Wrote: Please retry with the latest beta from https://hashcat.net/beta/
C:\Users\p96xl\Desktop\hashcat-5.1.0>hashcat64 -I
hashcat (v5.1.0-896-g85d58b03) starting...
clCreateCommandQueue(): CL_OUT_OF_HOST_MEMORY
It wont even let me do -I
(Two Vega FE, but also happens on One)
RE: Vega64 clCreateCommandQueue(): CL_OUT_OF_HOST_MEMORY - atom - 04-14-2019
Another try, did some change. Please retry with the latest beta from https://hashcat.net/beta/
RE: Vega64 clCreateCommandQueue(): CL_OUT_OF_HOST_MEMORY - p96xl - 04-15-2019
(04-14-2019, 07:32 AM)atom Wrote: Another try, did some change. Please retry with the latest beta from https://hashcat.net/beta/
This time I get BSOD error: THREAD_STUCK_IN_DEVICE_DRIVER
I am running AMD driver Radeon Pro Settings Version 2019.0326.2353.42986 since I cant get gaming drivers to work.
edit: I found the reason for the error, amd crossfire was on. Turning off the setting stopped the BSOD, but now my pc turns off probably because of my power supply. (750w Corsair 80+ bronze)
edit 2: nvm, its back