hashcat Forum

Dear Atom pls. help look what wrong is this.

With Win7 x64, 4x 6990, catalyst v11.12(12.1 not work for me)

D:\oclHashcat-lite-0.09>oclHashcat-lite64 6A46CABB98880BEC7BF00851C6B2A4E7DD7930
F3:003533880416474800 -1 00010203040506070809 -m 1900 ?1?1?1?1?1?1?1?1?1?1?1?1?1
?1?1 --pw-skip 140000000000000 --pw-limit 290000000000000 --gpu-watchdog=0 -n 80
0 --outfile-format=1 --outfile=z:/Son_353388041647480_8_10.txt
oclHashcat-lite v0.9 by atom starting...

GPU-Loops: 1024
GPU-Accel: 800
Password lengths range: 15 - 15
Platform: AMD compatible platform found
Watchdog: Temperature limit disabled
Device #1: Cayman, 2048MB, 0Mhz, 24MCU
Device #2: Cayman, 2048MB, 0Mhz, 24MCU
Device #3: Cayman, 2048MB, 0Mhz, 24MCU
Device #4: Cayman, 2048MB, 0Mhz, 24MCU
Device #5: Cayman, 2048MB, 0Mhz, 24MCU
Device #6: Cayman, 2048MB, 0Mhz, 24MCU
Device #7: Cayman, 2048MB, 0Mhz, 24MCU
Device #8: Cayman, 2048MB, 0Mhz, 24MCU
ERROR: clBuildProgram() -11

This is error message from catalyst 11.12. Your catalyst 12.1 installation might be not successfull.

@vid
You can keep your 11.12 on your system, just only update your AMD SDK Runtime from 12.1 package (untick all accept that), it works well on my system with that.

noted....


Tkx. for Atom and Hoang....

I have exact same problem on Linux 64bit (2.6.39-sabayon) with HD 5650 and HD 5850. I've installed APP SDK v 2.6 prior to ati-drivers-11.12 and the 0.08 version works fine on this config. Version 0.09 after issuing:

$ ./oclHashcat-lite64.bin -m 1900 -n 160 --outfile=result.txt -1 00010203040506070809 B84E3C2F9B780A911B0613E6AFDC5FF4783942FF:003553590478594900 ?1?1?1?1?1?1?1?1?1?1?105060907

results in:
oclHashcat-lite v0.9 by atom starting...

GPU-Loops: 1024
GPU-Accel: 160
Password lengths range: 15 - 15
Platform: AMD compatible platform found
Watchdog: Temperature limit set to 90c
Device #1: Redwood, 512MB, 0Mhz, 5MCU
ERROR: clBuildProgram() -11

Any ideas?

uninstall SDK, uninstall driver, driver sweep all amd ati gpu stuff which is left, install cat 12.1

For me just installing the new Catalyst driver (12.1) fixed the problem. Thanx!