CL_INVALID_BINARY
#1
But i figure out some problem here...

When I use benckmark, I got this:

D:\hashcat\hashcat-3.10>hashcat64.exe -b -m 2500
hashcat (v3.10) starting in benchmark-mode...

OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
- Device #1: Tahiti, 2112/3072 MB allocatable, 32MCU
- Device #2: Tahiti, 2112/3072 MB allocatable, 32MCU
- Device #3: WARNING: Not a native Intel OpenCL runtime, expect massive speed loss
You can use --force to override this but do not post error reports if you do so
- Device #3: Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz, skipped

OpenCL Platform #2: Intel(R) Corporation
========================================
- Device #4: Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz, skipped



ERROR: clCreateProgramWithBinary(): CL_INVALID_BINARY

Not just 2500, all hashtype benchmark with this same error.

I use AMD 7990 with radeon 16.6.
#2
(08-22-2016, 12:22 PM)tonyvg Wrote: But i figure out some problem here...

When I use benckmark, I got this:

D:\hashcat\hashcat-3.10>hashcat64.exe -b -m 2500
hashcat (v3.10) starting in benchmark-mode...

OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
- Device #1: Tahiti, 2112/3072 MB allocatable, 32MCU
- Device #2: Tahiti, 2112/3072 MB allocatable, 32MCU
- Device #3: WARNING: Not a native Intel OpenCL runtime, expect massive speed loss
            You can use --force to override this but do not post error reports if you do so
- Device #3:         Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz, skipped

OpenCL Platform #2: Intel(R) Corporation
========================================
- Device #4:         Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz, skipped



ERROR: clCreateProgramWithBinary(): CL_INVALID_BINARY

Not just 2500, all hashtype benchmark with this same error.

I use AMD 7990 with radeon 16.6.

The frist time I ran benckmark, hashcat stuck the system.
Then I reboot and ran again, I got CL_INVALID_BINARY.
And I delete the old copy and decompress again, it stuck agian, and reboot got a CL_INVALID_BINARY.
#3
Looks like AMD completely destroyed it now. Please use AMD driver 15.12 exact, not 16.6. This is not a hashcat problem.
#4
I am also getting a CL_INVALID_BINARY error:

C:\MyData\Downloads\hashcat-3.10\hashcat-3.10>hashcat64 -a 3 -m 12000 -o lookhere.txt --outfile-format=3 -1 ?l?d?u ./test.hash
hashcat (v3.10) starting...

OpenCL Platform #1: Intel(R) Corporation
========================================
- Device #1: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz, 2018/8072 MB allocatable, 4MCU

Hashes: 1 hashes; 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
* Slow-Hash-SIMD
Watchdog: Temperature abort trigger disabled
Watchdog: Temperature retain trigger disabled

Initializing device kernels and memory...

ERROR: clCreateProgramWithBinary(): CL_INVALID_BINARY

Using a Dell E6520 laptop running Windows 7 Pro.
Installed OpenCL runtime for Intel Core and Xeon Processors Intel Corp 11/26/2016 103MB 5.0.0.57

What am I missing?
Thanks!
#5
You need to removed the cache folder, called "kernels" in the hashcat installation. After that it should work.
#6
(11-27-2016, 02:29 PM)atom Wrote: You need to removed the cache folder, called "kernels" in the hashcat installation. After that it should work.

Thank you Atom!!!  That worked.  Hashcat is running now. Very much appreciated.