Heya folks,
First ever install upon win8.1 64bit with Hashcat-gui installed.. breezes in as all windows does and hogs everything it can..
Fire up the hashcat-gui, just want to run a brief test to see that it all function so I set all my GPU cards to compute on whatever hash, set to brute force (because it's a trial)
I then start proceedings, and here is where the fun starts..
Using "all" in the options menu for GPUS leads me to an OpenCL error message..
So no big deal, teething issues, I then change nothing apart from the GPU setting and start with card number one on its own, everything runs fine.. I then revert and try card number two on its own as well, this also runs fine.. Use the exact same setting apart from running card three alone and the whole computer out right switches off..??
Just curious really and maybe I need to RtFM before I get started..
hashcat-gui is not an official hashcat product and thus is not supported here. If you want help on these forums you need to learn how to use the command line.
Your rig powering itself off during benchmark is almost certainly power related. Your PSU likely cannot supply enough power.
(10-04-2016, 06:00 PM)epixoip Wrote: [ -> ]hashcat-gui is not an official hashcat product and thus is not supported here. If you want help on these forums you need to learn how to use the command line.
Your rig powering itself off during benchmark is almost certainly power related. Your PSU likely cannot supply enough power.
hashcat64.exe -a 3 -m 100 --session=all -o "C:\Users\didge\Desktop\HashcatGUI_050b1\tmp85E5_found100.txt" --outfile-format=3 -w 2 --gpu-temp-abort=80 -1 ?l?d "C:\Users\didge\AppData\Local\Temp\tmp85E5.tmp" ?1?1?1?1?1?1?1?1
Powersupply does seem fine for Blender rendering when I use all the cards as part of my RenderFarm and I only seem to be having this kind of issue with Hashcat itself.. I will try more on the cmd line, I'm so much more used to Linux myself..
Cheers buddy.
ERROR: clBuildProgram(): CL_INVALID_BINARY is the error returned when using all three GPU cards.
Thanks for you're feedback, things have actually changed now, I can run cards 2,3 on their own but running all three together I still return the same error as I have above in my last post
card one working GTX570
hashcat64.exe -a 3 -m 100 --session=1 -o "C:\Users\didge\Desktop\HashcatGUI_050b1\tmp85E5_found100.txt" --outfile-format=3 -w 2 --gpu-temp-abort=80 -d 1 -1 ?l?d "C:\Users\darren\AppData\Local\Temp\tmp85E5.tmp" ?1?1?1?1?1?1?1?1
card two working GTX570
hashcat64.exe -a 3 -m 100 --session=2 -o "C:\Users\didge\Desktop\HashcatGUI_050b1\tmp85E5_found100.txt" --outfile-format=3 -w 2 --gpu-temp-abort=80 -d 2 -1 ?l?d "C:\Users\darren\AppData\Local\Temp\tmp85E5.tmp" ?1?1?1?1?1?1?1?1
card three failed GTX660 [ ERROR: clBuildProgram(): CL_INVALID_BINARY ]
hashcat64.exe -a 3 -m 100 --session=3 -o "C:\Users\didge\Desktop\HashcatGUI_050b1\tmp85E5_found100.txt" --outfile-format=3 -w 2 --gpu-temp-abort=80 -d 3 -1 ?l?d "C:\Users\darren\AppData\Local\Temp\tmp85E5.tmp" ?1?1?1?1?1?1?1?1
So this could be related to the mixing of CUDA cards itself?
So, uninstalled the drivers for all graphics adapters and installed fresh copies from nVidia..
Funny thing is I'm using dual 850w 42+Amp PSUs here so loads of power handy.. Now with the fresh drivers, I'm not getting a single bean out of anything where as the older drivers worked fine at least for running a single GTX570 card when using them alone, using both GTX570 cards would instantly turn off the machine.. Running the GTX660oc model would always give me the same error..
But now, I get this regardless of card and regardless of which was I run them.
C:\Users\didge\Downloads\hashcat-3.10>hashcat64.exe -a 3 -m 100 --session=all -o "C:\Users\didge\Desktop\HashcatGUI_050b1\tmpF454_
found100.txt" --outfile-format=3 -w 2 --gpu-temp-abort=80 -1 ?l?d "C:\Users\didge\AppData\Local\Temp\tmpF454.tmp" ?1?1?1?1?1?1?1?1
hashcat (v3.10) starting...
OpenCL Platform #1: NVIDIA Corporation
======================================
- Device #1: GeForce GTX 570, 320/1280 MB allocatable, 15MCU
- Device #2: GeForce GTX 570, 320/1280 MB allocatable, 15MCU
- Device #3: GeForce GTX 660, 512/2048 MB allocatable, 5MCU
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
* Precompute-Init
* Precompute-Merkle-Demgard
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
* Raw-Hash
Watchdog: Temperature abort trigger set to 80c
Watchdog: Temperature retain trigger set to 75c
Initializing device kernels and memory...
ERROR: clBuildProgram(): CL_INVALID_BINARY
C:\Users\didge\Downloads\hashcat-3.10>hashcat64.exe -a 3 -m 100 --session=1 -o "C:\Users\didge\Desktop\HashcatGUI_050b1\tmp85E5_fo
und100.txt" --outfile-format=3 -w 2 --gpu-temp-abort=80 -d 1 -1 ?l?d "C:\Users\didge\AppData\Local\Temp\tmp85E5.tmp" ?1?1?1?1?1?1?1
?1
hashcat (v3.10) starting...
OpenCL Platform #1: NVIDIA Corporation
======================================
- Device #1: GeForce GTX 570, 320/1280 MB allocatable, 15MCU
- Device #2: GeForce GTX 570, skipped
- Device #3: GeForce GTX 660, skipped
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
* Precompute-Init
* Precompute-Merkle-Demgard
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
* Raw-Hash
Watchdog: Temperature abort trigger set to 80c
Watchdog: Temperature retain trigger set to 75c
Initializing device kernels and memory...
ERROR: clBuildProgram(): CL_INVALID_BINARY
C:\Users\didge\Downloads\hashcat-3.10>hashcat64.exe -a 3 -m 100 --session=2 -o "C:\Users\didge\Desktop\HashcatGUI_050b1\tmp85E5_fo
und100.txt" --outfile-format=3 -w 2 --gpu-temp-abort=80 -d 2 -1 ?l?d "C:\Users\didge\AppData\Local\Temp\tmp85E5.tmp" ?1?1?1?1?1?1?1
?1
hashcat (v3.10) starting...
OpenCL Platform #1: NVIDIA Corporation
======================================
- Device #1: GeForce GTX 570, skipped
- Device #2: GeForce GTX 570, 320/1280 MB allocatable, 15MCU
- Device #3: GeForce GTX 660, skipped
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
* Precompute-Init
* Precompute-Merkle-Demgard
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
* Raw-Hash
Watchdog: Temperature abort trigger set to 80c
Watchdog: Temperature retain trigger set to 75c
Initializing device kernels and memory...
ERROR: clBuildProgram(): CL_INVALID_BINARY
C:\Users\didge\Downloads\hashcat-3.10>hashcat64.exe -a 3 -m 100 --session=3 -o "C:\Users\didge\Desktop\HashcatGUI_050b1\tmp85E5_fo
und100.txt" --outfile-format=3 -w 2 --gpu-temp-abort=80 -d 3 -1 ?l?d "C:\Users\didge\AppData\Local\Temp\tmp85E5.tmp" ?1?1?1?1?1?1?1
?1
hashcat (v3.10) starting...
OpenCL Platform #1: NVIDIA Corporation
======================================
- Device #1: GeForce GTX 570, skipped
- Device #2: GeForce GTX 570, skipped
- Device #3: GeForce GTX 660, 512/2048 MB allocatable, 5MCU
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
* Precompute-Init
* Precompute-Merkle-Demgard
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force
* Raw-Hash
Watchdog: Temperature abort trigger set to 80c
Watchdog: Temperature retain trigger set to 75c
Initializing device kernels and memory...
ERROR: clBuildProgram(): CL_INVALID_BINARY
C:\Users\didge\Downloads\hashcat-3.10>
CL_INVALID_BINARY
clCreateProgramWithBinary, clBuildProgram
The provided binary is unfit for the selected device.
if program is created with clCreateProgramWithBinary and devices listed in device_list do not have a valid program binary loaded.
So anyone come across this issue prior? I'm now installing the CUDA SDK as well and see if this fixes anything..
Surely someone must be running a GTX 5 or 6 series with more then one card installed and the latest drivers? We aint all using GTX1080s now are we.. Even though I'm currently building a node with six GTX 770 cards on it..
This is windows and driver issue sadly not power supply, the PSU issue would be easy to fix and I could even right now give each GTX card an 850w 42amp PSU to itself..