Status EXHAUSTED with correct PWD in list
#1
Hi,

I'm new with Hashcat and i get allways "Exhausted", my wordlist contains to 100% the password "28958178" .

I dont know what to do, pls help me.

hashcat64.exe -m 2500 --self-test-disable plus.hccapx wordlist09.lst
(Without --self-test, it doesnt use GPU )



Approaching final keyspace - workload adjusted.

Session..........: hashcat
Status...........: Exhausted
Hash.Type........: WPA-EAPOL-PBKDF2
Hash.Target......: Liwest90DA-2.4G (AP:38:70:0c:fa:90:d8 STA:38:a4:ed:07:0a:fe)
Time.Started.....: Thu Jul 04 21:34:44 2019 (21 mins, 20 secs)
Time.Estimated...: Thu Jul 04 21:56:04 2019 (0 secs)
Guess.Base.......: File (wordlist09.lst)
Guess.Queue......: 1/1 (100.00%)
Speed.#1.........:    54379 H/s (0.73ms) @ Accel:64 Loops:32 Thr:64 Vec:1
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 70067613/70067613 (100.00%)
Rejected.........: 467213/70067613 (0.67%)
Restore.Point....: 70067613/70067613 (100.00%)
Restore.Sub.#1...: Salt:0 Amplifier:0-1 Iteration:0-1
Candidates.#1....: $HEX[5ab43a518070589c710bedf87ef1aadc5cc960bacb9ceeeebbc9dd82cb2ce6175d] -> $HEX[adeab79f6f6d4df702c42002c0f7a0f807b60e681ef8c7bc7b26378326739e4c9833b03278ce03cb6e]
Hardware.Mon.#1..: Temp: 73c Fan: 73% Util: 82% Core: 860MHz Mem:1200MHz Bus:8

Started: Thu Jul 04 21:34:41 2019
Stopped: Thu Jul 04 21:56:04 2019
Reply
#2
don't report problems when using --self-test-disable. your driver is broken.
Reply
#3
(07-05-2019, 08:54 PM)undeath Wrote: don't report problems when using --self-test-disable. your driver is broken.

what does it mean my driver is broken?

I already deleted amd drivers completely, and installed the newest amd driver 19.6.3 .

What more can i do with my driver?

Should i take an older version of Hashcat?
Reply
#4
had the same problem i still run 3.4 just fine
Reply
#5
I tried it with the same settings with an older Hashcat version (4.2.1)
Now its cracked, but i only get 38109 H/s , with Hashcat (5.10) i get 54000 H/s but evertime status exhausted.

Nobody with the same error or solution?




663f6e47b07e6594066fef6c00ffa2b4:38700cfa90d8:38a4ed070afe:Liwest90DA-2.4G:28958178

Session..........: hashcat
Status...........: Cracked
Hash.Type........: WPA-EAPOL-PBKDF2
Hash.Target......: Liwest90DA-2.4G (AP:38:70:0c:fa:90:d8 STA:38:a4:ed:07:0a:fe)
Time.Started.....: Sat Jul 06 00:04:05 2019 (12 mins, 40 secs)
Time.Estimated...: Sat Jul 06 00:16:45 2019 (0 secs)
Guess.Base.......: File (wordlist09.lst)
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....: 38109 H/s (8.18ms) @ Accel:32 Loops:16 Thr:256 Vec:1
Recovered........: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.........: 28966912/70067613 (41.34%)
Rejected.........: 0/28966912 (0.00%)
Restore.Point....: 28835840/70067613 (41.15%)
Candidates.#1....: 28835840 -> 28966911
HWMon.Dev.#1.....: Temp: 67c Fan: 59% Util: 92% Core: 860MHz Mem:1200MHz Bus:8

Started: Sat Jul 06 00:03:36 2019
Stopped: Sat Jul 06 00:16:47 2019
Reply
#6
i did notice also when running 5.1.0 with self test disabled it ran at like 160k/s but in 3.4 im running 550-600k/s
Reply
#7
i will try it with version 3.4 too, thank u for your answer
Reply
#8
Hascat v3.4 works perfect for me, with incredible boost i get 200 k/s !!!

thank u so much!
Reply
#9
Session..........: hashcat
Status...........: Running
Hash.Type........: WPA/WPA2
Hash.Target......: A1.hccapx
Time.Started.....: Sat Jul 06 02:27:22 2019 (7 hours, 9 mins)
Time.Estimated...: Sat Jul 06 20:47:00 2019 (11 hours, 10 mins)
Input.Mask.......: ?h?h?h?h?h?h?h?h [8]
Input.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....: 207.9 kH/s (8.37ms)
Recovered........: 0/3 (0.00%) Digests, 0/3 (0.00%) Salts
Progress.........: 4528939008/12884901888 (35.15%)
Rejected.........: 0/4528939008 (0.00%)
Restore.Point....: 94347264/268435456 (35.15%)
Candidates.#1....: baca7f72 -> bf8f99a0
HWMon.Dev.#1.....: Temp: 75c Fan: 42% Util: 96% Core: 860MHz Mem:1200MHz Lanes:
Reply
#10
yes idk why its faster on an older version but seems to work well for me too
Reply