Old restore file writed.
#1
v6.2.6-496-gd127558bb

-w 4

Session..........: xxx
Status...........: Aborted (Checkpoint)
Hash.Mode........: 1000 (NTLM)
Hash.Target......: ntlm.txt
Kernel.Feature...: Optimized Kernel
Guess.Base.......: Mask (?a?a?a?a) [4], Left Side
Guess.Mod........: File (r_5_plus.txt), Right Side
Speed.#1.........: 14756.4 MH/s (325.65ms) @ Accel:256 Loops:1024 Thr:512 Vec:1
Speed.#2.........:  1924.7 MH/s (416.84ms) @ Accel:256 Loops:1024 Thr:32 Vec:4
Speed.#*.........: 16681.1 MH/s
Recovered........: 237/2447941 (0.01%) Digests (total), 237/2447941 (0.01%) Digests (new)
Remaining........: 2447704 (99.99%) Digests
Recovered/Time...: CUR:0,1,N/A AVG:0.35,20.92,N/A (Min,Hour,Day)
Progress.........: 448394161490000/1540882190694375 (29.10%)
Rejected.........: 6516050000/448394161490000 (0.00%)
Restore.Point....: 786439/18917991 (4.16%)
Restore.Sub.#1...: Salt:0 Amplifier:81449984-81450625 Iteration:0-1024
Restore.Sub.#2...: Salt:0 Amplifier:81449984-81450625 Iteration:0-1024
Candidate.Engine.: Device Generator
Candidates.#1....: v"~}12261954 ->  ~?~7234025
Candidates.#2....: v"~}12345 ->  ~?~12261959
Reply
#2
what do you want to tell or ask?

your cracking task stopped, because you or someone else pressed the key [C] which caused hashcat to stop the task when reaching the next checkpoint

you can continue with hashcat --session yousessionname (default hashcat) --restore or starting the same task with the skip parameter (dont sure about that, should test it)
Reply