hashcat Forum

Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
GPU-Loops: 128
GPU-Accel: 160
Password lengths range: 1 - 15
Platform: AMD compatible platform found
Watchdog: Temperature limit set to 90c
Device #1: Cayman, 2048MB, 0Mhz, 24MCU
Device #2: Cayman, 2048MB, 0Mhz, 24MCU
Device #1: Allocating 577MB host-memory
Device #1: Kernel ./kernels/4098/m0000_a3.Cayman.64.kernel (511848 bytes)
Device #2: Allocating 577MB host-memory
Device #2: Kernel ./kernels/4098/m0000_a3.Cayman.64.kernel (511848 bytes)
Status.......: Running
Input.Mode...: Mask (?1?1?1?1?1?1?1?1)
Hash.Type....: MD5
Time.Running.: 3 mins, 54 secs
Time.Left....: 1 day, 13 hours
Time.Util....: 234147.9ms/0.9ms Real/CPU, 0.0% idle
Speed........: 1627.2M c/s Real, 1627.6M c/s GPU
Recovered....: 0/14 Digests, 0/1 Salts
Progress.....: 381010575360/218340105584896 (0.17%)
Rejected.....: 0/381010575360 (0.00%)
HW.Monitor.#1: 27% GPU, 62c Temp
HW.Monitor.#2: 100% GPU, 44c Temp
[s]tatus [p]ause [r]esume [q]uit =>
*******************************************
Windows7, same cards, stock clocks, Catalyst 12.4
Only iam have this problem?

what is the problem? everything looks normal to me. if you are concerned about the GPU usage being unequal it's normal. you could try to increase gpu-loops to 1024

its looks wrong for me because in hashcat plus 0.8 with catalyst 11.12 speed x2

I just had another idea. Maybe you are running a task which uses GPGPU. Flash (inside browser) is such a beast.

Reinstall windows 7 x64 ultimate and catalyst 12.4, nothing more.
Problem when in case 2 GPU, each solo GPU show good speed and load ~3M c/s on md5...but then 2, speed about 1.6M

---

with 11.12 catalyst
Hash.Type....: MD5
Time.Running.: 6 secs
Time.Left....: 10 hours, 27 mins
Time.Util....: 6964.5ms/1.0ms Real/CPU, 0.0% idle
Speed........: 5799.6M c/s Real, 5801.9M c/s GPU
Recovered....: 0/14 Digests, 0/1 Salts
Progress.....: 40391147520/218340105584896 (0.02%)
Rejected.....: 0/40391147520 (0.00%)
HW.Monitor.#1: 95% GPU, 62c Temp
HW.Monitor.#2: 95% GPU, 57c Temp

I noticed this issue as well. Turning on Crossfire resolved it for me.