Hi!
I have Ubuntu 16 with installed Cuda 10.2 and Last Nvidia drivers - geforce 440.64
The system has 16 gb RAM , Core i3 and 7x1080ti
I compiled Hashcat from last github source. And have a strange bug:
CUDA API is using.
- I have dictionary splitted on files by 512mb.
- If i using -m 21700 or -m 21800 - hashcat always freezes on 70-86% progress in same files (for example always on dict4 and dict9). When i press S for status it just print in cmd line and nothing happend. Then i should use cntrl-c to stop proccess. (look attachment)
- If i use ./hashcat --restore after abort. It freezes too.
- I tried to use different hash's - but no results.
- If i using -m 11300 - i haven't any problems.
./hashcat -a 0 -m 21700 /mnt/hdd/hash/ehash.txt /mnt/hdd/pass.txt.004
How can i catch where the bug ?
I have Ubuntu 16 with installed Cuda 10.2 and Last Nvidia drivers - geforce 440.64
The system has 16 gb RAM , Core i3 and 7x1080ti
I compiled Hashcat from last github source. And have a strange bug:
CUDA API is using.
- I have dictionary splitted on files by 512mb.
- If i using -m 21700 or -m 21800 - hashcat always freezes on 70-86% progress in same files (for example always on dict4 and dict9). When i press S for status it just print in cmd line and nothing happend. Then i should use cntrl-c to stop proccess. (look attachment)
- If i use ./hashcat --restore after abort. It freezes too.
- I tried to use different hash's - but no results.
- If i using -m 11300 - i haven't any problems.
./hashcat -a 0 -m 21700 /mnt/hdd/hash/ehash.txt /mnt/hdd/pass.txt.004
How can i catch where the bug ?