Hey,
did you try to run the same attack with the command line parameter -d 1 , afterwards -d 2 .
Furthermore you should try to run the benchmark oclHashcat64.bin -b -m 1000, also oclHashcat64.bin -b -m 1000 -d 1 and oclHashcat64.bin -b -m 1000 -d 2
New 1.02 version (not yet released https://twitter.com/hashcat/status/437598775687659521 ) may change this situation / fix this problem somehow, because several things changed since last release. Dunno.
But it could also be a hw / driver issue.
Btw, dunno if it helps or changes sth, but did you try to swap the 2 cards?
It would be also important that you post the device list (with mem, clocks etc) which you will always see (if --quiet was not used) at the beginning of the run.
did you try to run the same attack with the command line parameter -d 1 , afterwards -d 2 .
Furthermore you should try to run the benchmark oclHashcat64.bin -b -m 1000, also oclHashcat64.bin -b -m 1000 -d 1 and oclHashcat64.bin -b -m 1000 -d 2
New 1.02 version (not yet released https://twitter.com/hashcat/status/437598775687659521 ) may change this situation / fix this problem somehow, because several things changed since last release. Dunno.
But it could also be a hw / driver issue.
Btw, dunno if it helps or changes sth, but did you try to swap the 2 cards?
It would be also important that you post the device list (with mem, clocks etc) which you will always see (if --quiet was not used) at the beginning of the run.