Hashcat randomly stops
#1
cudaHashcat64.exe -p --show --force -m 10 "testcrack.txt" "hashkiller-dict.txt" --separator=: --gpu-loops=1024

Code:
cudaHashcat v1.33 starting...

Device #1: GeForce GTX 860M, 4096MB, 1019Mhz, 5MCU
Device #1: WARNING! Kernel exec timeout is not disabled, it might cause you errors of code 702
           You can disable it with a regpatch, see here: http://hashcat.net/wiki/doku.php?id=timeout_patch

Hashes: 45 hashes; 45 unique digests, 45 unique salts
Bitmaps: 9 bits, 512 entries, 0x000001ff mask, 2048 bytes
Rules: 1
Applicable Optimizers:
* Zero-Byte
* Precompute-Init
* Precompute-Merkle-Demgard
* Meet-In-The-Middle
* Early-Skip
* Not-Iterated
* Appended-Salt
* Scalar-Mode
* Raw-Hash
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: Kernel ./kernels/4318/m00010_a0.sm_50.64.ptx

Cache-hit dictionary stats hashkiller-dict.txt: 224465332 bytes, 18138922 words,
18138922 keyspace


Session.Name...: 40000
Status.........: Exhausted
Input.Mode.....: File (hashkiller-dict.txt)
Hash.Target....: File (testcrack.txt)
Hash.Type......: md5($pass.$salt)
Time.Started...: Sun Mar 01 17:09:25 2015 (10 secs)
Time.Estimated.: 0 secs
Speed.GPU.#1...:  3979.8 kH/s
Recovered......: 0/45 (0.00%) Digests, 0/45 (0.00%) Salts
Progress.......: 816251490/816251490 (100.00%)
Skipped........: 0/816251490 (0.00%)
Rejected.......: 12258720/816251490 (1.50%)
HWMon.GPU.#1...:  0% Util, 44c Temp, N/A Fan

Started: Sun Mar 01 17:09:25 2015
Stopped: Sun Mar 01 17:09:38 2015
#2
I've edited your post so that it is actually readable.

You have four problems here:

1. You are using --force. Your system is not properly configured if you need to use this, and you shouldn't post any bug reports when using --force.

2. You have not applied the timeout patch. The timeout patch prevents hashcat from randomly stopping. This might fix one of your problems.

3. You're using command line switches that make absolutely no sense, which means you probably don't know what they do. "-p --show --separator=:" ??

4. The output you pasted doesn't show hashcat "randomly" stopping. It shows that it successfully reached the end of your wordlist and cleanly exited. That's precisely what it's supposed to do.

From all of this I gather you do not understand how hashcat works, nor how to use hashcat. Take the time to study the wiki.
#3
Sorry, I didnt realize my post wasnt in english before you edited it.

1. I use --force to force it to process the list I need cracked even when there is a "blank spot" in m rows of hashes.

2. Maybe this is it.

3. Maybe, but this was working fine yesterday and it just started this so I think its irrelevant. Separator is used when splitting hashes by :, is it not? (md5Confusedalt) When I run that list without that variable, it gives me an error, when I run it with the variable, the list processes.

4. Yesterday it took over 5 hours to crack one hash from that list so thats not the issue.

From all this, I gather you don't speak to people in this demeanor outside of the internet. Thanks for your assistance.
#4
Applied the time-out patch and removed all variables but the hash type. Still the same outcome.

cudaHashcat64.exe -m 1000 "testcrack.txt" "hashki
ller-dict.txt"
cudaHashcat v1.33 starting...


Device #1: GeForce GTX 860M, 4096MB, 1019Mhz, 5MCU

Hashes: 4 hashes; 4 unique digests, 1 unique salts
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Rules: 1
Applicable Optimizers:
* Zero-Byte
* Precompute-Init
* Precompute-Merkle-Demgard
* Meet-In-The-Middle
* Early-Skip
* Not-Salted
* Not-Iterated
* Single-Salt
* Scalar-Mode
* Raw-Hash
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: Kernel ./kernels/4318/m01000_a0.sm_50.64.ptx

Cache-hit dictionary stats hashkiller-dict.txt: 224465332 bytes, 18138922 words,
18138922 keyspace


Session.Name...: cudaHashcat
Status.........: Exhausted
Input.Mode.....: File (hashkiller-dict.txt)
Hash.Target....: File (testcrack.txt)
Hash.Type......: NTLM
Time.Started...: Sun Mar 01 21:10:42 2015 (4 secs)
Time.Estimated.: 0 secs
Speed.GPU.#1...: 4431.4 kH/s
Recovered......: 0/4 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 18138922/18138922 (100.00%)
Skipped........: 0/18138922 (0.00%)
Rejected.......: 272416/18138922 (1.50%)
HWMon.GPU.#1...: 0% Util, 40c Temp, N/A Fan

Started: Sun Mar 01 21:10:42 2015
Stopped: Sun Mar 01 21:10:52 2015
#5
The only problem here is you center-aligning your posts, and not understanding how hashcat works.
#6
I cannot see any problems here.
#7
Neither can I.
Closed.