Discrepancy between Benchmark numbers and actual numbers

[XakEp]

Adding ?b to the mask results in an Integer Overflow Detected in Keyspace of Mask error. So that's a no go.

[XakEp]

Ok, so I've been doing a LOT of testing and have a mask attack at this speed now -

Speed.#1.........: 40525.5 MH/s (8.24ms) @ Accel:64 Loops:512 Thr:256 Vec:4
Speed.#2.........: 29474.6 MH/s (6.84ms) @ Accel:128 Loops:256 Thr:256 Vec:4
Speed.#3.........: 16398.9 MH/s (5.99ms) @ Accel:256 Loops:128 Thr:256 Vec:4
Speed.#4.........: 17355.7 MH/s (9.46ms) @ Accel:128 Loops:256 Thr:256 Vec:4
Speed.#*.........: 103.8 GH/s

The 2080RTX is very inconsistent. It speeds up and slows down and I can't tell why. I think at this point I need to start figuring out efficient ways to get GPU acceleration with rule based attacks. Nothing in the FAQ is getting me near the benchmarks. For example, I'm seeing this on NTLM benchmarks -

Hashmode: 1000 - NTLM

Speed.#1.........: 73142.2 MH/s (9.74ms) @ Accel:64 Loops:1024 Thr:256 Vec:2
Speed.#2.........: 57691.4 MH/s (15.03ms) @ Accel:128 Loops:1024 Thr:256 Vec:2
Speed.#3.........: 33680.1 MH/s (28.19ms) @ Accel:256 Loops:1024 Thr:256 Vec:2
Speed.#4.........: 30712.6 MH/s (23.18ms) @ Accel:128 Loops:1024 Thr:256 Vec:2
Speed.#*.........: 195.2 GH/s

But actual attacks are 60% slower than that. So more experimentation will be happening, maybe someone else can learn from my missteps. If anyone has suggestions for me I'm all ears, but I'll be plugging away at this.

Thanks for listening to this old fart. I'm not smart, I'm just too dumb to give up.

[philsmd]

what makes me wondering the most is the util percentage in your benchmark-like run for -m 0:

Code:

Time.Started.....: Fri Aug 30 12:52:59 2019 (2 secs)
...
Guess.Mask.......: ?b?b?b?b?b?b?b [7]
...
Speed.#1.........: 24835.8 MH/s (17.96ms) @ Accel:64 Loops:1024 Thr:256 Vec:4
Speed.#2.........: 20023.2 MH/s (34.71ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Speed.#3.........: 16091.3 MH/s (50.37ms) @ Accel:256 Loops:1024 Thr:256 Vec:4
Speed.#4.........: 15734.6 MH/s (38.61ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Speed.#*.........: 76685.5 MH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
...
Hardware.Mon.#1..: Temp: 33c Fan: 44% Util: 57% Core:2040MHz Mem:6800MHz Bus:1
Hardware.Mon.#2..: Temp: 25c Fan: 40% Util: 77% Core:1392MHz Mem:5005MHz Bus:1
Hardware.Mon.#3..: Temp: 37c Fan: 48% Util: 77% Core:2037MHz Mem:3802MHz Bus:1
Hardware.Mon.#4..: Temp: 38c Fan: 71% Util: 84% Core:1379MHz Mem:3304MHz Bus:1

it's probably not the best to just use 2 seconds for benchmark, but I hope/guess it's still quite accurate in your case.

The Util is always 100% on my systems if I run this same test.
Also the Bus is only 1.

I'm wondering if there is some kind of strange bottleneck with your system, e.g. PCI speed etc. It actually shouldn't matter too much to use only 1x PCI, but maybe you can explain more what kind of system this is and if you are using some risers etc. Not sure if this is really the problem, because it's strange that the benchmark with -b shows higher speed even with almost all the same settings it should show the same speed and keep showing 100% util on all cards.

You might also play around with (physically) only testing some of the cards and/or using -d to test e.g. only with 1 GPU, with 2 GPUs, 3 GPUs etc... and see if the Util drops for you.

Maybe the first thing we should clarify now is if also after for instance 5 minutes the Util is still much less than 100% .
Thanks

[XakEp]

I'd guess the mask is still too short and doesn't provide enough work. Numbers are pretty close to the benchmark on all cards but the fastest, the 2080.

Yeah, this is a system I built using an open air crypto rig (no, I've never mined so these cards have only been used for gaming).

https://imgur.com/a/T3uNgGn

I am using risers, but I think I can relocate one to the board (should be enough room with everything but maybe not) to test if you think that would make a difference. The system has 32GB of RAM, which is just under what the cards have on them when added up. I wouldn't think this would make a difference but if so, I'd love to hear your thoughts. I've read through all the posts about having 1:1 ratio and while I would think having just UNDER the 1:1 wouldn't be optimal, I would also think it wouldn't cause something quite like this. But hey, I'm open to being wrong.

I ran that ?b test again and let it run for 5 minutes. I'll let it run for a while longer, if I see a change in speed I'll post the data up here.

Session..........: hashcat
Status...........: Running
Hash.Type........: MD5
Hash.Target......: (redacted)
Time.Started.....: Sat Aug 31 10:49:48 2019 (6 mins, 2 secs)
Time.Estimated...: Sat Sep 14 05:48:07 2019 (13 days, 18 hours)
Guess.Mask.......: ?b?b?b?b?b?b?b [7]
Guess.Queue......: 1/1 (100.00%)
Speed.#1.........: 21820.6 MH/s (17.56ms) @ Accel:64 Loops:1024 Thr:256 Vec:4
Speed.#2.........:  9964.0 MH/s (5.40ms) @ Accel:128 Loops:128 Thr:256 Vec:4
Speed.#3.........: 14835.7 MH/s (50.15ms) @ Accel:256 Loops:1024 Thr:256 Vec:4
Speed.#4.........: 13853.8 MH/s (37.36ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Speed.#*.........: 60470.0 MH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 21514464264192/72057594037927936 (0.03%)
Rejected.........: 0/21514464264192 (0.00%)
Restore.Point....: 0/4294967296 (0.00%)
Restore.Sub.#1...: Salt:0 Amplifier:10413056-10414080 Iteration:0-1024
Restore.Sub.#2...: Salt:0 Amplifier:3677184-3677312 Iteration:0-128
Restore.Sub.#3...: Salt:0 Amplifier:5429248-5430272 Iteration:0-1024
Restore.Sub.#4...: Salt:0 Amplifier:6874112-6875136 Iteration:0-1024
Candidates.#1....: $HEX[73e49e6572616e] -> $HEX[ffe79eff7f0b00]
Candidates.#2....: $HEX[7376436580255e] -> $HEX[d21c38ff7f3331]
Candidates.#3....: $HEX[73d85265800b00] -> $HEX[ffdb52ff7f1a00]
Candidates.#4....: $HEX[73e46865801a00] -> $HEX[ffe768ff7f255e]
Hardware.Mon.#1..: Temp: 47c Fan: 97% Util: 47% Core:2085MHz Mem:7500MHz Bus:1
Hardware.Mon.#2..: Temp: 44c Fan: 46% Util: 25% Core:1949MHz Mem:5103MHz Bus:1
Hardware.Mon.#3..: Temp: 57c Fan:100% Util: 82% Core:2025MHz Mem:3802MHz Bus:1
Hardware.Mon.#4..: Temp: 59c Util: 22% Core:1189MHz Mem:3304MHz Bus:1

That's what I don't get - the Utilization % is way low and there's no reason I can think of beyond either driver or OS. Have you heard of anyone else having this happen to them?

Here's the results of individual card testing.

RTX 2080

Session..........: hashcat
Status...........: Running
Hash.Type........: MD5
Hash.Target......: (redacted)
Time.Started.....: Sat Aug 31 11:01:06 2019 (42 secs)
Time.Estimated...: Fri Oct 04 05:42:58 2019 (33 days, 18 hours)
Guess.Mask.......: ?b?b?b?b?b?b?b [7]
Guess.Queue......: 1/1 (100.00%)
Speed.#1.........: 24689.8 MH/s (17.54ms) @ Accel:64 Loops:1024 Thr:256 Vec:4
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 1051897888768/72057594037927936 (0.00%)
Rejected.........: 0/1051897888768 (0.00%)
Restore.Point....: 0/4294967296 (0.00%)
Restore.Sub.#1...: Salt:0 Amplifier:1395712-1396736 Iteration:0-1024
Candidates.#1....: $HEX[7347346572616e] -> $HEX[ff4f46ff7f0b00]
Hardware.Mon.#1..: Temp: 47c Fan: 96% Util: 58% Core:2085MHz Mem:7500MHz Bus:1p

1080ti FE

Session..........: hashcat
Status...........: Running
Hash.Type........: MD5
Hash.Target......: (redacted)
Time.Started.....: Sat Aug 31 11:02:44 2019 (1 min, 0 secs)
Time.Estimated...: Fri Oct 11 02:57:25 2019 (40 days, 15 hours)
Guess.Mask.......: ?b?b?b?b?b?b?b [7]
Guess.Queue......: 1/1 (100.00%)
Speed.#2.........: 20510.0 MH/s (27.09ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 1243929903104/72057594037927936 (0.00%)
Rejected.........: 0/1243929903104 (0.00%)
Restore.Point....: 0/4294967296 (0.00%)
Restore.Sub.#2...: Salt:0 Amplifier:1355776-1356800 Iteration:0-1024
Candidates.#2....: $HEX[73b0146572616e] -> $HEX[ffb314ffff0d00]
Hardware.Mon.#2..: Temp: 49c Fan: 46% Util: 62% Core:1949MHz Mem:5103MHz Bus:1

GTX 1070

Session..........: hashcat
Status...........: Running
Hash.Type........: MD5
Hash.Target......: (redacted)
Time.Started.....: Sat Aug 31 11:04:29 2019 (2 mins, 49 secs)
Time.Estimated...: Tue Oct 22 04:53:43 2019 (51 days, 17 hours)
Guess.Mask.......: ?b?b?b?b?b?b?b [7]
Guess.Queue......: 1/1 (100.00%)
Speed.#3.........: 16118.3 MH/s (50.13ms) @ Accel:256 Loops:1024 Thr:256 Vec:4
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 2723948789760/72057594037927936 (0.00%)
Rejected.........: 0/2723948789760 (0.00%)
Restore.Point....: 0/4294967296 (0.00%)
Restore.Sub.#3...: Salt:0 Amplifier:2770944-2771968 Iteration:0-1024
Candidates.#3....: $HEX[7352406572616e] -> $HEX[ff4b75ffff0e00]
Hardware.Mon.#3..: Temp: 57c Fan:100% Util: 85% Core:2025MHz Mem:3802MHz Bus:1

980ti

Session..........: hashcat
Status...........: Running
Hash.Type........: MD5
Hash.Target......: (redacted)
Time.Started.....: Sat Aug 31 11:07:57 2019 (1 min, 48 secs)
Time.Estimated...: Wed Oct 23 11:08:51 2019 (52 days, 23 hours)
Guess.Mask.......: ?b?b?b?b?b?b?b [7]
Guess.Queue......: 1/1 (100.00%)
Speed.#4.........: 15735.7 MH/s (37.36ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 1704498036736/72057594037927936 (0.00%)
Rejected.........: 0/1704498036736 (0.00%)
Restore.Point....: 0/4294967296 (0.00%)
Restore.Sub.#4...: Salt:0 Amplifier:2364416-2365440 Iteration:0-1024
Candidates.#4....: $HEX[73645f6572616e] -> $HEX[ff1724ffff0a00]
Hardware.Mon.#4..: Temp: 60c Fan: 99% Util: 77% Core:1429MHz Mem:3304MHz Bus:1

If I let them run for hours the utilization never goes up significantly, but it'll drop to 0% now and again on all cards.

[XakEp]

For giggles I ran the ?b attack on my personal desktop (single 1080ti) and here's what I got

[quote]Session..........: hashcat
Status...........: Running
Hash.Type........: MD5
Hash.Target......: (redacted)
Time.Started.....: Sat Aug 31 11:30:35 2019 (1 min, 2 secs)
Time.Estimated...: Wed Sep 25 03:11:05 2019 (24 days, 15 hours)
Guess.Mask.......: ?b?b?b?b?b?b?b [7]
Guess.Queue......: 1/1 (100.00%)
Speed.#1.........: 33829.4 MH/s (107.80ms) @ Accel:128 Loops:1024 Thr:1024 Vec:4
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 2074469203968/72057594037927936 (0.00%)
Rejected.........: 0/2074469203968 (0.00%)
Restore.Point....: 0/4294967296 (0.00%)
Restore.Sub.#1...: Salt:0 Amplifier:565248-566272 Iteration:0-1024
Candidates.#1....: $HEX[73a06d6572616e] -> $HEX[ffa365ffff3737]
Hardware.Mon.#1..: Temp: 66c Util: 97% Core:1784MHz Mem:5508MHz Bus:16[]/quote]


Exactly what is expected. So I'm going to try a few things and report back later today. If y'all have any ideas I'm all ears, will report back when I'm done tonight. Hopefully my issues help others in the future who are googling lol.

[XakEp]

Ok so for giggles I did some testing, and accidentally came across something.

Here's the benchmark for MD5

Hashmode: 0 - MD5

Speed.#1.........: 41444.7 MH/s (18.21ms) @ Accel:64 Loops:1024 Thr:256 Vec:4
Speed.#2.........: 33367.6 MH/s (27.55ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Speed.#3.........: 19730.0 MH/s (50.48ms) @ Accel:256 Loops:1024 Thr:256 Vec:4
Speed.#4.........: 18815.4 MH/s (38.72ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Speed.#*.........:  113.4 GH/s

Here's an attack for MD5, done wrong.

hashcat64.exe --stdout d:\wordlists\rockyou.txt -r rules\best64.rule | hashcat64.exe -m0 -a3 d:\hashlists\Random\Quillen.txt -O --status --status-timer=2

That -a3 shouldn't be there (typo on my part) but look at the output

Session..........: hashcat
Status...........: Running
Hash.Type........: MD5
Hash.Target......: (redacted)
Time.Started.....: Sat Aug 31 11:53:43 2019 (19 secs)
Time.Estimated...: Sat Aug 31 11:54:34 2019 (32 secs)
Guess.Mask.......: ?1?2?2?2?2?2?2?3 [8]
Guess.Charset....: -1 ?l?d?u, -2 ?l?d, -3 ?l?d*!$@_, -4 Undefined
Guess.Queue......: 8/15 (53.33%)
Speed.#1.........: 39630.7 MH/s (9.13ms) @ Accel:64 Loops:512 Thr:256 Vec:4
Speed.#2.........: 31296.3 MH/s (6.96ms) @ Accel:128 Loops:256 Thr:256 Vec:4
Speed.#3.........: 18150.8 MH/s (6.39ms) @ Accel:256 Loops:128 Thr:256 Vec:4
Speed.#4.........: 17768.5 MH/s (9.85ms) @ Accel:128 Loops:256 Thr:256 Vec:4
Speed.#*.........:  106.8 GH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 2072621613056/5533380698112 (37.46%)
Rejected.........: 0/2072621613056 (0.00%)
Restore.Point....: 18841600/68864256 (27.36%)
Restore.Sub.#1...: Salt:0 Amplifier:55808-56320 Iteration:0-512
Restore.Sub.#2...: Salt:0 Amplifier:18688-18944 Iteration:0-256
Restore.Sub.#3...: Salt:0 Amplifier:36736-36864 Iteration:0-128
Restore.Sub.#4...: Salt:0 Amplifier:76288-76544 Iteration:0-256
Candidates.#1....: lo18164a -> 94kzrr6t
Candidates.#2....: 5mswrr6t -> zclnjo1c
Candidates.#3....: M5btwh6c -> Bjl6804a
Candidates.#4....: 81yw8w0a -> Bbx68s5c
Hardware.Mon.#1..: Temp: 51c Fan: 38% Util: 96% Core:2010MHz Mem:6800MHz Bus:1
Hardware.Mon.#2..: Temp: 45c Fan: 22% Util: 96% Core:1822MHz Mem:5005MHz Bus:1
Hardware.Mon.#3..: Temp: 58c Fan:  8% Util: 95% Core:1999MHz Mem:3802MHz Bus:1
Hardware.Mon.#4..: Temp: 67c Fan:  0% Util: 96% Core:1366MHz Mem:3304MHz Bus:1

And look at the Guess.Charset, which is what you would expect from a basic brute force. It's not using the parameters (rule/wordlist) from the first instance of hashcat that's being piped to the second one. Yet, when I correct that -a3 by removing it OR putting an -a0 in there, I get this -

Session..........: hashcat
Status...........: Running
Hash.Type........: MD5
Hash.Target......: (redacted)
Time.Started.....: Sat Aug 31 12:15:01 2019 (19 secs)
Time.Estimated...: Sat Aug 31 12:15:20 2019 (0 secs)
Guess.Base.......: Pipe
Speed.#1.........:  148.8 kH/s (0.17ms) @ Accel:64 Loops:1 Thr:256 Vec:1
Speed.#2.........:  181.1 kH/s (0.41ms) @ Accel:128 Loops:1 Thr:256 Vec:1
Speed.#3.........:  257.5 kH/s (0.44ms) @ Accel:256 Loops:1 Thr:256 Vec:1
Speed.#4.........:  189.1 kH/s (0.29ms) @ Accel:128 Loops:1 Thr:256 Vec:1
Speed.#*.........:  776.6 kH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 8421448
Rejected.........: 72
Restore.Point....: 0
Restore.Sub.#1...: Salt:0 Amplifier:0-1 Iteration:0-1
Restore.Sub.#2...: Salt:0 Amplifier:0-1 Iteration:0-1
Restore.Sub.#3...: Salt:0 Amplifier:0-1 Iteration:0-1
Restore.Sub.#4...: Salt:0 Amplifier:0-1 Iteration:0-1
Candidates.#1....: snopsnop -> /avid
Candidates.#2....: d00davi -> tweetyie
Candidates.#3....: moza -> oliv3r21
Candidates.#4....: olver21 -> snoo88
Hardware.Mon.#1..: Temp: 31c Fan: 36% Util:  0% Core:1515MHz Mem:7500MHz Bus:1
Hardware.Mon.#2..: Temp: 27c Fan: 40% Util:  0% Core:1480MHz Mem:5103MHz Bus:1
Hardware.Mon.#3..: Temp: 29c Fan: 40% Util:  0% Core:1632MHz Mem:3802MHz Bus:1
Hardware.Mon.#4..: Temp: 32c Fan: 52% Util:  0% Core:1189MHz Mem:3304MHz Bus:1

It's acting like a basic dictionary lookup and ignores the rules parameter completely.

Now I'm really confused. I was going to relocate one of the cards to the MB to test, but this tells me the hardware is just fine. Something else is keeping that hardware from being utilized unless something funky happens with the command. Ideas?

Edit - both this rig and my desktop have the same drivers and are updated Windows 10

[XakEp]

Think I found something wrong with hashcat itself, but you guys are the experts not me.

If I run this attack with -w3 or -w4, I get something like this -

hashcat64.exe -m0 -a3 d:\hashlists\Random\Quillen.txt -O -w3 (or -w4)

Session..........: hashcat
Status...........: Running
Hash.Type........: MD5
Hash.Target......: (redacted)
Time.Started.....: Sat Aug 31 12:26:09 2019 (30 secs)
Time.Estimated...: Sat Aug 31 12:27:13 2019 (34 secs)
Guess.Mask.......: ?1?2?2?2?2?2?2?3 [8]
Guess.Charset....: -1 ?l?d?u, -2 ?l?d, -3 ?l?d*!$@_, -4 Undefined
Guess.Queue......: 8/15 (53.33%)
Speed.#1.........: 24814.2 MH/s (17.29ms) @ Accel:64 Loops:1024 Thr:256 Vec:4
Speed.#2.........: 29846.9 MH/s (25.97ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Speed.#3.........: 16099.1 MH/s (49.42ms) @ Accel:256 Loops:1024 Thr:256 Vec:4
Speed.#4.........: 15716.5 MH/s (37.04ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Speed.#*.........: 86476.9 MH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 2579455016960/5533380698112 (46.62%)
Rejected.........: 0/2579455016960 (0.00%)
Restore.Point....: 28409856/68864256 (41.25%)
Restore.Sub.#1...: Salt:0 Amplifier:18432-19456 Iteration:0-1024
Restore.Sub.#2...: Salt:0 Amplifier:6144-7168 Iteration:0-1024
Restore.Sub.#3...: Salt:0 Amplifier:6144-7168 Iteration:0-1024
Restore.Sub.#4...: Salt:0 Amplifier:7168-8192 Iteration:0-1024
Candidates.#1....: nclt5o6r -> Hhsspig4
Candidates.#2....: 0uc85lmn -> Cisqqtfh
Candidates.#3....: 0ucoy1n9 -> Cisz52v4
Candidates.#4....: J33wqqv4 -> pfo65lmn
Hardware.Mon.#1..: Temp: 45c Fan: 96% Util: 56% Core:2100MHz Mem:7500MHz Bus:1
Hardware.Mon.#2..: Temp: 49c Fan: 44% Util: 85% Core:1923MHz Mem:5103MHz Bus:1
Hardware.Mon.#3..: Temp: 52c Fan:100% Util: 80% Core:2037MHz Mem:3802MHz Bus:1
Hardware.Mon.#4..: Temp: 53c Fan:100% Util: 81% Core:1429MHz Mem:3304MHz Bus:1

But when I run it with JUST -O and no workload options at all, I get this

hashcat64.exe -m0 -a3 d:\hashlists\Random\Quillen.txt -O

Session..........: hashcat
Status...........: Running
Hash.Type........: MD5
Hash.Target......: (redacted)
Time.Started.....: Sat Aug 31 12:27:57 2019 (6 secs)
Time.Estimated...: Sat Aug 31 12:28:47 2019 (44 secs)
Guess.Mask.......: ?1?2?2?2?2?2?2?3 [8]
Guess.Charset....: -1 ?l?d?u, -2 ?l?d, -3 ?l?d*!$@_, -4 Undefined
Guess.Queue......: 8/15 (53.33%)
Speed.#1.........: 41490.8 MH/s (8.69ms) @ Accel:64 Loops:512 Thr:256 Vec:4
Speed.#2.........: 32504.0 MH/s (6.58ms) @ Accel:128 Loops:256 Thr:256 Vec:4
Speed.#3.........: 18270.0 MH/s (6.28ms) @ Accel:256 Loops:128 Thr:256 Vec:4
Speed.#4.........: 18502.0 MH/s (9.38ms) @ Accel:128 Loops:256 Thr:256 Vec:4
Speed.#*.........:  110.8 GH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 637860315136/5533380698112 (11.53%)
Rejected.........: 0/637860315136 (0.00%)
Restore.Point....: 2654208/68864256 (3.85%)
Restore.Sub.#1...: Salt:0 Amplifier:75776-76288 Iteration:0-512
Restore.Sub.#2...: Salt:0 Amplifier:43264-43520 Iteration:0-256
Restore.Sub.#3...: Salt:0 Amplifier:26752-26880 Iteration:0-128
Restore.Sub.#4...: Salt:0 Amplifier:67328-67584 Iteration:0-256
Candidates.#1....: r9zwe9lo -> opqqlxv1
Candidates.#2....: N8regqlo -> Y5rsb9l1
Candidates.#3....: 7zlog4vo -> zevza7d1
Candidates.#4....: Z1vdugby -> cc7sb8un
Hardware.Mon.#1..: Temp: 46c Util: 93% Core:2100MHz Mem:7500MHz Bus:1
Hardware.Mon.#2..: Temp: 43c Fan: 44% Util: 94% Core:1923MHz Mem:5103MHz Bus:1
Hardware.Mon.#3..: Temp: 49c Fan: 92% Util: 94% Core:2037MHz Mem:3802MHz Bus:1
Hardware.Mon.#4..: Temp: 48c Fan:100% Util: 96% Core:1429MHz Mem:3304MHz Bus:1

Running the same command with JUST -w3 or -w4

Session..........: hashcat
Status...........: Running
Hash.Type........: MD5
Hash.Target......: (redacted)
Time.Started.....: Sat Aug 31 12:29:31 2019 (4 secs)
Time.Estimated...: Sat Aug 31 12:31:33 2019 (1 min, 58 secs)
Guess.Mask.......: ?1?2?2?2?2?2?2?3 [8]
Guess.Charset....: -1 ?l?d?u, -2 ?l?d, -3 ?l?d*!$@_, -4 Undefined
Guess.Queue......: 8/15 (53.33%)
Speed.#1.........: 16048.6 MH/s (40.96ms) @ Accel:64 Loops:1024 Thr:256 Vec:1
Speed.#2.........: 13741.6 MH/s (62.22ms) @ Accel:128 Loops:1024 Thr:256 Vec:1
Speed.#3.........:  8074.8 MH/s (112.42ms) @ Accel:256 Loops:1024 Thr:256 Vec:1
Speed.#4.........:  7676.1 MH/s (84.19ms) @ Accel:128 Loops:1024 Thr:256 Vec:1
Speed.#*.........: 45541.1 MH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 153075318784/5533380698112 (2.77%)
Rejected.........: 0/153075318784 (0.00%)
Restore.Point....: 0/68864256 (0.00%)
Restore.Sub.#1...: Salt:0 Amplifier:70656-71680 Iteration:0-1024
Restore.Sub.#2...: Salt:0 Amplifier:50176-51200 Iteration:0-1024
Restore.Sub.#3...: Salt:0 Amplifier:26624-27648 Iteration:0-1024
Restore.Sub.#4...: Salt:0 Amplifier:34816-35840 Iteration:0-1024
Candidates.#1....: J9yerane -> pr7njrne
Candidates.#2....: ntj5ajba -> Hq4z2wat
Candidates.#3....: 5xntwhll -> Yrr68011
Candidates.#4....: S8t81698 -> coebs7do
Hardware.Mon.#1..: Temp: 45c Fan: 96% Util: 87% Core:2100MHz Mem:7500MHz Bus:1
Hardware.Mon.#2..: Temp: 43c Fan: 44% Util: 98% Core:1847MHz Mem:5103MHz Bus:1
Hardware.Mon.#3..: Temp: 50c Fan: 94% Util: 92% Core:2025MHz Mem:3802MHz Bus:1
Hardware.Mon.#4..: Temp: 49c Util: 86% Core:1429MHz Mem:3304MHz Bus:1

I have some ideas as to what the problem might be, but I'm pretty sure it isn't my hardware at this point. Your thoughts? I'm going to keep experimenting and I'll update the thread as i find things. If I need to do anything to gather more data in a certain direction, just let me know.

[undeath]

It's acting like a basic dictionary lookup and ignores the rules parameter completely.

You're specifying the rules file for the first instance, rules are applied before they hit the second instance. That doesn't make much sense. If you want to amplify the load you need to specify the rules in the instance actually running on your GPUs.

[XakEp]

Like I said, it was a broken command and I get that. What I don't understand is why using -w in any form more than halves my speed but -O nearly maxes it out.

[XakEp]

I moved the rule to the other side of the pipe, this happens...

hashcat64.exe --stdout d:\wordlists\rockyou.txt | hashcat64.exe -m0 d:\hashlists\Random\Quillen.txt -r rules\best64.rule -O --status --status-timer=10

Session..........: hashcat
Status...........: Running
Hash.Type........: MD5
Hash.Target......: (redacted)
Time.Started.....: Sat Aug 31 12:55:48 2019 (2 mins, 45 secs)
Time.Estimated...: Sat Aug 31 12:58:33 2019 (0 secs)
Guess.Base.......: Pipe
Guess.Mod........: Rules (rules\best64.rule)
Speed.#1.........:  1582.0 kH/s (5.80ms) @ Accel:64 Loops:77 Thr:256 Vec:1
Speed.#2.........:  2134.4 kH/s (8.80ms) @ Accel:128 Loops:77 Thr:256 Vec:1
Speed.#3.........:  1147.7 kH/s (8.02ms) @ Accel:128 Loops:77 Thr:256 Vec:1
Speed.#4.........:  1682.5 kH/s (11.22ms) @ Accel:128 Loops:77 Thr:256 Vec:1
Speed.#*.........:  6546.5 kH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 724283098
Rejected.........: 143066
Restore.Point....: 0
Restore.Sub.#1...: Salt:0 Amplifier:0-77 Iteration:0-77
Restore.Sub.#2...: Salt:0 Amplifier:0-77 Iteration:0-77
Restore.Sub.#3...: Salt:0 Amplifier:0-77 Iteration:0-77
Restore.Sub.#4...: Salt:0 Amplifier:0-77 Iteration:0-77
Candidates.#1....: dexxa12 -> baqueb
Candidates.#2....: klappich -> ixxixx
Candidates.#3....: iiiisssssc -> g4+lpm
Candidates.#4....: gdm2442 -> d34d34
Hardware.Mon.#1..: Temp: 34c Fan: 54% Util:  0% Core:1515MHz Mem:7500MHz Bus:1
Hardware.Mon.#2..: Temp: 31c Fan: 45% Util:  0% Core:1480MHz Mem:5103MHz Bus:1
Hardware.Mon.#3..: Temp: 32c Fan: 55% Util:  0% Core:1632MHz Mem:3802MHz Bus:1
Hardware.Mon.#4..: Temp: 35c Fan: 70% Util:  0% Core:1189MHz Mem:3304MHz Bus:1

I'd say there's an argument here it's not actually doing anything. Over the time that test ran, the Candidates only changed twice I think? So yeah, something funky is going on and I can't put my finger on it. If I run commands as they're in the FAQ for getting more speed/parallel power, I either get no improvement or a drastic reduction in performance.

If I'm huffing paint (hey, there's a TON I don't know here) then by all means please correct me in that lovingly harsh way y'all correct stupid n00bs (learn math lol, loved that post). I'm a big boy and can take it lol, just trying to figure out an interesting challenge here and learn while I'm at it.