Bug -o option

[BytePuker]

Hi, I have a big problem with oclhashcat.

When I want to bruteforce or combinate my Speed is going down.

G:\Cracker\oclHashcat-0.26>oclHashcat64.exe --remove -o Hashes/md5_cracked.txt Hashes/md5.txt -n 160 --gpu
-loops 1024 -1 ?l ?1?1?1?1?1 ?1?1?1?1?1
oclHashcat v0.26 by atom starting...
......
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: Juniper, 1024MB, 0Mhz, 10MCU
Device #1: Kernel ./kernels/4098/m0000.Cayman.64.kernel
Device #2: Kernel ./kernels/4098/m0000.Cayman.64.kernel
Device #3: Kernel ./kernels/4098/m0000.Cayman.64.kernel
Device #4: Kernel ./kernels/4098/m0000.Cayman.64.kernel
Device #5: Kernel ./kernels/4098/m0000.Juniper.64.kernel

The problem is, when it found a password I only get 570 M/Hashs/s. Before, I get the full speed. Anything I'm doing wrong ?

oclhashcat-plus and oclhashcat-lite are running without any problems.

[atom]

left side is a bit small for so much computing power. maybe shift some masks from the right to the left like ?1?1?1?1?1?1?1 ?1?1 or increase keyspace with -1 ?l?d. also mixing gpus isnt very good. consider removing the 57xx. also the number of hashes depend. but if you have less than 1 million it should not drop so much. but if you have more it may happen.

[BytePuker]

no, you missunderstand. When I start a attack /for example combinator with rockyou) I get the full speed (a few billion). BUT AFTER one password is found the speed drops dramaticly and I only get 500-600 MHash/s.

With the new oclhashcat-plus version I only get 3000kHash/s. I build a new case to find the problem (now only one HD6970 and one 6990).

What is the problem? My OS is Windows 7 x64 ultimate.

Edit: Screenshot

oclhashcat:

http://imageshack.us/photo/my-images/836...18m31s.jpg

oclhashcat-plus

http://img87.imageshack.us/img87/7894/sc...19m21s.jpg

[atom]

you need to add rules when using fast algorithms in combination with plus. for example add -r rules/perfect.rule (its a benchmarking rule).

[BytePuker]

I found out that the cause of the problem (in oclhashcat) is the --remove switch. Without this the speed is constantly at max but with this option the speed drops down dramaticly after one password is found.

[atom]

which version are you using? i remember having that issue in an old version

[BytePuker]

oclhashcat v0.26, it would be nice if you could fix this problem

you can see it on the screenshot

[atom]

thanks for the screenshot. i cant see which cpu is it?

[BytePuker]

it is an i7 920 CPU.

[atom]

cant reproduce this locally. please upload all required files somewhere pls. maybe its something in your hashlist.