Hashcat aborting (bug?)

[rsberzerker]

I set a hashcat run to run overnight. In the morning, it had stopped. The last status is:

Session..........: emailspecialmask

Status...........: Exhausted
Hash.Type........: MD5
Hash.Target......: C:\Users\<redacted>\Documents\lefts\090217_md5_left.txt
Time.Started.....: Mon Sep 04 21:56:10 2017 (2 hours, 49 mins)
Time.Estimated...: Thu Nov 05 09:32:03 2020 (3 years, 61 days)
Guess.Base.......: File (C:\Users\<redacted>\Documents\wordlists\emaildomainsv2U.txt), Right Side
Guess.Mod........: Mask (?1?1?1?1?1?1?1?1?1) [9], Left Side
Guess.Charset....: -1 ?l?d, -2 Undefined, -3 Undefined, -4 Undefined
Speed.Dev.#1.....:   566.1 MH/s (0.46ms)
Recovered........: 36/960851 (0.00%) Digests, 0/1 (0.00%) Salts
Recovered/Time...: CUR:0,9,N/A AVG:0,12,306 (Min,Hour,Day)
Progress.........: 5656097587200/495206348715196416 (0.00%)
Rejected.........: 0/5656097587200 (0.00%)
Restore.Point....: 4876/4876 (100.00%)
Candidates.#1....: s0dphgere -> y9pzlhane@zzom.co.uk
HWMon.Dev.#1.....: Temp: 57c Fan: 55% Util: 62% Core:1163MHz Mem:2505MHz Bus:16

Started: Mon Sep 04 21:56:06 2017
Stopped: Tue Sep 05 00:45:25 2017

I attempted to restart it, using the command, with the -s value from the progress above to resume:

hashcat64.exe -m 0 -a 7 --remove -o "C:\Users\<redacted>\Documents\lefts\090217_md5_cracked.txt" --status --markov-hcstat="C:\Users\<redacted>\Documents\hashcat-3.6.0\082617_founds.hcstat" --session=emailspecialmask  "C:\Users\<redacted>\Documents\lefts\090217_md5_left.txt" -1 ?l?d ?1?1?1?1?1?1?1?1?1 "C:\Users\<redacted>\Documents\wordlists\emaildomainsv2U.txt" -s 5656097587200

But all it did was abort:

* Keyspace..: 495206348715196416

Restore value is greater than keyspace.

Hashcat 3.6.0 on Windows 7 x64.

Am I missing something or is this a bug?

[philsmd]

You should try again with the latest beta versions of hashcat (https://hashcat.net/beta/ , do not forget to use -O if you want to use the optimized kernels and have the same speed as with 3.6).

Recently devs fixed some problems with the progress getting larger than the restore point. This might be the same problem happening here, see:

Progress.........: 5656097587200/495206348715196416 (0.00%)
Restore.Point....: 4876/4876 (100.00%)

In theory the restore point percentage value should never be greater than the progress number.

Please test with beta. thx

[stumblebot]

I have experienced the same issue with the same version of hashcat. As suggested, I attempted to use the current beta version and observed the same problem.