08-13-2017, 05:34 AM
I'm using hashcat64.exe with -w 3 and -m 2500. I've looked up a ton of 1080gtx benchmarks and I should be hitting ~500kH/s, but I'm hitting ~270-290kH/s. Any idea what to do here?
|
1080gtx running slow with WPA
|
08-13-2017, 07:17 AM
At stock clocks you should be around 415 KH/s, with an overclock you should be around 530 KH/s. So yes, 290 KH/s is pretty low -- that's actually right in line with how a GTX 1070 performs. Assuming you're positive you have a GTX 1080 and not a 1070, check clocks, perf level, power limit, temps, make sure you're not being throttled.
08-13-2017, 11:33 AM
(08-13-2017, 07:17 AM)epixoip Wrote: At stock clocks you should be around 415 KH/s, with an overclock you should be around 530 KH/s. So yes, 290 KH/s is pretty low -- that's actually right in line with how a GTX 1070 performs. Assuming you're positive you have a GTX 1080 and not a 1070, check clocks, perf level, power limit, temps, make sure you're not being throttled. Yep, definitely a 1080GTX. Slightly overclocked. Hashcat shows core at 1936MHz, mem at 4911MHz, Bus at 16... I'm currently trying an all digit bruteforce WPA attack, which is running at 85-90% GPU usage in MSI Afterburner, but earlier when I wrote the post, I was doing a dictionary attack, which was 96-98% GPU usage if I recall correctly... Temps do seem quite low (76 degrees celcius in a pretty small HTPC case, all air cooling, very standard setup)...
08-14-2017, 05:13 AM
Are you sure there's only one handshake in your capture? Because it sounds like there may be two different SSIDs.
08-15-2017, 03:31 AM
08-15-2017, 04:29 AM
Two Hashcat processes running simultaneously? One you forgot about running under screen?
 I don't know, I'm kind of at a loss on this one.
Is your CPU hashing too? Otherwise try to use stock clock and run one simple benchmark. See if the results are as expected with all the usual hash methods (MD4, MD5, NTLM etc.).
|
|
« Next Oldest | Next Newest »
|
