hashcat Forum - No GPU utilization

I am trying to run some md5 hashes through the gpus. The hashlist has about 9.5 million hashes and the wordlist from InsidePro has about 154 million words.
Windows 7-64bit 16GB ram, 2x ATI-5770

Option 1 using hashcat-gui:

C:\Users\XXXXX\Downloads\hashcat-gui-0.5.1\hashcat-gui-0.5.1\oclHashcat-plus>oclHashcat-plus64.exe --remove --outfile J:\Hashes\xabout.txt --gpu-devices 2 -m 0 J:\Hashes\xab J:\Wordlists\InsidePro\Master.txt

Status.......: Running
Input.Mode...: File (J:\Wordlists\InsidePro\Master.txt)
Hash.Type....: MD5
Time.Running.: 17 mins, 47 secs
Time.Left....: 4 hours, 26 mins
Time.Util....: 1067513.1ms/885.3ms Real/CPU, 0.1% idle
Speed........: 9305 c/s Real, 9207 c/s GPU
Recovered....: 73840/9532502 Digests, 0/1 Salts
Progress.....: 9981185/154045162 (6.48%)
Rejected.....: 48385/9981185 (0.48%)
HW.Monitor.#1: 0% GPU, 58c Temp
[s]tatus [p]ause [r]esume [q]uit =>

Option 2 using plain oclhashcat-plus:

C:\Users\XXXXX\Downloads\oclHashcat-plus-0.09>oclHashcat-plus64.exe --remove --outfile J:\Hashes\xabout.txt --gpu-devices 2 -m 0 J:\Hashes\xab J:\Wordlists\InsidePro\Master.txt

Access is denied.

Windows prompt error popup: oclHashcat-plus64.exe is not a valid Win32 application. Of course I tried the 32 bit version but it didn't have enough memory. The md5 hashlist is

For option 1, why is my gpu not getting used at all?
For option 2, how can I run the 64 bit cmd?

it is getting use just not reporting the utilization. otherwise you would have 0 found. for the error, try downloading it again, never seen that problem.

(12-02-2012, 04:34 AM)radix Wrote: [ -> ]it is getting use just not reporting the utilization. otherwise you would have 0 found. for the error, try downloading it again, never seen that problem.

Well that I can guess was just by the cpu. You would think that 2 ati 5770's would get more than 9207 c/s. My cpu gets tons more than that. Also I am using the AMD Vision control center to monitor the activity temps, and fan info and it doesn't get to 1%

EDIT: A redownload of the oclhashcat-plus (not gui) seems to still have the issue that it is not using the GOU, but at least it let me run the oclHashcat-plus64.exe

oclhashcat-plus does not use CPU. if you are using the gui stop and use just the command line, gui is not supported by us.

you are not giving the card any work to do, that is why there is 0% utilization. if you want to fully utilize the gpu then try adding rules to give the card something to do.

(12-02-2012, 03:30 PM)epixoip Wrote: [ -> ]you are not giving the card any work to do, that is why there is 0% utilization. if you want to fully utilize the gpu then try adding rules to give the card something to do.

That was my problem. I now show the cpu at 721M c/s and the gpu at 755M c/s for generate rules 20. If I were to say --generate-rules 20 would it do all of --generate-rules 19 and --generate-rules 18? The manual isn't clear on that.

On my use of the rule d3ad0ne the hardware 1 still shows 0%. It seems to only report and use one of my two graphics cards. They are both 5770's and have crossfire. I notice on the AMD control center that card 1 is at 0% and card 2 is at ~95% at 72C.

Dude, the CPU is not cracking your hashes... thats all gpu power

(12-03-2012, 01:56 AM)tinman Wrote: [ -> ]If I were to say --generate-rules 20 would it do all of --generate-rules 19 and --generate-rules 18? The manual isn't clear on that.

no. you are generating random rules. -g 19 would generate 19 random rules. -g 20 would generate 20 random rules. typically you want to do something like -g 30000.

(12-03-2012, 01:56 AM)tinman Wrote: [ -> ]They are both 5770's and have crossfire.

remove your crossfire interconnect and disable crossfire.

(12-03-2012, 01:56 AM)tinman Wrote: [ -> ]On my use of the rule d3ad0ne the hardware 1 still shows 0%. It seems to only report and use one of my two graphics cards. They are both 5770's and have crossfire. I notice on the AMD control center that card 1 is at 0% and card 2 is at ~95% at 72C.

On your command line, you specify -d 2 which means use only GPU2. You have to specify -d 1,2 to get both working. You still need rules to keep them both busy...